Skip to main content

Monitor workflow audits and failures with InfluxDB dashboard

Workflow preview

Workflow preview
100%
Monitor workflow audits and failures with InfluxDB dashboard preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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 ex...

Best for

  • DevOps automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.stickynote, n8n-nodes-base.n8n, n8n-nodes-base.splitout, n8n-nodes-base.set, n8n-nodes-base.summarize, n8n-nodes-base.scheduletrigger, n8n-nodes-base.merge

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Łukasz.

Original n8n.io source

1.1 Workflow description

Title
Monitor workflow audits and failures with InfluxDB dashboard
Workflow name
Monitor workflow audits and failures with InfluxDB dashboard

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 monitor status of your systems, this will perfectly fit in your stack.

How it works

This automation is fairly simple. It uses native N8N nodes to gather data from itself. Then it is parsing this data to be compatible with InfluxDB input. And finally it is sending this data to InfluxDB for further processing.

Remember to set up

Setup is really simple and you just need to provide just three variables. First is your InfluxDB URL, second is your InfluxDB organization, and third is your InfluxDB bucket name.

Of course, to set up N8N nodes and gather data from them, you will need your instance API key.

And that's all.

How it looks in InfluxDB?

See below

Schedule Audits

Audits don't need to be run often, but I would recommend it to be run on regular basis. This way you can see real data series in InfluxDB. I think that once a day should be enough, but it depends on your N8N usage of course

Thank you, perfect!

Glad I could help. Visit my profile for other automations for businesses. And if you are looking for dedicated software development, do not hesitate to reach out!

You can also see automations on my Sailing Byte's GitHub N8N repository.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When clicking ‘Execute workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Database Audit

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 4 - Filesystem Audit

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 5 - Instance Audit

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 6 - Nodes Audit

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 7 - Credentials Audit

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 8 - Split Report Data

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 9 - Prepare Influx Input Strings

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 10 - Contactenate with Commas

Type / Role
n8n-nodes-base.summarize - summarize
Config choices
Version 1.1

Block 11 - Pull Report Data and Risk Credentials

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 12 - Pull Report Data and Risk Database

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 13 - Pull Report Data and Risk Filesystem

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 14 - Pull Report Data and Risk Instance

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 15 - Pull Report Data and Risk Nodes

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 16 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Influx Globals

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 18 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Once a Day

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 21 - Get Active Workflows

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 22 - Get Failed Executions

Type / Role
n8n-nodes-base.n8n - n8n
Config choices
Version 1

Block 23 - Count Active

Type / Role
n8n-nodes-base.summarize - summarize
Config choices
Version 1.1

Block 24 - Count Failed

Type / Role
n8n-nodes-base.summarize - summarize
Config choices
Version 1.1

Showing the first 24 of 29 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Monitor workflow audits and failures with InfluxDB dashboard
Complexity advanced
Nodes 29
Categories DevOps
Author Łukasz
Published 11 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5873/5873.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Monitor workflow audits and failures with InfluxDB dashboard do?

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 ex...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.