---
ref: tool:n8n/get-workflow-run
name: Get a workflow run
company: company:n8n
workflows: []
access: [mcp, cli, api]
tags: [capability:automate-workflows, category:automation, has:api, has:cli, has:mcp]
docs: https://docs.n8n.io/connect/n8n-api/executions
updated: 2026-09-27
---

# Get a workflow run

Returns one n8n execution's status and start and stop times and, when asked, the data each node produced.

It returns metadata only unless you pass `includeData`. The MCP tool also needs
the `workflowId`, and takes `nodeNames` or `truncateData` to keep the returned
data small.

## 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": { "n8n": { "url": "https://{your-n8n-domain}/mcp-server/http" } } }
```

Call the MCP tool `get_workflow_execution`.

Server URL: https://{your-n8n-domain}/mcp-server/http

### CLI (official)

Install the command, then confirm it runs.

```sh
npm install -g @n8n/cli
n8n-cli --version
```

Run `n8n-cli execution get`.

Set `$N8N_API_KEY` in your environment first.

### API (official)

- Base URL: https://{your-domain}/api/v1
- Endpoint: `GET /executions/{executionId}`
- Auth: send the header `X-N8N-API-KEY: $N8N_API_KEY`
- Docs: https://docs.n8n.io/connect/n8n-api

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.