Aggregate error alerts and send consolidated reports via Email and Jira

Error Alert Aggregator – Email and Jira

This workflow aggregates error logs arriving from multiple sources, deduplicates identical events within a configurable time-window, and sends a single consolidated notification via Email and Jira. It prevents alert fatigue by batching similar errors and guarantees that responsible teams are informed through both channels.

Pre-conditions/Requirements

Prerequisites - n8n instance (self-hosted ≥ v1.0 or n8n.cloud account) - Basic understanding of your log source’s payload structure - SMTP server or n8n Email credentials configured - Jira Cloud or Jira Server account with API access

Required Credentials - Email (SMTP/IMAP or n8n Email node credential) — to dispatch alert emails - Jira — Create issues automatically in the chosen project - HTTP Request Auth (optional) — If your log endpoint requires authentication

Specific Setup Requirements | Setting | Recommended Value | Notes | |-----------------------------|----------------------------------------|-----------------------------------------------------------| | Batch window (Wait node) | 10 minutes | Time allowed to collect & deduplicate errors | | Deduplication key (Code) | errorid or message field | Choose a unique attribute representing the same incident | | Email recipients | Security & DevOps distribution list | Use semicolons for multiple addresses | | Jira project key | SEC | Project where alert tickets should be filed |

How it works

This workflow aggregates error logs arriving from multiple sources, deduplicates identical events within a configurable time-window, and sends a single consolidated notification via Email and Jira. It prevents alert fatigue by batching similar errors and guarantees that responsible teams are informed through both channels.