Resources · n8n integration

uProc n8n integrationAutomate uProc with n8n.

Every uProc tool sits behind two dropdowns. The uProc n8n integration ships a single operation, Consume uProc API, backed by 11 resource families. Pick the family, pick the tool, fill the value field it asks for. uProc has no trigger node, so a Schedule starts the run.

Try the uProc integration on n8n See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the uProc n8n integration actually do?

uProc sorts its data tools into families, and the n8n node mirrors that shape. One operation, named Consume uProc API, then a Resource dropdown for the family and an Operation dropdown for the tool itself. The families are audio, communication, company, finance, geographical, image, internet, personal, product, security and text, 11 of them.

It is an action node. uProc has no trigger node in n8n, so the workflow starts elsewhere and uProc runs somewhere in the middle of it.

Learn the gesture, not the catalog. Open the node, set Resource to the family your data belongs to, then read the Operation list, described in n8n as "The Operation to consume", which holds the tools of that family. Once a tool is selected, fill the value field it works on. Every value field is marked required, and a required field left empty stops the node before it runs.

Cleaning a mailing list. The communication family carries the email checks: valid format, free provider like Gmail, disposable email service, catchall mailbox, role-based account, spam trap. Read the rows from Google Sheets, pass each address into Email, write the verdict back next to the row, and only then send through Gmail.

Finding a prospect address. Another communication tool discovers an email from a company website or domain plus the prospect's first name and last name. Fill Domain and Firstname, add Lastname, then choose Mode among guess, only_verify and verify. The finished lead record lands in Airtable or in Postgres.

Turning a message into audio. The audio family exposes getAudioSpeechByText and getAudioAdvancedSpeechByText, both of which get an audio file from a provided text and language. Text takes the script, Language offers values like american, french or spanish, and Gender is male or female.

Two settings pay off later. Under Additional Options, Data Webhook takes a URL that receives the tool response once the tool has resolved the request. And when the uProc endpoint you need has no entry in the Operation list, the HTTP Request node calls it directly and reuses the same uProc credential through predefined authentication. Published templates already pair the node with others, scraping pages into MongoDB, sending a website screenshot to a Telegram channel, watching the SSL certificate of a domain. If you are still choosing a platform, the n8n review goes into the trade-offs.

Connect

How do you connect uProc to n8n?

01
Open a uProc account
Sign up on uproc.io first, because the node authenticates against that account. On the n8n side there is nothing to install: the uProc node ships with n8n, on n8n Cloud and on a self-hosted instance under the Community Edition and its Sustainable Use license. The node itself has no authentication selector, so the credential does all the work.
02
Copy the email and the key
In uProc, go to Settings > Integrations > API Credentials. Both values you need are on that screen. The Email field of the n8n credential takes the address you log in to uProc with, which is displayed there too. The API Key field takes the value listed as API Key (real) in the API Credentials section, and API key is the supported authentication method for this node.
03
Save the credential once
Back in n8n, open the Credentials menu, create the uProc credential, paste both values and save. A credential is created once and reused across every workflow, and the node offers it in its own dropdown. A second uProc node in the same workflow picks the same entry, so nothing gets retyped when you chain two tools.

Actions

What the uProc node can do

The uProc node exposes one operation. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Consume uProc API

execute

What you see in n8n

uProcParameters

Credential to connect withuProc account

OperationuProc

Credit card *{{ $json.credit_card }}

Address *{{ $json.address }}

Coordinates *{{ $json.coordinates }}

Date *{{ $json.date }}

Years1 *{{ $json.years1 }}

Years2 *{{ $json.years2 }}

Years *{{ $json.years }}

Ean *{{ $json.ean }}

Asin *{{ $json.asin }}

Text *{{ $json.text }}

Gender *{{ $json.gender }}

Language *{{ $json.language }}

Account *{{ $json.account }}

Bic *{{ $json.bic }}

Isocode *{{ $json.isocode }}

Iban *{{ $json.iban }}

Swift *{{ $json.swift }}

Bcid *{{ $json.bcid }}

Author *{{ $json.author }}

Category *{{ $json.category }}

Isbn *{{ $json.isbn }}

Publisher *{{ $json.publisher }}

Title *{{ $json.title }}

Dni *{{ $json.dni }}

Cif *{{ $json.cif }}

Nie *{{ $json.nie }}

Nif *{{ $json.nif }}

Ip *{{ $json.ip }}

City *{{ $json.city }}

Phone *{{ $json.phone }}

Zipcode *{{ $json.zipcode }}

Upc *{{ $json.upc }}

Isin *{{ $json.isin }}

Number *{{ $json.number }}

Uuid *{{ $json.uuid }}

Domain *{{ $json.domain }}

Duns *{{ $json.duns }}

Email *{{ $json.email }}

Name *{{ $json.name }}

Url *{{ $json.url }}

Profile *{{ $json.profile }}

Role *{{ $json.role }}

Taxid *{{ $json.taxid }}

Company *{{ $json.company }}

Message *{{ $json.message }}

Message1 *{{ $json.message1 }}

Message2 *{{ $json.message2 }}

Address1 *{{ $json.address1 }}

Address2 *{{ $json.address2 }}

Fuel consumption *{{ $json.fuel_consumption }}

Price liter *{{ $json.price_liter }}

Coordinates1 *{{ $json.coordinates1 }}

Coordinates2 *{{ $json.coordinates2 }}

Ip1 *{{ $json.ip1 }}

Ip2 *{{ $json.ip2 }}

