// automations — follow-ups that run themselves
Somebody left a full cart. An invoice went unpaid. A client signed three weeks ago and nobody checked in. Build the response once, from an event that already happens in your business, and it happens every time after that.
No app connecting · no per-task bill
Connect the shop to the mailer. Authorise it. Map the fields. Discover the field you needed is not exposed. Pay per task. Then something changes at one end and it quietly stops, and you find out from a customer.
// how it works
A cart left behind, an invoice paid, a quote signed, a class nearly full. Real events, already happening in your workspace.
Conditions, waits and branches — and unlike a checklist, paths can split apart and come back together.
Edit the words, not the layout. Or take full control with raw HTML and merge tags when you want it.
Who is enrolled, who is excluded, and whether anyone can enter twice — decided once, then it looks after itself.
// what can start a flow
Nothing to connect, because it is all one system. The order, the payment, the signature and the booking are already in here — a flow just listens for one.
Shop
Cart abandoned · Order placed · Order fulfilled · Back in stock
Money
Invoice paid · Subscription renewed · Payment failed · Upcoming charge
Sales
Quote agreed · Deal won · New client captured
Bookings
Appointment booked · Session registered · Waitlisted · Reminder due
Audience
Newsletter subscribed · Guide downloaded · Loyalty reward reached
Quiet
A contact who has gone dormant
// vs. a connector tool
A connector exists because your tools are separate. When the shop, the invoices, the CRM and the mail are one system, most of that work simply is not there to do.
// set it running
The follow-ups you know you should send, sent — whether or not anyone remembers.