Monitor workflow audits and failures with InfluxDB dashboard
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 24 nodes and runs on a schedule (every day at 05:00) (plus 1 other trigger). It uses only n8n's built-in nodes.
How it runs
Trigger: On a schedule (every day at 05:00) (plus 1 other trigger).
- Influx Globals (Edit Fields (Set)): sets 3 fields: influx_url, influx_org, influx_bucket
- Credentials Audit (n8n): generate (audit)
- Nodes Audit (n8n): generate (audit)
- Database Audit (n8n): generate (audit)
- Filesystem Audit (n8n): generate (audit)
- Instance Audit (n8n): generate (audit)
- Get Failed Executions (n8n): work with execution
- Get Active Workflows (n8n): uses n8n
- Pull Report Data and Risk Credentials (Edit Fields (Set)): sets 2 fields: report, risk
- Pull Report Data and Risk Nodes (Edit Fields (Set)): sets 2 fields: report, risk
…plus 12 more steps. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - n8n
n8n-nodes-base.n8n - Split Out
n8n-nodes-base.splitOut - Edit Fields (Set)
n8n-nodes-base.set - Summarize
n8n-nodes-base.summarize - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Merge
n8n-nodes-base.merge - HTTP Request
n8n-nodes-base.httpRequest
From the author
Who is it for This workflow is for anyone who is using N8N. It's especially helpful if you are a DevOps and your N8N instance is self hosted. If you carea lot about security and number of failed executions and at the same time you are using InfluxDB to…