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.

View on GitHub
Updated Sep 27, 2026Available asMCPCLIAPI

Description

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.

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.

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.

{ "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.

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

Run n8n-cli execution get.

Set $N8N_API_KEY in your environment first.

API (official)

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.

Built from these files in the repository

The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.

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.