All-in-One Chat Widget Support in the Customer Replied Trigger
You can now trigger workflows when a customer replies through an All-in-One Chat widget. This update adds clearer options and more specific filters, so you can build automations based on exactly how a customer responded.
What This Update Helps You Do
- Select All-in-One Chat directly from the Reply Channel dropdown
- Filter replies by Chat Type (Chat Widget or Live Chat)
- Select specific All-in-One Chat widget configurations
- Create cleaner, more precise workflow logic for unified chat setups
What’s New in the Customer Replied Trigger
All-in-One Chat as a Reply Channel
Inside the Customer Replied trigger, you will now see All-in-One Chat as an option under Reply Channel, alongside other channels like Email, Messenger, and more.
Additional Filters
Once Reply Channel is set to All-in-One Chat, two extra layers of filtering appear:
Chat Type filter - Choose between Chat Widget or Live Chat to decide whether the reply needs to come from a full chat widget experience or specifically from the live chat component.
Dynamic widget configuration selection - Based on your Chat Type selection, the next filter updates automatically. If Chat Type is Chat Widget, you see a dropdown listing only All-in-One Chat widgets. If Chat Type is Live Chat, you see a dropdown listing All-in-One Live Chat configurations.
How to Use It
- Go to Automation → Workflows
- Add a trigger: Customer Replied
- Under Reply Channel, select All In One Chat
- Choose Chat Type: Chat Widget or Live Chat
- Select the specific configuration
- Click Save Trigger, add your actions, and publish your workflow
Why This Matters
Previously, replies from unified chat experiences were harder to distinguish cleanly. Now you get a dedicated All-in-One Chat option with structured filters, making it easier to maintain workflows and keep routing and follow-ups consistent across chat sources.
Notes
- All-in-One Chat support is currently available only in the Customer Replied trigger
- Existing Chat Widget-based workflow triggers continue working as they do today
- No migration is required