Automation Templates

What it is

An automation here is not a diagram you have to maintain. It is the platform doing the obvious next thing: money lands, the thing they bought is issued, the receipt goes, the follow-up is scheduled, and the record is written.

• Message sequences with a wait, a template and conditions on every step
• Stop rules that matter: stop if they reply, stop if they buy, stop if they finish the thing you are chasing them about
• Send windows that respect the hour where the person actually is
• Templates that keep their old versions, so you can answer what somebody received in September with the exact words
• Automatic replies on filing addresses
• An event goes out when something happens, so another product or an outside tool can act on it
• Signed outbound webhooks per company, for Zapier, Make, n8n and the rest

1. A payment, a form, an enrolment or a signature raises an event
2. The event is recorded and handed to whatever is listening
3. Sequences run on the platform's own mail engine; there is no second email system
4. Every send is written to the outbox with its full body kept