UiPath on Make Enterprise
UiPath is an RPA or automation platform. Bots and workflows that Make can start, feed or hand work to. Here is what Make lists for it, what we build around it, and what to settle before you automate it.
What does Make list for UiPath?
Make's page lists 3 actions by name.
Actions
- Add an Item to a Queue
- Make an API Call
- Start a Job
Module lists change as Make updates the app. Treat this as a snapshot and confirm on Make's page before you scope work.
What do we build around UiPath?
These are the kinds of scenarios we build for rpa and automation platforms. They describe our work, not features of UiPath.
- Triggers that start a bot when a business event happens elsewhere
- Results from a bot passed on to the next system
- A single place to see which automation does what
- Hand-offs to a person when a bot cannot finish
Example flows
- A new request in a business system starts the bot and waits for its result
- A failed bot run creates a ticket with the run details
- A finished job updates the record that asked for it
What should you settle before automating UiPath?
Settle these before the first production scenario so builders can start without waiting on a later security review.
- Which tool owns each process, so the same job is not automated twice
- How a bot failure is reported and who picks it up
- Which credentials the bot and the scenario each hold
- How changes to either side are tested together
Platform-level controls such as SSO, roles, encryption and log retention are Make's own published terms; see make.com/security and our Make Enterprise page for how we scope against them. Make describes the Enterprise plan itself at make.com/enterprise.
Frequently asked questions
Can Make connect to UiPath?
Yes. Make has a UiPath app, and its page states that it is supported and maintained by Make. It is listed in Make's Enterprise integrations category. The modules and names on this page are what Make shows on its own UiPath page as of November 5, 2026, so check Make's page for the current list.
What do you build around UiPath?
We build the scenarios around it: triggers that start a bot when a business event happens elsewhere; results from a bot passed on to the next system; a single place to see which automation does what. Scope is set on a call, and each scenario is documented in plain language before hand-over.
What should we decide before automating UiPath?
Start with the guardrails: which tool owns each process, so the same job is not automated twice; how a bot failure is reported and who picks it up; which credentials the bot and the scenario each hold. Settling these first lets builders start without waiting on a security review later.
Does the connection need UiPath admin access?
That depends on what the scenarios do and on UiPath's own permission model. We aim for a dedicated service account with the narrowest role that works, and we record which scenarios write and which only read. Your UiPath administrator decides what that account may reach.
Consultants in a Box is a Make partner. This page is written by us and is not published by Make or by UiPath's vendor. UiPath, Make and related names are trademarks of their owners. Statements about Make's platform are the ones Make publishes.
Planning to automate UiPath?
Book a call. We map your systems to the pages here, agree the guardrails and give you a written scope and price afterwards.