251
All tools
n8nn

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)

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.

Ways in

RouteSourceCallRequiredDocs
MCPOfficial · remoteget_workflow_executionOAuthDocs
CLIOfficialn8n-cli execution getAPI key in $N8N_API_KEYDocs
APIOfficialGET /executions/{executionId}API key in $N8N_API_KEYDocs

Workflows using Get a workflow run

No workflows yet
No published workflow uses Get a workflow run yet.