Fire an automation from a tag, from a changed attribute, or from an API call inside your own application. Branch on what they opened. Post a webhook back to your systems mid-flow. Lifecycle segments built on real engagement, not on a signup date.
Most lifecycle email fails at the same point: the tool has no idea what happened inside the product. So you send a "getting started" sequence to someone who finished onboarding on Tuesday, and a feature announcement to someone who churned in March.
Twelve triggers ship with the flow builder. Three of them are the ones a SaaS actually needs: tag added, attribute changed, and a call to the API. Your application already knows when a workspace is created, when a key is issued, when a plan is upgraded. Tell CleverlyBox, and the flow starts.
Highlighted: the three most SaaS teams build on.
"Day 3 of onboarding" is a guess. "Has not yet invited a teammate" is a fact. Push the fact into a field or a tag, and the flow branches on the thing that actually matters.
Update a custom field — plan, seat count, workspace count, integration connected — and the attribute-changed trigger fires. An upgrade sequence, a downgrade save, an onboarding branch for the new tier: all keyed off the field your product already writes.
A webhook node inside the automation POSTs to your endpoint at whatever step you place it. The email sequence stops being a dead end and becomes part of your system — it can create a task, ping Slack, or set a flag on the account.
Copy-to-list and move-to-list nodes mean a contact who activates ends up on the activated list without anyone touching a CSV. The list becomes a consequence of behaviour rather than a manual chore.
Illustrative shape, not the literal schema — see the API reference in-app.
A REST API to create and update contacts, manage lists, tags and fields, and trigger automations from your own code. Webhooks for opens and clicks so the events land in your warehouse or CRM as they happen, not in a nightly CSV.
There is also an SMTP relay — point your application, your WordPress site or your n8n workflows at CleverlyBox and the transactional path goes through the same authenticated, monitored sending you use for campaigns.
Segments combine your fields with real engagement — last opened within N days, last clicked within N days, tag membership, created date, verification status. Which means the lifecycle stage is computed, not curated.
Created-date plus the absence of a tag. This is the segment where every additional email has to earn its place, and where a wrong one costs you the account.
A field match on the plan and a click recency operator. The people you can talk to about a new feature without softening it first.
Still paying, no longer listening. The most valuable segment nobody builds, because most tools cannot express it without an export.
The goodbye trigger and the tag-removed trigger both exist. A cancellation can end a sequence cleanly and start an honest one — including the win-back you send three months later.
The sending platform. The verification service you bolted on when signups started arriving with typos. The automation tool. The AI writer someone expensed. CleverlyBox is all four, and sending is included — there is no separate relay to provision and no AWS console to learn.
If your infrastructure team has opinions, nine sending providers are supported from the Business tier, including Amazon SES, SendGrid, Mailgun, SparkPost and any SMTP. Deliverability is monitored either way: SPF, DKIM and DMARC verified in-app, IP warm-up, and automatic pause when bounce or complaint rates spike.
Yes. API is one of the twelve triggers — your code calls CleverlyBox and the flow begins. Tag-added and attribute-changed triggers cover the other common path: push a tag or update a custom field, and the sequence fires off the state change.
A webhook node can sit at any step of an automation and POST to your endpoint. Separately, open and click events can be pushed to you by webhook. The email flow is part of your system rather than a black box beside it.
There is an SMTP relay — point your application, WordPress site or n8n workflows at CleverlyBox and that mail goes through the same authenticated, monitored sending path as your campaigns. It's included on Business and Agency, metered separately from your campaign allowance — here's how it works.
As a segment. Match your plan field to the paid value, then add the engagement operator — has not opened within 60 days. Both are native conditions; you do not export anything to work it out.
No. Sending is included with no setup, which is the fastest route. From the Business tier you can instead route through Amazon SES, SendGrid, Mailgun, SparkPost, Elastic Email, Blastengine, Gmail OAuth, Sendmail or any SMTP server.
Twelve triggers, a REST API, webhooks in and out. One platform.