Overview

Know when Twilio messages fail. Twilio Event Streams sends message status events as JSON to a webhook sink, which you point at your SQIBS API endpoint. SQIBS opens an incident for each failed or undelivered message.

You need
A Twilio account with Event Streams, and a SQIBS API token
Setup time
About 15 minutes
Result
Failed Twilio messages open SQIBS incidents

How it works

Twilio
Alert fires
A message fails or cannot be delivered.
Twilio
Sends a webhook
Event Streams posts the event to a webhook sink, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Event types ending in failed or undelivered open it.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. Add a filter with these values (there is no built-in Twilio template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger (filter 1) "type" failed Opens an incident for failed messages.
Trigger (filter 2) "type" undelivered Opens an incident for undelivered messages.
Match "data"."messageSid" One incident per message.
Title from "type" The event type becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

Add each numbered row as its own filter (same Match values). SQIBS needs every value in Key value contains to be present, so several values in one filter would never match.

Do not use the classic message Status Callback URL for this: Twilio sends those as form data, which the filter cannot read. Event Streams sends JSON. If your sink delivers events in a list, prefix each key with [0]., for example [0]."type".

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

Find the right key with the JSON key creator
In the API Integration window, click the round {} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.

Step 2: Create a webhook sink and subscription

  1. In the Twilio Console, go to Event Streams > Manage and create a new sink of type Webhook.
  2. Set the destination to your SQIBS endpoint and the method to POST:
https://<your-endpoint>/sqibs-api/v1/process?from=twilio&token=<your-token>

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

  1. Create a subscription for the sink and choose the messaging events you care about, for example message failed and undelivered.
  2. Save. Twilio sends a test event to new sinks; check it in the API log.

Step 3: Test it

The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.

  1. Send a message to a number that cannot receive it, for a test.
  2. In SQIBS, a new incident opens. The event looks like this (shortened):
{
  "specversion": "1.0",
  "type": "com.twilio.messaging.message.failed",
  "source": "/2010-04-01/Accounts/AC123/Messages/SM123.json",
  "time": "2026-11-22T10:15:00.000Z",
  "data": {
    "messageSid": "SM0123456789abcdef0123456789abcdef",
    "to": "+6590000000",
    "errorCode": 30003
  }
}

No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the Event Streams sink.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when SMS messages start failing, SQIBS can run a workflow that checks your Twilio balance and sender status and switches to a backup sender.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: