by n8n
Get a workflow run
Returns one n8n execution's status and start and stop times and, when asked, the data each node produced.
Updated Sep 27, 2026
get-workflow-run.md
Get a workflow run
Returns one n8n execution's status and start and stop times and, when asked, the data each node produced.
Note: Returns metadata only unless you pass includeData. The MCP tool also needs the workflowId.
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": { "n8n": { "url": "https://{n8n_host}/mcp-server/http" } } }
Call the MCP tool get_workflow_execution.
Server URL: https://{n8n_host}/mcp-server/http
Note: {n8n_host} is your instance's domain, such as acme.app.n8n.cloud. An owner or admin turns on Settings > Instance-level MCP first.
CLI (official)
Install the command, then confirm it runs.
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://{n8n_host}/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
Note: {n8n_host} is your instance's domain, such as acme.app.n8n.cloud. The API is not available during the free trial.
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.