Make

Let your agents work with your Make automations: browse organizations, teams, scenarios, execution logs, data stores, webhooks and connections, run, activate or deactivate scenarios, and add or replace data store records.

Connection

Authentication: API key (Make API token).
Required settings:
- Make zone — The start of your Make dashboard address: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com or us1.make.celonis.com.

In Make: click your avatar → Profile → API access → ”+ API token”. Name it, pick the organization and the scopes, then copy the token (shown once). Recommended scopes: organizations:read, teams:read, scenarios:read, scenarios:write, scenarios:run, datastores:read, datastores:write, hooks:read, connections:read. A token only works on its own zone: set the zone to the start of your Make dashboard address (e.g. eu1.make.com).See Make’s documentation.

Read actions (11)

Action	Description
`get_current_user`	Get the Make user the token belongs to. Also used as the credential probe. No arguments.
`get_scenario`	Get a scenario (name, team, active state, schedule, modules used; not the blueprint). scenarioId: integer, from list_scenarios.
`get_scenario_log`	Get one execution of a scenario. scenarioId: integer; executionId: string, the id from list_scenario_logs or returned by run_scenario.
`list_connections`	List the connections (app accounts) of a team: id, name, app, expiry. Read only, no credential. teamId: integer, required, from list_teams.
`list_data_store_records`	List the records of a data store; the answer has records [{key, data}], spec, count and pg. dataStoreId: integer, required, from list_data_stores. Optional pagination: pg[limit] (integer), pg[offset] (integer).
`list_data_stores`	List the data stores of a team. teamId: integer, required, from list_teams. Optional pagination: pg[limit] (integer), pg[offset] (integer), pg[sortBy] (string), pg[sortDir] (“asc” or “desc”); the answer carries a pg object.
`list_hooks`	List the webhooks and mailhooks of a team (name, type, enabled, scenarioId, queue size). The public URL is removed from the answer: it is a trigger anyone could call. teamId: integer, required, from list_teams.
`list_organizations`	List the organizations the token can see (ids are needed by list_teams). Optional pagination: pg[limit] (integer), pg[offset] (integer), pg[sortBy] (string), pg[sortDir] (“asc” or “desc”); the answer carries a pg object.
`list_scenario_logs`	List the executions of a scenario. scenarioId: integer, required. Optional: from and to (integers, Unix epoch in MILLISECONDS), status (integer: 1 = success, 2 = warning, 3 = error). Optional pagination: pg[limit] (integer), pg[offset] (integer), pg[sortBy] (string), pg[sortDir] (“asc” or “desc”); the answer carries a pg object.
`list_scenarios`	List scenarios. Give EXACTLY ONE of teamId (integer, from list_teams) or organizationId (integer, from list_organizations). Optional: isActive (boolean, true = only active scenarios), folderId (integer). Optional pagination: pg[limit] (integer), pg[offset] (integer), pg[sortBy] (string), pg[sortDir] (“asc” or “desc”); the answer carries a pg object.
`list_teams`	List the teams of an organization (team ids are needed by list_scenarios, list_data_stores, list_hooks and list_connections). organizationId: integer, required, from list_organizations.

Write actions (5)

Action	Description
`activate_scenario`	Activate a scenario (it then runs on its schedule or trigger). scenarioId: integer, required. No other argument.
`add_data_store_record`	Add a record to a data store. Arguments: dataStoreId (integer, required); key (string, optional, generated when omitted); data (object, required, fields following the structure of the data store, see spec in list_data_store_records).
`deactivate_scenario`	Deactivate a scenario (stops it if it is running). scenarioId: integer, required. No other argument.
`replace_data_store_record`	REPLACE a whole data store record: fields left out of data are emptied. Arguments: dataStoreId (integer, required); key (string, required, the record key from list_data_store_records); data (object, required, the complete new content following the data store structure).
`run_scenario`	Run a scenario once. Needs the token scopes scenarios:read, scenarios:write and scenarios:run. Arguments: scenarioId (integer, required); data (object of input values, only if the scenario defines inputs); responsive (boolean: true waits for the end of the run, about 40 seconds at most, and returns status and executionId; false or omitted returns executionId at once). 429 with code IM310 = the organization is paused (usage limit).

Permissions

Every action above must be explicitly granted to an agent before it can be used. See Permissions for the grant model and Security for how credentials are protected.

Last reviewed against the provider API: October 2026.

Using integrations

Communication

Scheduling

Project management

Docs & design

Files & storage

CRM & sales

Customer support

HR & recruiting

Commerce & billing

Developer tools

Observability & analytics

AI & media

Connection

Read actions (11)

Write actions (5)

Permissions

​Connection

​Read actions (11)

​Write actions (5)

​Permissions

Connection

Read actions (11)

Write actions (5)

Permissions