n8n Subworkflow Dependency Graph & Auto-Tagging

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: Fetching all workflows and identifying which ones execute others. Verifying that referenced subworkflows exist. Building a caller-subworkflow dependency graph for visibility. Automatically tagging sub-workflows based on their parent workflows. Providing a chart visualization to highlight the most-used sub-workflows. Set Up Steps Estimated time: ~10–15 minutes Set up n8n API credentials to allow

Help me set up the n8n workflow "n8n Subworkflow Dependency Graph & Auto-Tagging" (https://n8n.io/workflows/2939). It uses: HTTP Request, Code, QuickChart. Import the template JSON into my n8n instance, list every credential I need to create, and walk me through testing it.