Send Statuspage Incident Digest Emails (SMTP) with n8n

Get one clean status digest email—automatically—when Atlassian Statuspage incidents change

This n8n workflow polls multiple Atlassian Statuspage incident feeds every 10 minutes (for example GitHub, Cloudflare, and OpenAI), filters for new relevant incident updates, and sends a single combined digest email via SMTP—without spamming duplicates.

What this workflow does

• Runs on a schedule: executes every 10 minutes to check incident updates.
• Maintains a sent-alert memory: ensures an n8n Data Table named vendor_status_alerts_sent exists to store alert keys already emailed.
• Fetches Statuspage incidents per vendor: splits your vendor list and retrieves each feed from /api/v2/incidents.json via HTTP.
• Filters what matters: selects incident updates that match your configured impact threshold, lookback window, and optional component keywords.
• Handles failures: generates a daily “fetch failed” alert when a status page cannot be read.
• Prevents duplicate notifications: drops any alerts whose keys already exist in vendor_status_alerts_sent.
• Sends one digest email: builds a combined HTML + text message grouped by vendor and incident, then sends it using the Email (SMTP) node.
• Updates history: records sent alert keys (with timestamps) back into the Data Table for future runs.

Use cases

• Send SaaS operators a single incident digest covering multiple dependencies (e.g., GitHub, Cloudflare, OpenAI) instead of checking each status page.
• Reduce alert fatigue for on-call teams by only emailing incident updates that meet your minimum impact and lookback rules.
• Detect monitoring gaps when a vendor status page feed can’t be fetched (daily fetch-failed notice).

Technical details

• Workflow schedule: every 10 minutes.
• Core logic: Data Table, split out, code, set, and drop/merge behavior to avoid duplicates.
• Integrations: HTTP polling of Atlassian Statuspage /api/v2/incidents.json; email delivery via Email (SMTP).
• Nodes mentioned: set, code, split out, data table, email send, sticky note.

Set your emailFrom / emailTo, provide Statuspage base URLs, and configure minimumImpact and lookback to tailor your incident digest.