Robocorp Make integrationAutomate Robocorp with Make.
Can a form, a spreadsheet row or a new deal kick off a Robocorp robot? The Robocorp Make integration gives you 3 modules: two actions and one search. This guide shows how to link your workspace, which module does what, and how to build a first scenario that starts a process for you.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Robocorp Make integration do for you?
The Robocorp Make integration lets a Make scenario, the automation you build in Make as a chain of bricks called modules, start a Robocorp process and then read the work items that process produced. Your robots stay in Robocorp; Make decides when they run and where their results go next.
Robots that start on a business event. An operations team can let a record in another app, say a row added in a sheet or an entry in a CRM, fire Start Process instead of someone opening Control Room to press a button. The robot runs as usual, only the launch changes.
Results that travel on their own. Once a run is done, Get Work Items looks up the output work items of that run. A finance assistant could then push each item into a spreadsheet or a message, without copying anything by hand.
Calls the listed modules do not cover. With only three modules, Make an API Call matters here: it reaches any endpoint of the Robocorp API through the same connection.
What Make does not give you: Robocorp has no trigger module in Make, so nothing in Robocorp can start a scenario by itself; the scenario begins on another app or on a schedule. The Make documentation for this app also warns that it is AI-generated from Robocorp docs, so check important details with Robocorp. If you are still choosing a tool, the n8n vs Make comparison and the Make review help, and Make troubleshooting covers failed runs.
How do you connect Robocorp to Make?
- 01
Collect three values in Control Room
Log in to Robocorp and open the Control Room dashboard. Pick your workspace in the workspace selector, go to Workspace settings, then the API access tab. Copy the API URL, the API key and the Workspace ID shown there.
- 02
Open the connection window in Make
In your scenario, add any Robocorp module and click Create a connection. A connection is your Robocorp account linked to Make once, then reused by every Robocorp module. The Connection name field is optional; a clear name helps if you run several workspaces.
- 03
Paste the credentials and save
Enter the values you copied from Control Room, or follow the instructions Make shows on screen, and save. Your account needs access to a workspace and a workspace scoped API key, so check that before you start.
Build your first scenario with Robocorp
GoalWhen a new request lands in another app, Make starts a Robocorp process to handle it.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the +. Robocorp has no trigger, so this first module comes from the app where requests arrive, such as a sheet or a form tool.
- 02
Set up the starting module
Search that app, pick its trigger and link its account. Make then lists the sheets or objects it can read, so you choose the source instead of typing it.
- 03
Add Start Process
Click the + on the right of the first module, search Robocorp and choose Start Process. Create the connection, then map data from the first module into the fields Make displays.
- 04
Test with Run once
Click Run once. Make executes the scenario one time and shows the bundles, the items passed from one module to the next, that each module received. Check in Control Room that the run started.
- 05
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From here, each new request launches the robot without anyone logging in.
What the Robocorp modules do
Robocorp gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
This module reaches any endpoint of the Robocorp API from your scenario and reuses the connection you already created, so you never manage a second key.
Start Process
ActionIn Make“Triggers a process”
Start Process launches a Robocorp process from Make, so a robot begins its job the moment your scenario reaches this step rather than when someone clicks in Control Room.
Get Work Items
SearchIn Make“Gets output work items based on processId and processRunId, which are available e.g. with a webhook.”
Get Work Items brings back the output work items of a given run, using its process ID and process run ID, so the data a robot produced can move on to other apps.
Need help automating Robocorp with Make?
A person reads every message.
