Resources · Make integration

uProc Make integrationAutomate uProc with Make.

Need uProc data inside your other tools without copying it by hand? The uProc Make integration gives you 2 action modules. This guide is for people who know uProc and are new to Make: connect the account, build a first scenario, and see when each module helps.

Try the uProc integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the uProc Make integration do for you?

The uProc Make integration links your uProc account to Make so a scenario (the automation you build in Make, a chain of modules) can call a uProc tool and pass its answer to your other apps. There are two modules, both actions, and no trigger, so another app or a schedule starts the flow.

Get data from a uProc tool on demand. The Select a Tool module lets you pick one of the tools of your uProc account and returns the data it produces. Put it after the module of another app that brings in a record, and each record goes through the tool you chose.

Reach what the listed module does not cover. Make an API Call sends an authorized request to any endpoint of the uProc API, with the same connection. It is the fallback when Select a Tool is not enough.

Feed the result to the rest of your stack. Each answer becomes a bundle (one item passed from a module to the next) that you map into a spreadsheet, a CRM or an email.

What Make does not give you here: a uProc trigger. Nothing in uProc can start a scenario by itself, so plan the start on another app or on the schedule. The uProc n8n integration covers the same app on the other platform, and n8n vs Make lays out how the two tools differ. If a run fails, Make troubleshooting lists the usual causes.

Connect

How do you connect uProc to Make?

  1. 01

    Add a uProc module

    In your scenario, click the +, search for uProc and pick Select a Tool. Then click Create a connection. A connection is your uProc account linked to Make once, then reused by both modules.

  2. 02

    Name the connection

    Giving it a name is optional but helps later. Something like "uProc main account" tells you at a glance which account a module uses when you reopen the scenario.

  3. 03

    Authorize and save

    Follow what uProc asks for: approve access on the uProc page, or paste the key uProc gives you. Click Save, and Make can now list the tools of your account inside the module.

First scenario

Your first scenario with uProc

GoalWhen a new record reaches Make from another app, Make runs it through a uProc tool and hands the answer to the next module.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Add the module of the app that holds your records, for example a new row in a sheet, since uProc has no trigger.

  2. 02

    Add Select a Tool

    Click the + on the right of that first module, search uProc and choose Select a Tool. Create the connection if this is your first uProc module.

  3. 03

    Pick the tool and map data

    Once connected, Make lists what it can read from your uProc account. Choose the tool you need, then map the values coming from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. The scenario runs one time, and you can open each module to read the bundles it received and check what uProc sent back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default on a new scenario), then switch the scenario on. Each module run counts as an operation on your Make plan.

Modules

What the uProc modules do

uProc gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

uProc1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module lets you call any endpoint of the uProc API from your scenario, reusing the connection you already created, so you are not limited to what the other module exposes.

When to use it
a uProc feature you need does not appear in Select a Tool, and you have the API documentation of uProc at hand to build the request.
Watch out
you write the request yourself, so check the result of a first Run once before you switch the scenario on.
uProc2

Select a Tool

Action

In Make“Selects your preferred tool and get data.”

Pick one of the tools available in your uProc account and get back the data it returns, ready to map into the next module of the scenario. It is the everyday entry point into uProc.

When to use it
records arrive from a form, a sheet or a CRM, and you want each one processed by the same uProc tool before it moves on.
Watch out
the module runs once per bundle it receives, and each run is an operation counted on your Make plan.
Need help

Need help automating uProc with Make?

A person reads every message.

FAQ

uProc and Make: common questions

01Is the uProc Make integration free?
Yes, on the Make side. uProc is a standard app, available from the Free plan, like the 3,000+ standard apps of Make. The Free plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and count usage in credits each month. What uProc itself charges for your account is a separate matter this page does not cover.
02What do you need to connect uProc to Make?
A uProc account and a Make account. The uProc documentation lists no specific prerequisite and no connection steps of its own, so Make uses its generic flow: add a uProc module, click Create a connection, optionally name it, then authorize Make on the uProc page or paste the key uProc provides, and click Save. The connection is then shared by both uProc modules, so you only do this once per account.
03Can a uProc scenario start in real time?
Not from uProc. The app has no trigger module, scheduled or instant, so uProc cannot start a scenario on its own. Two options remain. Start the scenario with a trigger from another app, such as the form or the sheet where your records land, and place Select a Tool after it. Or rely on the schedule of the first module, which is every 15 minutes by default on a new scenario, with 15 minutes as the minimum on the Free plan and 1 minute on paid plans.
04What if the uProc module you need is missing?
Use Make an API Call. When an app has this module, any endpoint of its API can be called from the scenario with the same connection, so a uProc feature that Select a Tool does not expose is still reachable. You build the request from the uProc API documentation. The Make documentation for uProc gives no numbered limit, so there is no documented quota to plan around on the Make side; test with Run once and read the response before activating.
05Should you use Make or n8n for uProc?
It depends on the tool your team already works in. uProc also has an n8n node, so both platforms can call it. On Make, you get 2 action modules, Select a Tool and Make an API Call, one shared connection and the visual editor with Run once for testing. If your other automations already live in n8n, keeping uProc there avoids splitting your flows across two tools. If they live in Make, this integration covers the same need without leaving it.
Same platform

Other docs you might need on this stack.

Browse all integrations