Key Benefits
Catch Failures Instantly - React the moment a message fails to deliver Channel Agnostic - Works across WhatsApp, iMessage, and Android SMS Smart Recovery - Automate retries, fallbacks, or alerts on failure Filtered Automation - Trigger only on the error codes or channels you care about Zero Manual Monitoring - No need to watch logs for failed sendsWho Should Use It
Sales teams - Get notified the instant an outreach message fails Support teams - Catch undelivered replies before they cost you a customer Agencies - Monitor delivery health across client sub-accounts Operations teams - Trigger fallbacks and clean up bad contact data automaticallyRequirements
Before using this trigger, update your messaging provider app to the latest version:How to Set Up
Step 1: Create a New Workflow
Step 2: Add the Trigger
Step 3: Add Your Actions
Add any actions you want to execute when a message fails:- Send Internal Notification → Alert your team inside the CRM
- Wait + Resend → Retry the message after a delay
- Update Contact / Custom Field → Flag the contact for review
- Create Task → Queue a manual follow-up
Step 4: Save and Publish
Available Filters
Use filters to control exactly which failed messages start the workflow. Each filter can be paired with an operator (equals, contains, etc.).| Filter | Description |
|---|---|
| Contact ID | The unique ID of the contact the message was sent to |
| Location ID | The CRM location (sub-account) where the message failed |
| Error Code | The specific failure code returned (see Error Codes below). Choose one or more. |
| Error Type | The category of failure returned. Choose one or more. |
| Channel Type | The channel the message was sent on (e.g. whatsApp, imessage, sms) |
| Contact Phone Number | The phone number of the contact the message was sent to |
| Whatsapp Instance Index | The index of the WhatsApp instance that attempted the send |
| Phone Number Used | The number the message was sent from |
Error Codes
Use these codes with the Error Code filter to build precise recovery flows.| Code | What It Means |
|---|---|
| 101 | No connected WhatsApp instances exist for the location. Nothing can send. |
| 102 | A manual override {WA#N} was used in the message body, but instance N does not exist. |
| 103 | A manual override {WA#N} was used, but that instance is currently not connected. |
| 104 | The contact has a wa:<number> tag, but that WhatsApp number is not connected. |
| 105 | The contact’s assigned user owns a WhatsApp instance, but it is not connected. |
| 106 | All sender-selection rules were tried; no connected instance was available. |
| 107 | The logged-in user’s WhatsApp instance is not connected. |
| 108 | The workflow specified a sender number that exists but is currently offline. The system retried before failing. |
| 109 | The WhatsApp API rejected the message after multiple retries. |
| 110 | The recipient does not have a WhatsApp account. The contact is also auto-tagged with Invalid WhatsApp Number. |
| 111 | The workflow specified a sender number that is not registered for this location at all. |
Example Use Cases
Use Case 1: Alert the Team on a Failed Send
Know the moment an outbound message doesn’t go through. Trigger: Message Failed Action: Send an internal notification to the assigned user.Use Case 2: Clean Up Invalid Numbers
Flag contacts that can’t receive messages. Trigger: Message Failed Filter: Error Code is 110 Action: Add a tag and move the contact out of active outreach.Important Notes
Technical Details
- The trigger fires once per failed message
- Filters are optional - leave them blank to fire on every failed message
- Error Code and Error Type support selecting multiple values
- Use the Channel Type filter to scope the workflow to a single channel
Best Practices
- Use the Error Code filter to build targeted recovery flows (e.g. retry on 108, tag on 110)
- Use the Channel Type filter when handling channels differently
- Test your workflow by forcing a failure (e.g. sending to a disconnected number)
FAQs
Which channels does this trigger cover?
Which channels does this trigger cover?
All of them - WhatsApp, iMessage, and Android SMS. Use the Channel Type filter to narrow to one channel.
Can I trigger on specific errors only?
Can I trigger on specific errors only?
Yes. The Error Code and Error Type filters are multi-select, so you can fire on one or several failure conditions.
Do I have to add filters?
Do I have to add filters?
No. Filters are optional. Without them, the trigger fires on every failed message.
Support
If you need help with the setup or onboarding:- Email: support@messagesync.ai