Alert Workflow Failures Instantly with n8n and Twilio SMS

What This Automation Does

This workflow watches for errors in all active workflows in your n8n setup.
When any workflow stops working caused by a failure, it sends an SMS message right away.
The message tells you which workflow failed by showing the workflow ID and name.
This helps you notice problems fast and fix them quickly before they cause trouble.
It saves time from checking logs manually and avoids delays in your work.

Tools and Services Used

• n8n: automation platform where workflows run.
• Twilio: sends SMS messages with failure alerts.

Inputs, Processing Steps, and Outputs

Inputs

• Any workflow failure event caught by the Error Trigger node.

Processing Steps

• The Error Trigger node detects workflow errors across n8n.
• The error data includes workflow ID, workflow name, and error timestamp.
• The Twilio node uses this error data to create a detailed SMS.
• Twilio node sends the SMS using the configured phone numbers and credentials.

Output

• A text message on your phone showing which workflow failed and when.

Beginner step-by-step: How to use this Workflow in n8n Production

Import Workflow

1. Download the workflow file using the Download button on this page.
2. Open your existing n8n editor where workflows are created.
3. Use Import from File option to bring this workflow into n8n.

Configure after Import

1. Add Twilio API Key credentials in the Credential Manager inside n8n if not done before.
2. Open the Twilio node and select the proper Twilio API credentials.
3. Update the “To” phone number in the Twilio node to the recipient’s number in E.164 format.
4. Update the “From” phone number to your Twilio verified sending number.

Test Workflow

1. Trigger a test error in a dummy workflow or use the built-in test feature in the Error Trigger node.
2. Check if the SMS message arrives with correct workflow failure info.

Activate for Production

1. Save any changes made to the workflow.
2. Toggle the workflow to Active mode to enable live error monitoring.
3. Ensure your n8n instance is running continuously. Use self-host n8n if needed to keep n8n always working.

Step-by-Step Guide

Step 1: Start with n8n and Create a New Workflow

Log into your n8n dashboard. Click Create → New Workflow to start fresh. You should see a blank canvas ready for nodes.

Step 2: Add the Error Trigger Node

On the left node panel, search for and drag the Error Trigger node onto the canvas. This node listens for any workflow failures across your n8n instance.

No parameters need configuring here. Just ensure it’s positioned clearly (e.g., center of canvas) for better visualization.

Step 3: Add the Twilio Node

Next, add the Twilio node. Search for “Twilio” in the nodes panel and drag it next to the Error Trigger node.

Step 4: Configure Your Twilio Node for SMS

In the Twilio node settings, fill in the following:

• To: Enter the recipient’s phone number in E.164 format (e.g., +1234567890).
• From: Enter your Twilio verified sending number.
• Message: Use the expression editor to dynamically create a text alert message:

=Your workflow with ID: {{$node["Error Trigger"].json["workflow"]["id"]}} and name: {{$node["Error Trigger"].json["workflow"]["name"]}} failed to execute.

This message pulls the workflow ID and name from the Error Trigger node’s json payload to provide context.

Step 5: Connect the Nodes

Click on the output of the Error Trigger node and drag it to the input of the Twilio node. This connection means that when an error is caught, it will trigger sending your SMS alert.

Step 6: Set Up Twilio Credentials in n8n

If you haven’t already, go to Credentials → New Credential → Twilio API and enter your Account SID and Auth Token from Twilio dashboard. Save the credentials.

Then in the Twilio node settings, select these credentials under Authentication.

Step 7: Save and Activate Your Workflow

Click Save, then toggle the workflow Active to enable real-time monitoring.

Step 8: Test Your Workflow

To verify, deliberately cause a workflow error or test the Error Trigger in isolation. You should receive an SMS alert matching the failure details.

If no message arrives, double-check your Twilio numbers and credentials.

Customizations ✏️

• Change the SMS message text: Edit the field inside the Twilio node with this example:

=Your workflow named {{$node["Error Trigger"].json["workflow"]["name"]}} failed at {{$node["Error Trigger"].json["timestamp"]}}.

• Send to more than one phone number: Copy the Twilio node and link the Error Trigger to each copy. Update each node with different recipient numbers.
• Add error details into SMS: Use this expression to include more info:

{{$node["Error Trigger"].json["error"]}}

Troubleshooting 🔧

• Problem: No SMS message sends when a workflow fails.
• Cause: Twilio credentials or phone numbers are incorrect.
• Fix: Check the Twilio Account SID, Auth Token, and phone numbers in the credential manager and Twilio node setup. Use the Twilio console to test sending SMS directly.
• Problem: The Error Trigger node does not fire when expected on error.
• Cause: The workflow or nodes are not active, or error conditions are not met.
• Fix: Confirm the workflow is active. Create a test workflow with a forced failure to check the Error Trigger.

Pre-Production Checklist ✅

• Make sure Twilio credentials are valid and connected in n8n.
• Verify phone numbers are in correct E.164 format and Twilio sender number is verified.
• Test the setup by causing workflow failures to confirm SMS arrives.
• Ensure the workflow is saved and activated for live monitoring.
• Consider a backup alert method, like email, if SMS delivery fails.

Deployment Guide

Keep this workflow switched on in n8n to keep watching for workflow errors.
SMS alerts will come instantly if any failures occur.
Add logging or team chat notifications later for a complete error tracking system.
No extra servers needed beyond n8n and Twilio, so it’s easy for small to medium teams.
Check resources like self-host n8n if own server hosting is wanted.

Conclusion

✓ This workflow sends SMS on any workflow fail instantly.
✓ Helps catch automation errors without manual log checks.
✓ Saves time and cuts downtime for your processes.
→ You get fast alerts with all failure details on your phone.
→ You improve operation reliability and response speed.
→ This setup is simple, no coding needed, only native n8n nodes.
Consider adding Slack notifications or error history logs next.
Keep automation running smooth and trouble-free!