Skip to main content

Automations

Automations cookbook

The sixteen triggers, what they are good for, and three recipes worth copying.

The full trigger menu

Customer: created, updated. Conversations: opened, message received, unassigned threshold. Tasks: created, completed, overdue. Orders: created, status changed. Tickets: created, resolved, priority changed. Broadcasts: completed, failed. Infrastructure: WhatsApp connection degraded.

Every trigger event follows one lifecycle: queued, leased, processed, failed, cancelled. Every run records its execution status. If a rule did not do what you expected, the event history says why.

Recipe 1: welcome on customer created

Trigger: customer_created. Action: send a template greeting and create a task for an agent to introduce the catalog within one business day. First contact while intent is warm.

Recipe 2: escalation on unassigned threshold

Trigger: conversation_unassigned_threshold. Action: notify the support manager. Coverage gaps become visible instead of discovered by angry customers.

Recipe 3: ops alert on connection degraded

Trigger: whatsapp_connection_degraded. Action: create a high-priority ticket. A channel outage is an operational incident, not a mystery to be noticed by customers first.