Skip to content
Automation Squad
{}TwIn build

Notifications & alerts

Any-system webhook → Twilio SMS to the on-call phone

Text the person on call the moment any system fires a webhook.

Any tool that can send a webhook can now wake a phone. Point your uptime monitor, form, CRM or custom script at one n8n URL and the alert reaches the on-call number as a Twilio SMS within a minute of the event. Built for owners and IT leads who are away from Slack more than they are in it. The sending system gets a receipt back with the Twilio message ID.

How it works

  1. {}

    Trigger

    HTTP POST received on the n8n webhook URL from any system

    Webhook / HTTP API

  2. if

    Step 1

    Check the secret and read the payload

    Requests without the matching header secret are rejected; the rest have their fields (source, severity, message, link) mapped onto one alert shape, whatever system sent them.

  3. Tw

    Step 2

    Send the SMS to the on-call numbers

    One text per number on the on-call list, from your Twilio number: source, severity and message on the first line, the link on the second if there is one.

  4. {}

    Step 3

    Return a receipt to the sender

    The calling system gets a 200 response carrying the Twilio message SIDs, so its own log shows the texts were accepted.

What changes once it runs

  • A text lands on the on-call phone within a minute of the webhook arriving.
  • One URL serves every system you own; each sender is told apart by the source field it passes.
  • Requests without the shared secret are dropped before any SMS is sent.
  • The sending system receives the Twilio message SIDs in the response, so a delivery can be traced from its log to Twilio's.

What you get

  • The n8n workflow export, tested end to end before it ships
  • A setup guide covering the webhook URL, the header secret and the on-call number list
  • One recorded walkthrough of the first test alert, sent from curl and then from a real monitor
  • Three sample payloads to test with: a monitoring alert, a form submission and a plain curl call
  • 30 days of email support for setup questions

Before you start

  • Twilio: an account with an SMS-capable number (the trial number works for testing), plus the Account SID and Auth Token
  • Recipient numbers verified in Twilio while the account is on trial
  • For US recipients, the sending number registered for A2P 10DLC or a verified toll-free number; Twilio blocks unregistered US traffic
  • Any system that can send an HTTP POST with a custom header (most monitors, forms and CRMs can)
  • n8n Cloud, or a self-hosted n8n reachable from the internet so the webhook URL can be called

Built for

Questions before you buy

Can it send to more than one person?
Yes. The on-call list is a comma-separated set of numbers in one workflow variable, and every number on it gets the same text. Rotation by day or hour is a small change to the first logic step, and the setup guide shows where.
What happens if Twilio is down or a number is wrong?
The Twilio step is set to continue on error, and the response to the sender carries the error text instead of a message SID. The sender's log will show the failure. Nothing is retried in the starter build; add a second channel such as Slack or email if you need a fallback.
Do I need a paid n8n plan?
Any n8n plan works. n8n Cloud's Starter tier is enough, and the self-hosted Community Edition is free. Self-hosted needs a public URL for the webhook, which usually means a reverse proxy or a tunnel.
Does it work on Make or Zapier?
Yes. The Make blueprint is in the package and the Zapier version ships as a shared Zap template. Zapier needs Webhooks by Zapier, a premium app on its paid plans. Make's custom webhook module is on every plan, the free one included.

Nearby on the shelf

Whole catalog