Automations
An automation (Flow) is a visual pipeline: one trigger that starts it, followed by a chain of actions, conditions and delays. You build it with drag-and-drop on the Automations page — no code.
Triggers — what starts the automation
| Trigger | When it fires |
|---|---|
| Keyword | A customer sends a message containing a word or phrase you defined |
| First message | A new contact writes for the first time |
| Webhook | An external system (form, store, CRM) calls a unique URL |
| Tag added / removed / changed | A contact's tags change |
| Field changed | A chosen field is set or changes value |
| Group added | A contact joins a group |
| Email engagement | An email is opened, a link clicked, bounced or unsubscribed |
| Event | Registration, cancellation, attendance, before or after an event starts |
| Zoom event | A Zoom event is scheduled, started, ended or canceled |
| Manual run | You run the flow on selected contacts |
Actions — what the automation does
- Send a WhatsApp message, an approved template or an email (with automatic WhatsApp fallback if the email isn't opened).
- Update the contact: change fields, add/remove tags and groups.
- Make an HTTP API call to any external system — custom URL, method and body.
- Register to an event, mark attendance or register to Zoom.
- Send an internal notification to an agent or the team.
Logic — conditions, splits and delays
- Condition — checks fields, tags and groups with a full operator set (equals, contains, is empty, greater than, in any group…) and splits the flow into yes/no branches.
- Wait — pauses the flow for a duration, with timezone support and wait rules.
- Channel router — tries the first available channel per contact (email or WhatsApp) with a separate branch when none is available.
- Capacity gate — limits the flow to the first N contacts (e.g. a perk for the first 100).
Variables — personalizing every message
Any text field accepts variables in [[...]] syntax — replaced with the real value at run time:
Variable syntax
[[contact.first_name]] → Dana
[[contact.custom_fields.city | upper]] → TEL AVIV
[[contact.name : friend]] → fallback when empty
[[event.start_time | date]] → formatted date💡 The variable picker in the editor lists every available field — including custom fields and event variables — so you never have to memorize paths.
The automation log
The Automation Log page records every run: which trigger fired it, which nodes ran, each node's input and output, and where the run stopped if it failed. It's the main tool for debugging flows.