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.

Note: A run that outlasts the call (40 seconds on the API with responsive: true, 25 over MCP) keeps going: look it up by its executionId, or get the result at a callbackUrl. Scenarios don't run while their team or organization is paused over its limits.

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

Note: {zone_url} is your organization's zone from the Make dashboard's address bar, such as eu1.make.com.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.