uProc
Clean, validate and enrich data with uProc's catalogue of tools — one row in real time, a column of values as a job, or a whole remote file.
OCNORA ships 8 typed uProc operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://api.uproc.io/api/v2 through the HTTP node with the same credential.
Before you connect uProc
- Authentication
- Username & password
- Credential
- {"email": "…", "api_token": "…"} — the account email and its API key
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with uProc
Operations, grouped by what they do to your data.
Create and send 3
Read and search 4
Other operations 1
A sample uProc workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no uProc trigger is needed.
- 2Get Account Profileuproc.get_profileRetrieve the uProc account the connection's credential belongs to; this is also what the connection test calls.
- 3Run Tooluproc.processRun one uProc tool over a single row and return its result in the same step — the node for cleaning, validating or enriching a value.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Get Account ProfileRetrieve the uProc account the connection's credential belongs to; this is also what the connection test calls.uproc.get_profile
- Describe ToolRetrieve one uProc tool from the catalogue — what it does and which parameters it takes — so a run can be built without hardcoding them.uproc.get_tool
- List Tool GroupsList the groups the uProc tool catalogue is organised into, such as communication, company, geographic and product.uproc.list_groups
- List JobsList the background jobs on the account, so a workflow can follow up on a batch or stream run it started earlier.uproc.list_jobs
- Run ToolRun one uProc tool over a single row and return its result in the same step — the node for cleaning, validating or enriching a value.uproc.process
- Run Tool to WebhookSchedule one uProc tool over a single row and have the result POSTed to a webhook, so a slow lookup does not hold the run open.uproc.process_async
- Run Tool Over Many RowsRun one uProc tool over a column of values as a background job; every params entry is an array with one element per row.uproc.process_multiple
- Process a Remote FileApply one or more uProc tools to a remote file or database table and write the enriched rows back beside it.uproc.process_stream
uProc questions
- How does OCNORA authenticate with uProc?
- With a stored Username & password credential, shaped {"email": "…", "api_token": "…"} — the account email and its API key. A connection test can check it when you add it.
- What can I automate with uProc?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the uProc operation I need is not listed?
- Call https://api.uproc.io/api/v2 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use uProc?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are uProc calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first uProc workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.