n8n Flowcharts | Subflow 1

Workflow Overview This workflow functions as a comprehensive analytics and reporting tool for an n8n instance. It is designed as a subflow, meaning it's intended to be called by another workflow. Its primary purpose is to gather data on every workflow within the instance, process it, and then aggregate it into a single, structured JSON object. This final object contains detailed statistics about workflows, node usage, and tag distribution, making it an invaluable tool for instance administration, maintenance, and understanding usage patterns. Technologies & Automation - n8n: The core platform for orchestration. The workflow uses the n8n node to interact with its own instance's API. - Data Transformation: Extensive use of n8n's built-in data manipulation nodes, including Set, Code, Sort, Aggregate, and Merge. - JavaScript & JMESPath: The Code node uses JavaScript for complex data restructuring (pivoting data), while the Set node uses JMESPath expressions for efficient data extraction and filtering from the JSON objects returned by the n8n API. - Automation Value: This workflow automates the time-consuming and complex task of auditing an n8n instance. Instead of manually checking each workflow for its nodes, tags, and status, this subflow generates a complete, sorted, and aggregated report in seconds. This provides immediate insights into: - Which nodes are most/least used across the instance. - How workflows are organized via tags. - Overall instance health (total vs. active workflows, trigger counts). - A master list of all workflows, sortable by recent activity. Extensive Analysis The workflow executes in several parallel branches to process and aggregate data efficiently. H3: Execute Workflow Trigger This is the entry point, indicating the workflow is designed as a subflow to be called by a parent workflow. It passes any initial data to the next step. H3: n8n-get-workflows This node uses the internal n8n API to perform its core function: it fetches a complete list of every workflow present on the n8n instance. Each workflow is returned as a separate item, containing all its metadata.