Conversation triggers (opened, closed, resolved, pending, inactivity, lookup)
Learn how to start automations when a conversation is opened, closed, resolved, left pending or sits inactive.
Watch this step in the video · The palette: triggers and nodes
Conversation triggers start an automation whenever a conversation in your Inbox changes state. They are the foundation for routing, alerting your team, sending surveys or tagging contacts hands-free. This article covers the conversation triggers you will reach for most.
Available triggers
- Conversation opened — when a conversation is opened or reopened (by an agent, the API, another workflow or a customer reply).
- Conversation closed — when someone closes the chat. It carries the resolution time, handy for CSAT.
- Conversation marked resolved — when it is marked resolved without closing it.
- Conversation marked pending — when it is left waiting on the customer.
- Auto-close on inactivity and its variants customer didn't reply / agent didn't reply — fire when the inactivity sweep acts on the chat.
- Customer waiting on agent — a periodic watcher that looks up conversations where the customer is left waiting, ideal for escalation or alerts.
Requirements
- A plan with Automations enabled.
- Permission to manage automations in the workspace.
Steps
- Open Automations from the workspace menu and click New automation → Start from scratch.
- In the Trigger panel (left), open Choose how it starts and pick the conversation trigger you need, e.g. Conversation closed.
- In Settings (right panel) tune the filters: Channel type, Assigned team, Previous status or, for closures, the resolution time. Leave them empty to react to all.
- Drag one or more Actions from the palette and connect them to the trigger (notify the team, add a tag, send a template, and so on).
- Use the Available variables tokens (such as who opened the chat or which team closed it) inside your actions.
- Click Save, then Activate.
Verify it
- Click Test to fire it with sample data, then open the Run history → View trace to see exactly what happened, step by step.
- Trigger the real event (close or reopen a test conversation) and confirm the run shows as Completed.
If it doesn't work
- Is the automation set to Active? An Inactive one never fires.
- Check the filters: an over-strict Channel type or Assigned team can drop the event.
- If you chose Conversation opened with a Previous status filter, make sure that status matches (e.g. Was closed for reopens).
- Look in Run history for Paused by limit: you hit the plan's run cap.
Tips
- Pair Conversation closed with a minimum resolution-time filter to send CSAT only on real cases.
- The Customer waiting on agent trigger is great for SLAs: alert the team when nobody replies in time.
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.