Multi-channel Website Downtime Incident Response - n8n Workflow

DevOps engineers and Site Reliability Engineers (SREs).
System administrators needing immediate, reliable downtime alerts.
Teams utilizing Notion for incident management and ticketing.
Anyone looking for advanced n8n templates to handle critical monitoring tasks.

Website downtime demands immediate action. Relying on a single alert channel can lead to missed notifications and slower resolution times. This robust n8n workflow provides a solution by creating a multi-channel incident response pipeline powered by the UptimeRobot monitoring service. When a website goes down, the dedicated n8n trigger captures the event immediately.

The automation then executes four crucial actions in parallel: sending alerts via Slack, WhatsApp, and Email, and simultaneously logging the incident in Notion. This workflow ensures no critical alert is missed, providing rapid visibility across all key communication platforms and generating a traceable task for investigation. This structure showcases the flexibility achievable with n8n and serves as an excellent reference among available n8n templates for critical infrastructure monitoring.

This automation initiates immediately upon receiving a POST request from UptimeRobot, indicating a monitored site is down. This external event acts as the primary n8n trigger.

1. Triggering the n8n Workflow: The UptimeRobot Webhook Trigger n8n node listens for downtime events on a specific path (/uptime-alert). When an alert is received, the node extracts critical data like the monitorURL and alertTime.


2. Parallel Alerting: The workflow immediately branches out to execute three parallel notification actions:

1. Task Management: After the alerts are initiated, the flow proceeds to the final step: task creation. The Create Notion Task n8n node uses the incident data to automatically generate a new page/task in the designated Notion database. This step ensures the incident is logged and assigned immediately for tracking and post-mortem analysis.

To deploy this comprehensive n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON data and paste it directly into your n8n canvas using the 'Import Workflow' option.


2. UptimeRobot Setup: Activate the UptimeRobot Webhook Trigger n8n node. Note the unique URL generated by n8n (e.g., https://your.n8n.instance/webhook/05e1fbdc...). Configure UptimeRobot to send downtime alerts to this specific URL.


3. Credential Setup: You must configure credentials for the connected services:

1. Activation: Once all credentials and configurations are correct, save and activate the n8n workflow.

This n8n workflow leverages several specialized n8n node types to achieve reliable multi-channel communication:

UptimeRobot Webhook Trigger (n8n trigger):
Function: Serves as the starting point, listening for POST requests from UptimeRobot. This is the critical n8n trigger that initiates the entire response process.
Key Configuration: Uses a specific path (uptime-alert).
Send Slack Alert (n8n node):
Function: Sends a formatted text message containing the down URL and timestamp to the team's incident channel.
Key Configuration: Dynamically maps data: text: 🚨 Website Down Alert: {{$node['UptimeRobot Webhook Trigger'].json['monitorURL']}}...
Send message (WhatsApp n8n node):
Function: Delivers a high-priority text alert via WhatsApp.
Key Configuration: Requires a configured phoneNumberId and recipientPhoneNumber.
Send Email Alert (n8n node):
Function: Sends a formal email notification to the monitoring distribution list.
Key Configuration: Sets the subject to 'Website Down Alert' and uses the input data for the body text.
Create Notion Task (n8n node):
Function: Automatically logs the incident as a task in the specified Notion database, ensuring accountability and tracking.
* Key Configuration: The title of the new page is dynamically set using the incident data, marking it as a critical task.