Developer tools
Make in your product and your AI agents, through one API
The Make toolkit covers organizations, teams, scenarios, execution logs and incomplete executions of one Make zone. Your customer connects once with an API key, and your product or AI agent calls each operation through Connect, which stores the credential and logs every execution.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/make_activate_scenario/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"scenarioId": 1
}
}How it works
From a connected customer to the first Make call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Make account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Make.
Trigger automations from your product
Run a customer's scenario when something happens in your SaaS, and wait for the status and outputs with responsive true.
Control scenarios from a settings page
Show a customer's scenarios, rename them and switch them on or off, so users manage automations without opening Make.
Failed-run recovery for agents
Let an AI agent list the logs and incomplete executions of a scenario, read the error and the module that caused it, and retry the run.
Tools
12 Make tools
- List organizationsGETLists the organizations of the user, each with its id and name. The id is the organizationId the other tools ask for.
- List teamsGETLists the teams of an organization, each with its id and name. The id is the teamId of List scenarios.
- List scenariosGETLists the scenarios of a team or of a whole organization: send teamId or organizationId, never both. Each item has the id and name of the scenario.
- Get scenarioGETReturns the details of one scenario, such as its name, team, scheduling and whether it is active.
- Update scenarioPATCHRenames a scenario. The name does not need to be unique.
- Activate scenarioPOSTActivates a scenario so it runs on its schedule. A scenario scheduled at regular intervals also runs right away.
- Deactivate scenarioPOSTDeactivates a scenario, which stops its schedule and the run in progress, if there is one.
- Run scenarioPOSTRuns an active scenario now, which uses operations of the organization. Returns the executionId; with responsive true it waits up to 40 seconds and also returns the status and the scenario outputs. A paused organization or team answers 429 with code IM310.
- List scenario logsGETLists the execution logs of a scenario, newest first, each with the execution id, status, duration, operations and transfer.
- Get scenario executionGETReturns the status of one execution of a scenario, with the scenario outputs, or the error and the module that caused it.
API key
Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.
When connecting, your customer also enters {zone}: the address of their account on the app's API.
Questions about the Make toolkit
Do I need to build against the Make API?
No. Connect ships 12 Make tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Make account?
With the mode the toolkit accepts: API key. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
See Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
