Trigger: Channel Disconnected

What it is

Fires when a channel loses its connection to Omnifox — for example, an expired Meta token or a manual disconnect. Today this is only implemented for WhatsApp channels; Instagram, Messenger, and other channels don't emit this event yet.

When to use it

• Alert your tech team the moment a WhatsApp channel drops, before customers notice.
• Log the disconnect reason internally.
• Pause other automations that depend on that channel until it's back.

Requirements

• At least one WhatsApp channel connected to the workspace.
• Workflows enabled.

Available variables

• $channel.id, $channel.name, $channel.type
• $disconnect.reason — why it disconnected

Configuration (filters)

• Specific channel: restrict the trigger to one channel.
• Channel type: today the event only fires for WhatsApp channels, so this filter has no practical effect for other types.

How to set it up

1. Open Workflows and create a new workflow.
2. Open the "System" category in the trigger palette.
3. Drag "Channel disconnected" onto the canvas.
4. (Optional) Filter by a specific WhatsApp channel.
5. Connect an action, like a Team alert or an email to the admin.
6. Save and activate the workflow.

Example

Your main WhatsApp channel disconnects because the Meta token expired. The workflow instantly posts to the "Tech Support" Team space with $channel.name and $disconnect.reason, so someone reconnects it before messages start piling up.

Tips

Reconnect the channel from Settings → Channels (Embedded Signup for WhatsApp). This trigger only alerts — it doesn't reconnect automatically.

Troubleshooting

• If it never fires for an Instagram, Messenger, or other non-WhatsApp channel: that's expected today, the trigger doesn't cover those channels yet.
• If it never fires even though a WhatsApp channel dropped, check the workflow is Active and that no channel filter is excluding the one that failed.