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 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.
• Messages with waits follow. In a sequence they are one to five messages in a line, each with an editable wait before it; in a flow they are steps on a canvas that can branch, so each contact follows their own path.
• An event can stop it early — a cancellation event in a sequence, exit events in a flow: for example, a contact who completes a purchase stops receiving abandoned-cart reminders.

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. In a sequence the channel is fixed when you create it; in a flow each message step has its own. 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. Both are available; Flows is in beta.

	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 goals and several possible endings.	Beta

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: wait for the best moment for each contact, check whether they clicked or bought, and send something different to each group. Flows can also start from a ready-made template built around the events your project receives.

Explore the collection