Book a demo

Run Tool Over Many Rows

uproc.process_multiple
ActionBusiness appsconnection required

Calls the uProc API with the connection's credentials.

Run one uProc tool over a column of values as a background job; every params entry is an array with one element per row.

Ask about uProcAll uProc nodesProvider API docs ↗

Connection

Required
Yes — the node will not save without one
Auth type
Username & password
Providers
uProc
Secret shape
{"email": "…", "api_token": "…"} — the account email and its API key
Resolved by
config.connection_id, else node.connection_id

Configuration

6 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
processor
Name of the uProc tool to run, in dashed lower case; uproc.list_groups and uproc.get_tool name the ones your plan can reach.
stringYes——get-email-lookup
params
The tool's parameters, each holding an array of values with one element per row to process.
objectYes—≥ 1 characters{"email":["ada@example.com","bob@example.com"]}
callback
Webhook URLs uProc notifies as the job runs, keyed by start, progress, end, error or data; omit it and the results stay in the uProc Jobs section.
objectNo——{"end":"https://example.com/hooks/uproc-end"}
normalized
Let uProc clean the parameter values (trim, case, punctuation) before the tool runs; leave off to send them exactly as supplied.
booleanNofalse——
limit
Maximum number of rows to return when the tool resolves to more than one.
numberNo50≥ 1—
write_titles
Write a header row at the top of the CSV results file uProc produces for the job.
booleanNotrue——

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "callback": {
    "end": "https://example.com/hooks/uproc-end"
  },
  "limit": 50,
  "normalized": false,
  "params": {
    "email": [
      "ada@example.com",
      "bob@example.com"
    ]
  },
  "processor": "get-email-lookup",
  "write_titles": true
}

Output

One shape.

result

FieldTypeExample
result
True when uProc accepted the job.
boolean—
message.id
Identifier of the scheduled job.
string—
message.status
Status uProc gave the job.
string—
message.total_rows
How many rows the job will process.
number—
message.estimated_price
Estimated cost of the job, in the account's currency.
number—
callback
Confirmation of where each callback will be sent.
object—
{
  "callback": {},
  "message": {
    "estimated_price": 0,
    "id": "",
    "status": "",
    "total_rows": 0
  },
  "result": false
}

Notes

  • This runs in the background: the rows are not in this step's output. Set a 'data' or 'end' callback, or collect the results file from the uProc Jobs section.

Related uProc nodes

See Run Tool Over Many Rows run in a workflow.

In a technical demo we add the uProc connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.

Book a technical demoTalk to sales