Trigger: Channel Disconnected
Set up a workflow that alerts you the moment a channel disconnects from Omnifox.
Watch this step in the video · WhatsApp templates and the 24-hour window
What it is
Fires when a channel of any type loses its connection to Omnifox: WhatsApp (API or QR), Instagram, Messenger and the rest. For example: the health check finds the channel isn't responding, Meta reports the account changed, a WhatsApp or Instagram token is no longer valid or couldn't be renewed, the WhatsApp QR session was closed or blocked, or the number moved to another account.
For the same channel it fires only once per hour, even if the outage is detected through several paths.
When to use it
- Alert the team as soon as a channel goes down, before a customer notices.
- Create an internal alert with the reason for the disconnection.
- Pause other automations that depend on that channel until it's reconnected.
Requirements
- At least one channel connected to the workspace.
- Workflows module enabled.
Available variables
$channel.id,$channel.name,$channel.type$disconnect.reason: reason for the disconnection
Configuration (filters)
- Specific channel: limits the trigger to one channel.
- Channel type: limits the trigger to one type (for example, only Instagram).
How to set it up
- Go to Workflows and create a new workflow.
- In the trigger palette, open the System category.
- Choose Channel disconnected.
- (Optional) Filter by channel or by channel type.
- Connect an action, such as posting in Team or emailing the admin.
- Save and turn the workflow on.
Example
The Instagram channel disconnects because its token couldn't be renewed. The workflow immediately posts in the “Tech support” Team space, with $channel.name and $disconnect.reason, so someone reconnects it before messages are lost.
Tips
- Reconnect the channel from Settings → Channels. This trigger only alerts; it doesn't reconnect by itself.
- Since it doesn't repeat within an hour for the same channel, you don't need to build your own guard against repeated alerts.
Troubleshooting
- It didn't fire: check that the workflow is on and that its channel or type filters don't exclude the channel that went down.
- Only one alert arrived although the channel dropped twice in a row: expected if it was within the same hour.
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.