Automations
Automations cookbook
The source trigger set, what the events represent, and three example recipes to verify against your build.
The public release record lists v0.2.0 as available by request. These notes are not a guarantee that every workflow or provider integration is enabled in your build. Check the release record and ask support to confirm version-specific setup.
The full trigger menu
The current source defines 18 events: customer created or updated; conversation opened, message received, or unassigned threshold; task created, completed, or overdue; order created, status changed, or cart abandoned; customer inactive threshold; ticket created, resolved, or priority changed; broadcast completed or failed; and WhatsApp connection degraded.
This source list does not mean every event is enabled in the invite-only public build. For a supported build, check which triggers and actions are exposed in its automation editor. Source events use queued, leased, processed, failed, or cancelled states; individual runs record their outcome.
Recipe 1: welcome on customer created
Example only: trigger on customer_created and create an internal follow-up task. Confirm the current build supports the trigger and chosen action; do not assume a customer message will be sent automatically.
Recipe 2: escalation on unassigned threshold
Example only: trigger on conversation_unassigned_threshold and route an internal alert or task if that action is available in your build.
Recipe 3: ops alert on connection degraded
Example only: use whatsapp_connection_degraded to prompt an operator follow-up if the deployed integration exposes this event and an approved action.
Next: request access to the desktop app or read the public changelog.