Send incident digest emails from Statuspage vendors with SMTP and Data Tables

Quick Overview

This workflow runs every 10 minutes to poll multiple Atlassian Statuspage incident feeds (for example GitHub, Cloudflare, and OpenAI), filters for relevant new incident updates, and sends a single digest email via SMTP while tracking what was already sent in an n8n Data Table.

How it works

1. Runs every 10 minutes on a schedule.
2. Ensures an n8n Data Table named vendor_status_alerts_sent exists to store keys for previously emailed alerts.
3. Splits your vendor list and fetches each vendor’s /api/v2/incidents.json feed via HTTP.
4. Extracts incident updates that match the configured impact threshold, lookback window, and optional component keywords, and also creates a daily “fetch failed” alert if a status page cannot be read.
5. Drops any alert events whose keys already exist in the vendor_status_alerts_sent table to prevent duplicate notifications.
6. Builds one combined digest (HTML + text) grouped by vendor and incident, then sends it as an email via the Email (SMTP) node.
7. Records the sent alert keys (with timestamp) back into the Data Table so only new updates are emailed on future runs.

Setup

1. Add an Email (SMTP) credential in the email-sending node so n8n can send messages from your mail server.
2. Update the vendor list in the Settings step with each status page base URL (must support the Atlassian Statuspage endpoint at /api/v2/incidents.json).
3. Set the emailFrom and emailTo values, and adjust minimumImpact, lookbackHours, and componentFilter to match your alerting preferences.