Trigger: Outbound Message Failed

The Outbound Message Failed trigger fires when a message you sent from Omnifox couldn't be delivered, for any reason: provider error, WhatsApp's 24-hour window expired, insufficient wallet balance, and so on.

When to use it

• Alert the team when a critical send fails (e.g. a payment confirmation).
• Retry through another channel if WhatsApp fails (e.g. fall back to SMS or email).
• Specifically flag wallet/balance errors to avoid a service outage.

Filters available

• Channel type, Specific channel.
• Error code contains: e.g. BSP_INSUFFICIENT_WALLET, SEND_FAILED, RETRY_FAILED.

Variables available

• $message.id, $message.text, $message.direction (always outbound)
• $message.error_code, $message.error_message, $message.failed_at
• Conversation and contact variables

How to build it

1. Go to Workflows → New workflow.
2. Drag a Trigger node → pick Outbound Message Failed (under Messages).
3. To isolate one error type, fill in Error code contains (e.g. BSP_INSUFFICIENT_WALLET).
4. Add an action like Notify team using $message.error_message.
5. Save and activate.

Example

Workflow "Low wallet alert": filters on error code containing BSP_INSUFFICIENT_WALLET → Notify team (Billing space): ⚠️ Send to {{contact.display_name}} failed: {{message.error_message}}.

Tips

Build a separate workflow just for wallet/balance errors — they usually need immediate admin action, unlike a simple message retry.

Troubleshooting

If the trigger never fires, check the outbound message's history inside the conversation — many "silent failures" are actually queued for automatic retry and only count as a final failure once retries are exhausted.