---
ref: tool:make/get-scenario-run
name: Get a scenario run
company: company:make
workflows: []
access: [mcp, cli, api]
tags: [capability:automate-workflows, category:automation, has:api, has:cli, has:mcp]
docs: https://developers.make.com/api-documentation/api-reference/scenarios/logs
updated: 2026-09-27
---

# Get a scenario run

Returns one scenario run's status, such as running, success, warning or error, and its outputs or error once it ends.

Pass the `executionId` a run returned, with the scenario's ID. Poll until the
status is no longer `RUNNING`: a run whose call timed out keeps going in Make
for up to 40 minutes.

## 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.

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

Call the MCP tool `executions_get`.

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

### CLI (official)

Install the command, then confirm it runs.

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

Run `make-cli executions get`.

Set `$MAKE_API_KEY` in your environment first.

### API (official)

- Base URL: https://{zone_url}/api/v2
- Endpoint: `GET /scenarios/{scenarioId}/executions/{executionId}`
- 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.