Create the main JSON object with the workflow statistics

• globals - general information (# of workflows, active workflows, total trigger count)
• wf_stats - summary per workflow (number or nodes, unique nodes, list of nodes and tags)
• nodes-section - summary per node (number of workflows that use a node and their URLs)
• tags-section - summary per tag (number of workflows that use a node and their URLs)
• webhook-section - lists all webhook endpoints of the instance and shows the workflow URLs

You can use this JSON in BI tools to create a custom dashboard

Learn JS tips & tricks

Instead of just using one Code node, the workflow contains several nodes with useful advanced tricks.

JMESPath

• Make a simple array of strings out of a complex array: $jmespath($json,'nodes[*].type')
• Extract values based on condition: $jmespath($input.all(),'[?json.wf_stats.wf_active == true]')

Map and arrow functions

• Perform operation on each array element: .map(item => (item.split('.').pop().toUpperCase() ))
• Calculate sum of values from an array: .reduce((accumulator, currentValue) => accumulator + currentValue, 0)

Create an array with only unique values

• [...new Set($json.nodes_array)]

Date-time conversions with the Luxon library:

• DateTime.fromISO($json.createdAt).toFormat('yyyy-MM-dd HH:mm:ss')

Template literals (Template strings) for creating strings in JS

• wf-${$json.id}

DO NOT RUN THIS

This webhook is needed to comply with the CORS policy of modern browsers.

It generates XML template and serves it using your n8n URL

XSLT template is created with 2 Set nodes:

1. Template elements node defines each section of the Dashboard
2. Final template node puts everything together
3. Bootstrap 5.3 styling is added. You can save the .css and .js files on your server. Right now a CDN version of the librarly is used.

Additional section to create a standalone dashboard via XLM templates

This section is not required if you only need a JSON

IMPORTANT!

This webhook is not protected. Everyone who knows the URL endpoint can get access to the Dashboard. Please consider adding authentication.

1. Request HTML dashboard node runs that main section of the workflow
2. It converts the JSON into an XML structure
3. A final HTML page is created with the link to an XML stylesheet (this stylesheet controls the look of the dashboard)
4. The resulting page is returned via Respond to Webhook node

IMPORTANT NOTE FOR CLOUD USERS

Since the cloud version doesn't support environmental variables, please make the following changes:

1. get-nodes-via-jmespath node. Update the instance_url variable: enter your n8n URL instead of {{$env["N8N_PROTOCOL"]}}://{{$env["N8N_HOST"]}}
2. Create HTML node. Please provide the n8n instance URL instead of {{ $env.WEBHOOK_URL }}

Workflow stats

Purpose and structure

This folder contains the Workflow stats workflow. Its executable nodes use aggregate, code, executeWorkflow, executeWorkflowTrigger, html, manualTrigger, merge, moveBinaryData, n8n, respondToWebhook, set, sort, webhook, xml. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When clicking "Test workflow", Execute Workflow Trigger, Request HTML dashboard, Request xsl template

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/1401_Code_Webhook_Automate_Webhook.json MIT; preserve source notices.