Skip to main content

Error log monitor with SSH, Slack alerts & Jira ticket creation

Workflow preview

Workflow preview
100%
Error log monitor with SSH, Slack alerts & Jira ticket creation preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Description Automates monitoring of error logs and notifies developers of critical errors. Sends Slack alerts for critical and non critical errors, with auto creation of Jira tickets for critical i...

Best for

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

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.set, n8n-nodes-base.ssh, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.jira, n8n-nodes-base.wait

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Oneclick AI Squad.

Original n8n.io source

1.1 Workflow description

Title
Error log monitor with SSH, Slack alerts & Jira ticket creation
Workflow name
Error log monitor with SSH, Slack alerts & Jira ticket creation

Description

  • Automates monitoring of error logs and notifies developers of critical errors.
  • Sends Slack alerts for critical and non-critical errors, with auto-creation of Jira tickets for critical issues.

Essential Information

  • Triggers manually or on a scheduled basis (e.g., every 5 minutes).
  • Reads and parses server logs to detect errors.
  • Alerts developers via Slack and creates Jira tickets for critical errors.

System Architecture

  • Error Detection Pipeline:
    • Manual Trigger: Initiates the workflow manually.
    • Schedule Every 5min: Schedules automatic runs every 5 minutes.
    • Set Config: Configures basic parameters for log reading.
    • Read Error Logs: Executes SSH command to fetch server logs.
    • Wait For All Logs: Ensures all logs are read.
  • Error Processing Flow:
    • Parse Logs: Parses logs and categorizes critical vs. non-critical errors.
    • IF Critical Error: Filters for critical errors.
  • Alert and Ticket Creation:
    • Send Slack Alert: Sends detailed alerts for critical errors via Slack.
    • Create Jira Ticket: Creates a Jira ticket for critical errors.
    • Send Non-Critical Alert: Sends simple alerts for non-critical errors via Slack.

Implementation Guide

  • Import the workflow JSON into n8n.
  • Configure SSH credentials for log access.
  • Set up Slack and Jira integrations with appropriate credentials.
  • Test with a manual trigger and sample log data.
  • Adjust the schedule (e.g., every 5min) and error parsing rules as needed.
  • Monitor alert accuracy and ticket creation.

Technical Dependencies

  • SSH access for reading server logs.
  • Slack API for team notifications.
  • Jira API for bug ticket creation.
  • n8n for workflow automation and scheduling.

Customization Possibilities

  • Adjust the Cron schedule for different intervals (e.g., every 10min).
  • Modify Parse Logs node to refine error categorization rules.
  • Customize Slack alert messages in Send Slack Alert and Send Non-Critical Alert nodes.
  • Enhance Jira ticket details in Create Jira Ticket node (e.g., add priority).
  • Add email notifications for additional alert channels.

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

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

Block 2 - Set Config

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

Block 3 - Read Error Logs

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

Block 4 - Parse Logs

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

Block 5 - IF Critical Error

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

Block 6 - Send Slack Alert

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

Block 7 - Create Jira Ticket

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

Block 8 - Send Non-Critical Alert

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

Block 9 - Wait For All Logs

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

Block 10 - Sticky Note

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

Block 11 - Sticky Note1

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

Block 12 - Sticky Note2

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

Block 13 - Schedule Every 5min

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

Block 14 - Sticky Note3

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

Block 15 - Sticky Note4

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

Block 16 - Sticky Note5

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

Block 17 - Sticky Note6

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

Block 18 - Sticky Note7

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

Block 19 - Sticky Note8

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

Block 20 - Sticky Note9

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

3. Summary Table

Workflow Error log monitor with SSH, Slack alerts & Jira ticket creation
Complexity advanced
Nodes 20
Categories DevOps
Author Oneclick AI Squad
Published 30 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6677/6677.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 Error log monitor with SSH, Slack alerts & Jira ticket creation do?

Description Automates monitoring of error logs and notifies developers of critical errors. Sends Slack alerts for critical and non critical errors, with auto creation of Jira tickets for critical i...

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.