AutoVerse Workflow ControllerInstall

Summary

Fetches a single n8n execution by ID through the n8n public API and returns its status record, optionally including full execution data.

Inputs

• executionId (required) — The execution to look up. Pick from a dropdown of the 5 pages of most recent executions (labelled with ID, status, workflow name and start time; cached ~30s), or supply an ID via expression. Empty value throws 'Enter an execution ID.'
• includeExecutionData — Defaults to false. When true, the request sets includeData=true so the response includes the node-level run data, not just metadata.

Output shape

One output item per input item, with json of the form { execution: }. The execution object is the raw API response (typically id, status, finished, mode, startedAt, stoppedAt, workflowId, and data when requested).

Requires the n8nApi credential (base URL plus API key/token). Requests retry up to 3 times with backoff on 408/425/429/5xx. Errors (e.g. unknown ID) throw a NodeApiError unless Continue On Fail is on, in which case an item with json.error is emitted. This is a single point-in-time read; it does not wait for completion (use Live Execution Polling for that).

Examples

Example 1: Check whether a sub-workflow run triggered earlier has finished, using the execution ID passed from a previous node.

Resource: Execution; Operation: Get Execution Status; Execution ID set by expression {{$json.executionId}}; Include Execution Data off.

Example 2: Inspect the full output data of a failed execution for debugging or alerting.

Execution ID chosen from the list or via expression; Include Execution Data on.

Links

• n8n community nodes installation guide