✨ $500 AI Visibility Audit — live at Spurlock Studios. Book the audit

Operations & Systems

n8n Flowcharts | Subflow 2

This n8n subflow is triggered by another workflow. It prepares data, converts JSON to XML, then embeds the XML into an HTML structure referencing an external XSLT stylesheet via a webhook. The resulting HTML/XML data is converted to binary, and the subflow signals completion.

Built · ~4 hours saved per week

Workflow Overview Purpose & Automation Value This workflow functions as a dynamic, self-documenting utility. Its primary purpose is to generate a visual, browser-renderable flowchart of its own structure. When executed, it fetches its own workflow data (the nodes and connections), converts it into an XML format, and cleverly links it to an XSLT stylesheet. The key value this automation provides is the ability to create live, interactive documentation or dashboards for n8n workflows. Instead of manually creating diagrams in external tools, this subflow can be called by any other workflow to instantly generate a visual representation, ensuring the documentation is always up-to-date with the actual workflow logic. Technologies Used - n8n: The core automation platform. - JSON: The native format for storing n8n workflow data. - XML: The target data format for the workflow structure. - XSLT (Extensible Stylesheet Language Transformations): A styling language for XML. It is used via a webhook to transform the raw workflow XML data into a visual HTML flowchart when opened in a browser. - Webhooks: Used to serve the XSLT stylesheet that renders the final visualization. \\\ Node-by-Node Analysis H3: When Executed by Another Workflow (ExecuteWorkflowTrigger) - Purpose: This is the starting point of the workflow. As a trigger node, it allows this entire flow to be run as a "sub-workflow" called by another, parent workflow. - Configuration: It is configured to accept a workflow ID as an input parameter from the calling workflow, although this specific input is not directly used in the subsequent nodes. The flow instead uses the $workflow.id expression to get its own ID. H3: Prepare JSON object (Execute Workflow) - Purpose: This node executes a separate, unspecified workflow. Its goal is to retrieve the JSON definition (nodes, connections, settings) of the current workflow. - Configuration: It is dynamically configured to pass its own workflow ID (={{ $workflow.id }}) to the workflow it calls. This is a common n8n pattern where a "helper" workflow is used to access the n8n API and fetch the detailed structure of another workflow by its ID.

Tags: n8n, Data Transformation, Content Creation

Integrations: Sub-workflow

Related automations

Back to the Automation Library