Automations
Workflows that fire when something actually happens.
Not a calendar. Not a blast. Real triggers, real branching, real time delays — the sequences your customers go through, mapped to what they do.
Included on every paid plan. Templates ready out of the box.
How it works
Automations look like this.
An honest example, not a marketing diagram. A trial expires, a tag fires, the workflow waits, then asks one question and routes the contact accordingly.
Drag-drop on the canvas, with branches that get their own conversion numbers. No duplicating the workflow just to test a path.
Triggers
Ten ways to start a workflow.
Real events from your account — behavior, CRM, dates, your own app. The automation fires when the thing actually happens, not on a Tuesday at 9.
- Contact added
- Tag added
- List joined
- Email opened
- Link clicked
- Deal stage changed
- Activity overdue
- Date-based
- Form submitted
- Webhook
Start fast
Templates that ship before your second coffee.
Drop one in, swap the copy, point it at a list. Each template arrives wired up — the waits, the branches, the conversion goal. You only edit what's actually yours.
Welcome series
Greet new signups, teach the product, then make the ask. Five touches, two waits, one conversion goal.
- New signup
- Welcome email
- Wait 2 days · tutorial
- Wait 5 days · upsell
Abandoned cart
A nudge first, then a deal. The math is boring; the recovered revenue is not.
- Cart created
- Wait 1 hour · reminder
- Wait 1 day
- Discount offer
Re-engagement
Inactive for a month? Send a "we miss you," then branch on whether they opened it. Tag accordingly.
- Inactive 30 days
- “We miss you” email
- Branch on open
- Tag accordingly
Post-purchase upsell
Five days after the receipt clears, the cross-sell goes out. Quiet, polite, dependable.
- Purchase
- Wait 5 days
- Cross-sell email
Triggers, branches, and the stuff under the hood.
How automations behave in flight, talk to the CRM, and stay isolated per client workspace.
Behavior triggers (tag added or removed, list joined, email opened, link clicked), CRM triggers (deal stage changed, deal created, activity overdue), date triggers (birthday, signup anniversary, custom date field), RSS feed updates, and inbound API or webhook calls from your own app.
Yes. Pause the automation, edit the steps, and resume — every in-flight contact stays at their current step and continues from there. No need to clone, rebuild, or restart.
Relative delays ("wait 3 days") run from when the contact entered the step. Absolute delays ("Tuesday at 9am") respect each contact’s timezone if you have it on file, otherwise the workspace timezone. Business-hours-only delays are supported.
Yes — that’s the point. When a deal stage changes, an activity goes overdue, or a deal is created, an automation can fire in the same workspace. It works the other way too: an automation can update a contact field or move a deal forward.
Yes. Every client workspace has its own automations, its own templates, its own goal reports. Nothing crosses between accounts. Switch workspaces in one click and you’re in a fully separate environment.
Yes. Conditional branches split on contact attributes (tag, list membership, custom field), engagement (opened or clicked a specific email), CRM state (deal stage, account owner), or any combination. Each branch has its own downstream steps.
Still have questions?
Reply to any product email or drop us a note — answers come from the engineer who shipped the feature, not a triage form.
Wire up one workflow. Watch it work.
Pick a template, point it at a real list, and let it run for a week. The numbers will tell you whether it's better than what you had — they always do.
Start free