The automation builder

The flagship. A canvas where a sequence is a graph, a published version is immutable, and every outbound step passes the same gate a human send does.

Triggers that include the absence of something

Most builders trigger on events: a form submitted, a stage changed, a message received. Those exist here. So does the one most tools cannot express - nothing happened for a period of time. No reply in three days. No booking after a quote. No visit in six months.

A windowed count is a trigger too: three missed appointments in a quarter is a different customer from one.

Versioning that means something

Publishing a workflow freezes it. Instances already running finish on the version they started on, so editing a sequence never changes what is happening to a customer halfway through it. A new version starts new instances only.

Timers survive a restart

A wait step is a durable timer in the database, not a process holding a promise. A deploy, a crash or a restart does not lose it, and a worker that dies mid-step has its work reclaimed rather than dropped.

The gate runs on every send

An automation cannot send what a human could not send. Consent, registration state and channel capability are checked on every outbound step, and a step that cannot establish permission stops rather than trying. Read how the gate works.

Every sequence has an email path

Where a branch depends on text messaging being available, the disabled path reaches the same place. A tenant whose text traffic is still being registered keeps running rather than stopping.