Phone1 *{{ $json.phone1 }}

Phone2 *{{ $json.phone2 }}

Zipcode1 *{{ $json.zipcode1 }}

Zipcode2 *{{ $json.zipcode2 }}

Distance *{{ $json.distance }}

Coin *{{ $json.coin }}

Country code *{{ $json.country_code }}

Amount *{{ $json.amount }}

Isocode1 *{{ $json.isocode1 }}

Isocode2 *{{ $json.isocode2 }}

Date1 *{{ $json.date1 }}

Date2 *{{ $json.date2 }}

Date3 *{{ $json.date3 }}

Period *{{ $json.period }}

Useragent *{{ $json.useragent }}

Email from *{{ $json.email_from }}

Email to *{{ $json.email_to }}

Subject *{{ $json.subject }}

Body *{{ $json.body }}

Firstname *{{ $json.firstname }}

Mode *{{ $json.mode }}

Fullname *{{ $json.fullname }}

Mobile *{{ $json.mobile }}

Source *{{ $json.source }}

Destination *{{ $json.destination }}

Length1 *{{ $json.length1 }}

Length2 *{{ $json.length2 }}

Length *{{ $json.length }}

Separator *{{ $json.separator }}

Latitude *{{ $json.latitude }}

Longitude *{{ $json.longitude }}

Imei *{{ $json.imei }}

Regex *{{ $json.regex }}

Host *{{ $json.host }}

Port *{{ $json.port }}

Number1 *{{ $json.number1 }}

Number2 *{{ $json.number2 }}

Number3 *{{ $json.number3 }}

Luhn *{{ $json.luhn }}

Mod *{{ $json.mod }}

Rest *{{ $json.rest }}

Password *{{ $json.password }}

Locality *{{ $json.locality }}

Surname *{{ $json.surname }}

Province *{{ $json.province }}

Format *{{ $json.format }}

Text1 *{{ $json.text1 }}

Text2 *{{ $json.text2 }}

Glue *{{ $json.glue }}

Field *{{ $json.field }}

Find *{{ $json.find }}

Replace *{{ $json.replace }}

Texts *{{ $json.texts }}

Html *{{ $json.html }}

Tin *{{ $json.tin }}

Vin *{{ $json.vin }}

Count1 *{{ $json.count1 }}

Count2 *{{ $json.count2 }}

Count *{{ $json.count }}

Additional Options+ Add Field (1)

Notes & use cases

A single operation covers the whole node. You choose a uProc tool inside it, and n8n runs that tool with the values you pass in.

Key parameters

Resource (group): the tool family, from audio and communication to finance, product and text, 11 in all.
Operation (tool): the tool to consume, for example getAudioSpeechByText (Get Speech By Text).
Email, Domain, Phone, Text: the value fields, each marked required, each usually fed by an expression like {{ $json.field }} from the previous node.
Data Webhook, in Additional Options: a URL that receives the tool response once the tool has resolved the request.

Use cases

check an address before a campaign, or read a text out loud as an audio file.

Need help

Need help automating uProc with n8n?

A person reads every message.

FAQ

uProc and n8n, the questions that come next

01Is the uProc n8n integration free?

On the n8n side, yes. The uProc node ships with n8n, so there is nothing to install and no extra cost from n8n, and it behaves the same on n8n Cloud as on a self-hosted instance running the Community Edition under its Sustainable Use license. What a uProc account costs is a separate matter handled on uProc's side, and you do need one: the node authenticates with a uProc API key, and without a credential the operation cannot run. Budget the uProc account, not the connector.

02What credentials does the uProc node need?

One credential, using an API key. It holds two values, both found in uProc under Settings > Integrations > API Credentials: an Email, which is the address you use to log in to uProc and which is displayed on that same screen, and an API Key, the value shown as API Key (real). The node has no authentication selector of its own, so there is no method to pick inside it. Create the credential once from the n8n Credentials menu and every workflow can reuse it, including the HTTP Request node through predefined authentication.

03What are the limits of the uProc node in n8n?

The node exposes one operation, Consume uProc API, and everything else is chosen inside it: Resource for the family, Operation for the tool, then the value field that tool works on. Two practical points follow. Every value field is marked required, so leaving one empty stops the node instead of sending a partial call. And when the uProc endpoint you want has no entry in the Operation list, the HTTP Request node calls it directly and reuses the same uProc credential through predefined authentication, which keeps the workflow on one set of keys.

04Can uProc trigger an n8n workflow in real time?

No, because uProc has no trigger node in n8n. A workflow that uses uProc starts with another trigger: a Schedule Trigger firing on a fixed interval, the n8n Webhook node called by a third-party service, or the trigger of another tool you already automate. One uProc setting is related but different: Data Webhook, in Additional Options, takes a URL that receives the tool response once the tool has resolved the request. That URL can be an n8n Webhook, which is how a long-running tool comes back into a workflow.

05n8n or Make for uProc?

It comes down to four criteria, not to which platform is better. Hosting: n8n runs self-hosted through Docker or npm, or on n8n Cloud, while Make is a hosted platform with no self-hosting option. Data control follows from that, since a self-hosted instance keeps the data inside your own infrastructure. Cost model: Make bills per operation, which matters when a uProc tool runs on every row of a large file. Visual logic is the fourth, and it is mostly a matter of habit. Both call the same uProc account.

Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Open a uProc account

Copy the email and the key

Save the credential once

Need help automating uProc with n8n?

Get our weekly integration tips.