## 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 ones. This workflow solves that problem by:
1. Fetching all workflows and identifying which ones execute others.
2. Verifying that referenced sub-workflows exist.
3. Building a caller-subworkflow dependency graph for visibility.
4. Automatically tagging sub-workflows based on their parent workflows.
5. Providing a chart visualization to highlight the most-used sub-workflows.
## Set Up Steps
*Estimated time: ~10-15 minutes*
1. Set up n8n API credentials to allow access to workflows and tags.
2. Replace instance_url with your n8n instance URL.
3. Run the workflow to analyze dependencies and generate the graph.
4. Review and validate assigned tags for sub-workflows.
5. (Optional) Enable pie chart visualization to see the most-used sub-workflows.
This workflow is essential for enterprise teams managing large n8n instances, preventing workflow duplication, reducing uncertainty around dependencies, and allowing safe, informed updates to sub-workflows.
Platform
n8n
Category
Business Operations & ERPs
Price
Free
Creator
Ludwig
if
n8n
set
code
merge
filter
webhook
splitOut
aggregate
n8nTrigger
How to import this workflow into n8n
1Purchase or download the workflow to get the n8n workflow JSON file.
2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
3Open each node marked with a credential warning and connect your own accounts and API keys.
4Run the workflow once manually to verify the data flow, then toggle it to Active.