Resources · Make integration

UiPath Make integrationAutomate UiPath with Make.

What if your UiPath processes started whenever the rest of your stack had work for them? The UiPath Make integration gives you 3 action modules to start jobs and feed queues. This guide walks you through the connection and a first working scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the UiPath integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the UiPath Make integration let you automate?

The UiPath Make integration lets Make act on your UiPath Orchestrator account: it can start a job for a process you pick, drop an item into a queue, or call any other endpoint of the UiPath API. Make is a no-code tool where you build a scenario, the automation itself, by chaining modules, each one a brick that does one thing.

Hand work to a robot from a form or a CRM. A new request lands in another app, and Add an Item to a Queue places it in the UiPath queue your process works from. Each item that flows between modules is called a bundle, so one request becomes one queue item.

Launch a process when a business event happens. Instead of starting an automation by hand in Orchestrator, Start a Job triggers the process you selected as soon as the previous module in your scenario has something for it.

Reach the rest of the API. Need something the two dedicated modules do not cover? Make an API Call reuses the same connection to reach any endpoint, as long as the right scopes are granted.

Two limits to know before you start. UiPath has no trigger in Make, so a scenario never starts from a UiPath event: it starts from another app or from its schedule. And the app is reserved to the Make Enterprise plan; the Make pricing page explains how the plans differ. If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, and the Make training covers scenario building from scratch.

Connect

How do you connect UiPath to Make?

  1. 01

    Create an external application in UiPath

    In UiPath, open the Product launcher icon, then Admin, External applications and + Add application. Add the Orchestrator API Access resource with the scopes the doc lists, leave the redirect URL empty, then copy the App ID and App Secret.

  2. 02

    Collect your organization ID and tenant name

    Your organization ID sits in the URL of your UiPath Home, right after cloud.uipath.com/. For the tenant, go back to Admin, click the tenant name in the sidebar, open Settings and copy the Name value.

  3. 03

    Fill in the connection in Make

    Add a UiPath module and click Create a connection. Pick UiPath Cloud (Client Credentials) as the connection type, paste the organization ID, tenant name, Client ID and Client Secret, then click Save. That connection is your UiPath account linked to Make once, for every module.

First scenario

Your first scenario: send work to UiPath and start the robot

GoalWhen a new request arrives in another app, Make adds it to a UiPath queue and starts the matching job.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since UiPath has no trigger, pick the module of the app where requests arrive as the first module.

  2. 02

    Add the queue module

    Click the + on the right, search for UiPath and choose Add an Item to a Queue. Create the connection, then pick the queue from the list Make reads from your account.

  3. 03

    Map the request data

    Fill the module fields with data from the first module: Make shows what the previous bundle holds, so you click values instead of typing them.

  4. 04

    Start the job

    Add Start a Job after the queue module and select the process that should handle the work. Point it at the process built to read that queue.

  5. 05

    Test, schedule and switch on

    Click Run once and check the bundles each module received. Then set the schedule on the first module, every 15 minutes by default, and switch the scenario on.

Modules

What the UiPath modules do

UiPath gives you 3 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Job

1 module
UiPath1

Start a Job

Action

In Make“Starts a UiPath job by triggering a selected process.”

Start a Job launches a UiPath job for the process you choose, so your robot goes to work right when your scenario decides it should. No one has to open Orchestrator and press start.

When to use it
after a module from another app confirms that work is ready, such as a signed contract or an approved request.
Watch out
each run of this module is one operation, the unit Make counts on your plan, so place it after any filter.

Queue

1 module
UiPath2

Add an Item to a Queue

Action

In Make“Adds items to a UiPath queue.”

Add an Item to a Queue hands your robots a new piece of work: the data from your scenario becomes an item in the UiPath queue you pick. Your process then treats queue items the way it was designed to.

When to use it
when requests arrive one by one from a form, an inbox or a CRM and should wait their turn instead of starting a job each time.
Watch out
one bundle gives one queue item, so a list of ten records adds ten items.

Other

1 module
UiPath3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call gives you access to UiPath endpoints that have no dedicated module, while reusing the connection you already set up. It is your fallback when Start a Job and Add an Item to a Queue are not enough.

When to use it
when you need data or an operation from the UiPath API that the two other modules do not offer.
Watch out
the connection must carry the scopes of that call, added in the Additional Scopes field, otherwise UiPath refuses the request.
Need help

Need help automating UiPath with Make?

A person reads every message.

FAQ

UiPath and Make: frequent questions

01Is the UiPath Make integration free?
No. UiPath is one of the enterprise apps in Make, and those are reserved to the Enterprise plan. The Free plan covers the standard apps, more than 3,000 of them, with 2 active scenarios, at least 15 minutes between scheduled runs and 5 minutes of execution per run, but it does not unlock UiPath. Paid plans are Core, Pro, Teams and Enterprise, and usage is counted in credits, which are operations, per month. You also need your own UiPath account, since Make only connects to it.
02What do you need to connect UiPath to Make?
A UiPath account, plus four values from it. In UiPath Admin, create an external application with Orchestrator API Access and the scopes the Make documentation lists, then copy its App ID and App Secret. Note your organization ID from the URL of your UiPath Home, and copy the tenant name from the tenant settings. In Make, choose the UiPath Cloud (Client Credentials) connection type, paste those values and click Save. If Make prompts you, authenticate and confirm access.
03Can a UiPath event start a Make scenario in real time?
No. UiPath has no trigger module in Make, neither scheduled nor instant, so no UiPath event can start a scenario. The scenario begins with a module from another app, for example a new form entry or a new CRM record, or it runs on its own schedule, which is every 15 minutes by default on a new scenario. The Free plan allows 15 minutes at minimum between scheduled runs, paid plans go down to 1 minute. The UiPath modules then act further along the flow.
04What if a UiPath module is missing in Make?
Use Make an API Call. It calls any endpoint of the UiPath API with the same connection as the other modules, which covers what Start a Job and Add an Item to a Queue do not handle. The one condition is on the connection side: the Additional Scopes field must list the scopes each call needs, as described in the UiPath API documentation. If you also use Whitelisted Scopes under the advanced settings, keep OR.Settings or OR.Settings.Read in it, or the integration may stop working.
05Should you use Make or n8n for UiPath?
It depends on the tool your team already runs and on what you want to do. On the Make side, UiPath comes with three modules: start a job, add a queue item, and a generic API call, and it requires the Enterprise plan. The same app often has an n8n node too, so check which modules each tool offers for your case before deciding. The comparison page linked above sets out the criteria side by side, without declaring a winner in advance.
Same platform

Other docs you might need on this stack.

Browse all integrations