n8n-check Saved call inspector

Follow your
returned items.

Select saved parent + child execution JSON. Compare the child's source path with the caller's recorded item links, right here in your browser.

Choose the whole saved call.

Select the parent and every referenced child from one n8n instance. Use complete includeData=true execution API responses.

How to get these files

File contents stay in this tab. Free, MIT-licensed. No installation.

Get the saved evidence.

  1. For the parent, save the JSON response from GET /api/v1/executions/<id>?includeData=true&ignoreDataSizeLimit=true using your local API client. Use both options for complete data beyond the instance's display-size limit.
  2. Follow saved metadata.subExecution.executionId references. Once-mode calls store them on the task; each-mode calls store them on returned items.
  3. Save each child's complete API response with the same options. Follow nested calls, then select all the files together above.

Workflow exports describe the workflow. This inspector takes saved execution responses, including workflowData and data.resultData.runData.

Collect from a parent ID.

Already have Node.js 24+? Download the local collector into your working folder. Set N8N_API_KEY in your local environment, then replace the instance URL and parent ID:

node n8n-fetch-bundle.cjs \
  https://your-n8n.example 123 \
  ./temp/saved-call-123

The GET-only script follows the saved child IDs. Use a fresh output directory, then choose its execution-*.json files above. If you select manifest.json too, the inspector keeps that acquisition receipt separate from execution data.

Collector source & CLI guide

Supported saved calls

Successful waiting Execute Workflow 1.2/1.3, with passthrough Execute Workflow Trigger 1.1/1.2. Nested once calls, each calls and recorded all-runs returns share the existing checker.

Missing or unsupported evidence returns incomplete with a reason. Source addresses retain execution, node, run, output and item.