Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
ETL PipelineIntermediate

Workflow Analytics and Reporting

Workflow Analytics and Reporting is a 28-node automation blueprint connecting n8n API. Inspect its trigger, execution graph, branches, and implementation requirements.

n8n API

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

28

Nodes

29

Edges

6

Zones

System stack

1 integrations

  • n8n API
Workflow Analytics and Reporting interactive execution graphStructural view of 28 workflow nodes and 29 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Execute Workflow Trigger. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.Execute Workflow TriggerTRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTn8n-get-workflows. integration node, n8n. 2 incoming and 1 outgoing connections.n8n-get-workflowsINTEGRATIONN8N2 IN / 1 OUTWhen clicking "Test workflow". trigger node, manualTrigger. 0 incoming and 1 outgoing connections.When clicking "Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTRequest HTML dashboard. trigger node, webhook. 0 incoming and 1 outgoing connections.Request HTML dashboardTRIGGERWEBHOOK0 IN / 1 OUTPrepare JSON object. integration node, executeWorkflow. 1 incoming and 1 outgoing connections.Prepare JSON objectINTEGRATIONEXECUTEWORKFLOW1 IN / 1 OUTRequest xsl template. trigger node, webhook. 0 incoming and 1 outgoing connections.Request xsl templateTRIGGERWEBHOOK0 IN / 1 OUTTemplate elements. transform node, set. 1 incoming and 1 outgoing connections.Template elementsTRANSFORMSET1 IN / 1 OUTget-nodes-via-jmespath. transform node, set. 1 incoming and 1 outgoing connections.get-nodes-via-jmespathTRANSFORMSET1 IN / 1 OUTConvert to XML. integration node, xml. 1 incoming and 1 outgoing connections.Convert to XMLINTEGRATIONXML1 IN / 1 OUTFinal template. transform node, set. 1 incoming and 1 outgoing connections.Final templateTRANSFORMSET1 IN / 1 OUTworkflows-section. transform node, set. 1 incoming and 5 outgoing connections.workflows-sectionTRANSFORMSET1 IN / 5 OUTCreate HTML. integration node, html. 1 incoming and 1 outgoing connections.Create HTMLINTEGRATIONHTML1 IN / 1 OUTRespond to Webhook2. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.Respond to Webhook2TRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTglobals-section. transform node, set. 1 incoming and 1 outgoing connections.globals-sectionTRANSFORMSET1 IN / 1 OUTnodes-section. transform node, code. 1 incoming and 1 outgoing connections.nodes-sectionTRANSFORMCODE1 IN / 1 OUTtags-section. transform node, code. 1 incoming and 1 outgoing connections.tags-sectionTRANSFORMCODE1 IN / 1 OUTwebhook-section. transform node, code. 1 incoming and 1 outgoing connections.webhook-sectionTRANSFORMCODE1 IN / 1 OUTMove Binary Data. integration node, moveBinaryData. 1 incoming and 1 outgoing connections.Move Binary DataINTEGRATIONMOVEBINARYDATA1 IN / 1 OUTSort-workflows. integration node, sort. 1 incoming and 1 outgoing connections.Sort-workflowsINTEGRATIONSORT1 IN / 1 OUTAggregate-workflows. transform node, aggregate. 1 incoming and 1 outgoing connections.Aggregate-workflowsTRANSFORMAGGREGATE1 IN / 1 OUTSort-nodes. integration node, sort. 1 incoming and 1 outgoing connections.Sort-nodesINTEGRATIONSORT1 IN / 1 OUTAggregate-nodes. transform node, aggregate. 1 incoming and 1 outgoing connections.Aggregate-nodesTRANSFORMAGGREGATE1 IN / 1 OUTSort-tags. integration node, sort. 1 incoming and 1 outgoing connections.Sort-tagsINTEGRATIONSORT1 IN / 1 OUTAggregate-tags. transform node, aggregate. 1 incoming and 1 outgoing connections.Aggregate-tagsTRANSFORMAGGREGATE1 IN / 1 OUTSort-whooks. integration node, sort. 1 incoming and 1 outgoing connections.Sort-whooksINTEGRATIONSORT1 IN / 1 OUTAggregate-whooks. transform node, aggregate. 1 incoming and 1 outgoing connections.Aggregate-whooksTRANSFORMAGGREGATE1 IN / 1 OUTRespond to Webhook. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.Respond to WebhookTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTFinal-json. decision node, merge. 5 incoming and 0 outgoing connections.Final-jsonDECISIONMERGE5 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph 51031869007481abEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

6 nodes

Events, schedules, and unconnected roots that can start an execution.

When clicking "Test workflow"

Trigger

Execute Workflow Trigger

Trigger

Respond to Webhook

Trigger

Respond to Webhook2

Trigger

Request HTML dashboard

Trigger

Request xsl template

Trigger

02

Data & operations

21 nodes

Transformations and external-system actions that move the work forward.

nodes-section

Transform

workflows-section

Transform

tags-section

Transform

globals-section

Transform

Convert to XML

Integration

Create HTML

Integration

+ 15 more in system map
03

Intelligence & routing

1 node

Model calls and control points that interpret, branch, or govern the run.

Final-json

Decision

04

Terminal actions

0 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

No nodes observed in this zone

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
exact
Quality score
11 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas