UNDELIVERABLE. You don’t run a webhook route, verify signatures, or keep a table of pending sends.
Choose failover or a Journey
Both move a message to another channel, at different moments:
A bounce arrives after the provider has accepted the email, so routing failover never sees it. Use the Journey for anything decided by delivery.
Prerequisites
- A Courier API key
- A connected email provider with delivery tracking on, such as the SendGrid event webhook. Without tracking, an email stays at
SENTand never reads asUNDELIVERABLE. See Delivery tracking is per provider. - A connected SMS provider
- Your users stored in Courier with an email address and a phone number
Send an SMS when an email bounces
1
Create the Journey
Open Journeys, select New Journey, name it
delivery-fallback, and choose the API Invoke trigger. Add a report_url field to the trigger schema so both messages can link to the same place.2
Send the email
Add a send node on the Email channel and write the message, using
{{report_url}} for the link. Publish its template.3
Wait for the delivery result
Add a delay node set to Duration, such as 1 hour. Courier updates the email’s status as your provider reports it, and the next node reads the status when the wait ends.Pick the longest wait you’re willing to make the user sit through before the SMS. A bounce your provider reports after the wait ends doesn’t trigger the SMS.
4
Send the SMS only if the email bounced
Add an SMS send node with the same message and one condition:
send_status.<email node ID> was UNDELIVERABLE. The node ID is the email node’s id. Over the API, it comes back when you create or replace the Journey, and GET /journeys/{templateId} returns it once the Journey is published.UNDELIVERABLE matches only that exact status, which your provider sets for a bounce or a dropped message. Users whose email went through skip the SMS.To send the SMS unless delivery is confirmed, use was not DELIVERED instead. That also covers an email still at SENT when the wait ends, so it needs delivery tracking working, or every user gets the SMS too.5
Publish
Publish the SMS template, then the Journey, and copy its ID from the editor.
Send an email when a push isn’t delivered
The same shape works the other way, for a push that doesn’t reach the device. Use a Push send node first, then a delay, then an Email send node with the conditionsend_status.<push node ID> was not DELIVERED.
A push reaches DELIVERED only when your app reports it, through a Courier mobile SDK or the payload’s trackingUrl. This works with Expo and every other push provider. Without that report, every push stays at SENT and every user also gets the email.
A user with no device tokens gets no push, and the email goes to them. The same happens if the push node was skipped: the condition reads as not delivered.
Trigger it from your app
CallPOST /journeys/{templateId}/invoke where you’d have sent the email. Replace delivery-fallback with the Journey ID you copied, or the alias if you set one.
Verify
1
Bounce an email on purpose
Invoke the Journey for a test user whose address you know bounces: a mailbox that doesn’t exist, on a domain with no catch-all. Send from a test sending domain, not your production one, so test bounces don’t count against its reputation. For a faster test, publish a copy of the Journey with a 2-minute delay and invoke the copy.After one bounce, SendGrid suppresses that address, so later tests to it are dropped. A dropped email also reads as
UNDELIVERABLE, so the SMS still goes out.2
Follow the run
Open the Journey’s Logs tab and select the run. The email node’s message shows
UNDELIVERABLE, and the SMS node shows its condition passed and the SMS sent. Over the API, GET /journeys/runs/{run_id}/steps returns the same steps.3
Check the happy path
Invoke it again for a user with a working address. The email is delivered and the SMS node is skipped.
FAQ
Does routing failover send an SMS when an email bounces?
Does routing failover send an SMS when an email bounces?
Routing failover acts when a provider rejects the send or errors. A bounce is reported after the provider accepted the email, so it takes a Journey with a
send_status condition, as above.Why did every user get the SMS?
Why did every user get the SMS?
The condition read a status other than the one you expected. With was not
DELIVERED, an email still at SENT passes, which happens when delivery tracking isn’t set up. Check the email’s status in Logs, and set up tracking for your provider.Why did a bounced user get no SMS?
Why did a bounced user get no SMS?
The bounce arrived after the delay ended, or the provider reported it as something other than a bounce. Lengthen the delay, and check the email’s timeline in Logs.
Can I fall back across more than two channels?
Can I fall back across more than two channels?
Chain the pattern: after the SMS node, add another delay and a send node with two conditions in one group, so both must hold:
send_status.<email node ID> was UNDELIVERABLE, and send_status.<SMS node ID> was not DELIVERED.Keep the email condition. When the email is delivered, the SMS node is skipped, and a skipped node reads as not delivered. Without the email condition, the third message would go to every user whose email arrived.