Run a scenario

Run a scenario

Runs an active Make scenario with the inputs you pass and returns the run's status, execution ID and, when the scenario defines them, its outputs.

Pass the scenario's inputs in data (--data on the CLI). On the API, responsive: true waits for the run to finish (--responsive on the CLI); a run longer than 40 seconds times out the call but keeps going, and callbackUrl receives the result when it ends. On the MCP server a run that outlasts the tool timeout (25 seconds over OAuth) returns an executionId: check it with executions_get. A scenario doesn't run while its organization or team is paused for going over its operations or data transfer limit.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "make": { "url": "https://mcp.make.com" } } }

Call the MCP tool scenarios_run.

Server URL: https://mcp.make.com

CLI (official)

Install the command, then confirm it runs.

npm install -g @makehq/cli
make-cli --version

Run make-cli scenarios run.

Set $MAKE_API_KEY in your environment first.

API (official)

• Base URL: https://{zone_url}/api/v2
• Endpoint: POST /scenarios/{scenarioId}/run
• Auth: send the header Authorization: Token $MAKE_API_KEY
• Docs: https://developers.make.com/api-documentation

Before doing anything else, make one read-only call to confirm access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data.
• Never print API keys.