Automations

An automation sends messages on its own, triggered by something a contact does — an order is placed, a cart is abandoned, a contact joins a segment. Each automation listens for a trigger event and, when it fires, enrols the contact and sends a short series of messages with waits in between. This page is the map of the collection: what an automation is, the two shapes it comes in, and where each part is documented.

What an automation is

An automation is built around a simple shape:

• A trigger event starts it — when the event happens for a contact, that contact is enrolled.
• A sequence of one to five messages is sent, each with an editable wait before it (the first wait is measured from the trigger, the rest from the previous message).
• An optional cancellation event stops the sequence early — for example, a contact who completes a purchase leaves an abandoned-cart sequence.

Unlike a campaign, which is a one-time send you launch by hand, an automation runs continuously in the background: once it's active, every contact who triggers the event flows through it.

Channel

Automations send over SMS and RCS. The channel is fixed when you create the automation. WhatsApp is coming soon for automations — it's available for campaigns today, but not yet here.

Sequences and Flows

Automations are built with two tools. Neither replaces the other: they solve different problems and you pick the one that fits. Only Sequences is available today; Flows is coming soon.

	What it is	Status
Sequences	A linear series: trigger → messages with waits → optional cancellation. The same path for every enrolled contact.	Available
Flows	A builder on a visual canvas: each contact follows their own path through sends, waits and branches, with several possible endings.	Soon

Use a Sequence whenever the same set of messages should go to everyone the trigger enrols — a welcome series, an abandoned-cart reminder, a post-purchase follow-up. Use a Flow when the path itself has to change with what each contact does. Until Flows ships, a Sequence with a cancellation event already covers the most common branch — "stop if they convert".

Explore the collection