When viewing the execution details of a workflow that was triggered as a Sub-Workflow, n8n currently does not show which parent workflow initiated it. This makes it difficult to trace execution flow, understand context, or perform debugging across chained workflows.
I am requesting a feature that adds the Parent Workflow Execution ID (with a clickable link) to the Sub-Workflow execution view.
Why this is useful
-
Improved traceability: Quickly see which workflow triggered the sub-execution without digging through logs or searching manually.
-
Faster debugging: When troubleshooting execution issues, it’s essential to follow the chain from parent → sub-workflow → child executions.
-
Better observability for complex automation: Many n8n setups use orchestration workflows that call multiple sub-workflows. This feature would make it significantly easier to monitor and audit execution paths.
-
Parity with other automation tools: Many workflow/orchestration platforms expose call-chains to improve visibility.
Proposed behaviour
- In any Sub-Workflow execution, show a small section such as:
”Triggered by: Workflow Name”
”Parent Execution:#123456"(clickable link to parent execution) - Display this near the top of the execution details for easy visibility.
Impact
This simple addition dramatically improves the user experience when working with multi-workflow architectures, especially those using reusable workflows, orchestration patterns, approval flows, or complex agent-based systems.