Send an SMS when a workflow fails

Used in n8n, this workflow automatically sends an SMS via Twilio when a workflow fails, ensuring immediate notification of issues for prompt resolution.

7/8/2025
2 nodes
Simple
manualsimpleerrortriggertwilio
Categories:
Communication & MessagingManual TriggeredSimple Workflow
Integrations:
ErrorTriggerTwilio

Target Audience

  • Developers: Those who create and manage workflows that need monitoring for failures.
    - Project Managers: Individuals who oversee projects and want to be alerted about workflow issues immediately.
    - Small Business Owners: Owners who rely on automated workflows for operations and need to ensure they run smoothly.
    - IT Support Teams: Teams responsible for maintaining systems and ensuring uptime, who need quick notification of errors.
  • Problem Solved

    This workflow addresses the issue of workflow failures by automatically sending an SMS notification via Twilio whenever an error occurs. This ensures that users are promptly informed about issues, allowing for quick resolution and minimizing downtime.

    Workflow Steps

  • Error Trigger: The workflow begins with an Error Trigger node that activates when a workflow fails. This serves as the initial point of detection for any errors that occur.
    - Twilio Notification: Once an error is detected, the workflow proceeds to the Twilio node, which sends an SMS notification. The message includes critical information such as the workflow ID and name, indicating which workflow has failed. This process ensures that the responsible parties are notified immediately.
  • Customization Guide

  • Phone Numbers: Users should customize the to and from fields in the Twilio node to specify the recipient's phone number and the sender's Twilio number.
    - Message Content: The message can be modified to include additional details or context about the error or to change the tone of the notification.
    - Error Handling: Users can integrate additional nodes to handle different types of errors or to take alternative actions based on the error type, enhancing the workflow's responsiveness.