Messaging triggers (received, delivered, read, failed, WhatsApp interactivity)
Learn the triggers that start a workflow based on a message's lifecycle and the customer's interaction on WhatsApp.
Watch this step in the video · Trigger filters
Messaging triggers are the events that start a workflow based on what happens to a message: a new one arrives, it gets delivered, the customer reads it, the send fails, or the customer taps a button on WhatsApp. They are the foundation for automating replies, follow-ups and alerts.
When to use them
- Reply instantly when a message comes in.
- Notify an agent when an outbound message fails.
- Chain steps when the customer reads or interacts with a message.
The available triggers
| Trigger | Fires when… | Typical use |
|---|---|---|
| Message received | The contact sends you an inbound message | Auto-reply, route to a team |
| Message delivered | Your outbound message reached the device | Mark stages of a send |
| Message read | The contact opened/read your message | Follow up only with readers |
| Outbound message failed | A message could not be sent | Alert the agent, retry on another channel |
| Button clicked | The contact taps an interactive WhatsApp button | Menus, confirmations, branch the flow |
"Message delivered" and "Message read" depend on the receipts (ticks) WhatsApp reports; if the customer turned off read receipts, the read event may never arrive.
Steps to use a messaging trigger
- Open Automations → Workflows and click New (or edit a flow).
- From the palette, drag the trigger node you need onto the canvas (for example, Message received).
- Select the trigger and, in the inspector, set its filters: which Channel it applies to and, depending on the trigger, data such as message ID or template.
- Connect the trigger to the actions you want (send message, assign, wait, condition…).
- Save and activate the workflow from the list.
Verification
- Cause the real event: send a test message, or ask the contact to tap a button.
- Check the flow's execution history and confirm it fired with the expected trigger.
- Use the editor's test run with sample data to validate the logic before going live.
If it does not work
- It does not fire on "Message received": confirm the Channel filter and that no other workflow captures the same event first.
- "Message read" never arrives: that is normal if the customer disabled read receipts; do not build critical logic on this event alone.
- "Button clicked" does not trigger: make sure the button comes from an interactive WhatsApp message and that the button ID/title is unique.
Tips
- For WhatsApp, remember the 24-hour window: outside it you can only start with a template. Combine "Message received" with your actions to reply inside the window.
- Keep button titles unique: Meta requires unique IDs/titles on reply buttons so "Button clicked" works reliably.
Related articles
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.