n8n subworkflow dependency graph & auto-tagging
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 27 nodes and runs when an HTTP GET request hits its webhook URL (plus 2 other triggers). Along the way it connects QuickChart.
How it runs
Trigger: When an HTTP GET request hits its webhook URL (plus 2 other triggers).
- GET all workflows (n8n): uses n8n
- List callers of subworkflows (Code): runs custom JavaScript code
- Exclude uncalled workflows (Filter): keeps only the items that match a condition
- GET workflow(s) (n8n): get
- Exclude missing workflows (Filter): keeps only the items that match a condition
- Count callers and identify new callers (Edit Fields (Set)): sets 5 fields: id, name, callers…
- Loop through workflows (Loop Over Items (Split in Batches)): loops over the items in batches
- Combine dependency graph values into labels (Aggregate): combines items into one
- Format workflow relationship data for rendering (Code): runs custom JavaScript code
- SET instance_url (Edit Fields (Set)): sets 1 field: instance_url
…plus 14 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (15)
- HTTP Request
n8n-nodes-base.httpRequest - n8n
n8n-nodes-base.n8n - Code
n8n-nodes-base.code - Filter
n8n-nodes-base.filter - Schedule Trigger
n8n-nodes-base.scheduleTrigger - n8n Trigger
n8n-nodes-base.n8nTrigger - Edit Fields (Set)
n8n-nodes-base.set - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - If
n8n-nodes-base.if - Split Out
n8n-nodes-base.splitOut - Merge
n8n-nodes-base.merge - Aggregate
n8n-nodes-base.aggregate - QuickChart
n8n-nodes-base.quickChart - Webhook
n8n-nodes-base.webhook - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
How it Works As n8n instances scale, teams often lose track of sub-workflows—who uses them, where they are referenced, and whether they can be safely updated. This leads to inefficiencies like unnecessary copies of workflows or reluctance to modify existing…