Skip to main content

Automated hourly n8n error monitoring with Slack notifications

Workflow preview

Workflow preview
100%
Automated hourly n8n error monitoring with Slack notifications 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 this template for? This template is ideal for n8n instance administrators, developers, and DevOps teams who need a proactive and organized way to monitor the health of their automations. If ...

Best for

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

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.n8n, n8n-nodes-base.splitinbatches, n8n-nodes-base.aggregate, n8n-nodes-base.code, n8n-nodes-base.stickynote, n8n-nodes-base.slack, n8n-nodes-base.set

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Automated hourly n8n error monitoring with Slack notifications
Workflow name
Automated hourly n8n error monitoring with Slack notifications

Who is this template for?

This template is ideal for n8n instance administrators, developers, and DevOps teams who need a proactive and organized way to monitor the health of their automations. If you want to be notified about failures as soon as they happen, without having to manually check execution logs, this workflow is for you.

What does this template do?

This workflow automates error monitoring on your n8n instance. Every hour, it performs the following steps:

  1. Queries the n8n API to fetch all executions that have failed in the last hour.
  2. Groups the errors by workflow to consolidate the information.
  3. Builds a rich message for each failed workflow, including the error count.
  4. Sends an alert to a Slack channel with a button to open the workflow directly, allowing for immediate investigation.

Requirements

Before you start, you will need to have the following configured in your n8n instance:

  • n8n API Credentials: You need to generate an API key in your n8n instance settings so the workflow can query execution data.
  • Slack Credentials: A configured Slack (OAuth2 API) credential to allow n8n to send messages to your workspace.

How to set it up

Setup is simple and only takes a few minutes:

  1. Config Node: In the node named "Config", you must set the value for the baseUrl to your n8n instance's URL (e.g., https://n8n.yourdomain.com). This is crucial for generating the correct workflow links in the Slack message.
  2. Schedule Trigger: The workflow is pre-configured to run every hour. You can adjust the frequency in this node to fit your needs.
  3. "Get Failed Executions" Node (HTTP Request):
    • Under Authentication, select 'Header Auth'.
    • In the Credentials field, select your n8n API credential.
  4. "Post to Slack" Node (Slack):
    • Select your Slack credential.
    • In the Channel field, enter the name of the channel where error notifications should be sent (e.g., #n8n-alerts).
  5. Activate the Workflow! After these steps, just activate the workflow to start the automatic error monitoring.

How to customize the workflow

You can easily customize this template:

  • Change the Schedule: Modify the Schedule Trigger node to run at different intervals (every 15 minutes, once a day, etc.).
  • Change the Notification Channel: Instead of Slack, you can replace the last node to send notifications to Discord, Microsoft Teams, Telegram, or even by email.
  • Add More Information: You can modify the MakeMessage node that generates the message to include more details about the errors, such as the error message or the exact time of failure.

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 - Schedule Trigger

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

Block 2 - GetWorkflows

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

Block 3 - Loop

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 4 - n8n

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

Block 5 - Aggregate

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

Block 6 - MakeMessage

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - FilterLastHour

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 8 - Sticky Note

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

Block 9 - Slack

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.2

Block 10 - Config

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

3. Summary Table

Workflow Automated hourly n8n error monitoring with Slack notifications
Complexity intermediate
Nodes 10
Categories DevOps
Author Matheus Pedrosa
Published 07 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7076/7076.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 Automated hourly n8n error monitoring with Slack notifications do?

Who is this template for? This template is ideal for n8n instance administrators, developers, and DevOps teams who need a proactive and organized way to monitor the health of their automations. If ...

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.