Grow · Lifecycle workflows

Lifecycle email automation for SaaS, already written

Atlis workflows send the right email when a user does something, or stops doing it, such as not activating in 48 hours, a failed payment or a pricing page visit. Pick from 30 triggers, start from a ready-written template and switch it on; Atlis handles timing, follow-ups and stopping.

Every plan, including Free; billing triggers need Stripe, Paddle, the Server API or a CRM mappingUpdated

Workflows · Ledgerly
Add a stepOnly ifSplit by productFollow-upA/B testSlack alert
TriggerReceivingSigned up, no milestone after 48h
WaitSend at their usual hourBest time on
Only ifOnly if plan type is TrialChecked again before every email
SplitSplit by productBooksPayrollEveryone else
Email 1A/BYou're one step from your first reportDefaultBooksPayroll
Wait 2 days
Follow-up 1A 2-minute guide to your first report
EndsStops when they activate

Example workflows for a sample company.

How it works

How does lifecycle email automation work?

  1. 1

    Pick a trigger

    Onboarding, engagement, trial, billing and churn moments, your key pages or any event your app sends.

  2. 2

    Shape it on the canvas

    Start from one of three ready-written templates, then add Only if rules, a version per product, follow-ups and stop rules, one step at a time.

  3. 3

    Switch it on

    Atlis sends at the right moment, holds emails that would land too close together, and stops when the person acts.

What you get

What's included in Lifecycle workflows

  • 30 built-in triggers

    From Not activated in 48h and Inactive 7 days to Payment failed, Plan downgraded and Cancellation page visited, plus your own events.

  • Up to 5 emails per workflow

    Add follow-ups with waits in hours or days. If the trigger happens again, follow-ups start over instead of doubling up.

  • A visual workflow canvas

    Every workflow drawn top to bottom: trigger, wait, rules, split, emails and stop rules, with settings beside the step you click.

  • Stops when they act

    Up to 3 events that end the workflow the moment the person does one, including reaching your activation milestone.

  • Only if rules

    Up to 5 rules on plan, stage, health, events they did or skipped, signup date, loyalty or any of your fields, checked again before every email.

  • A version per product

    One workflow, a different email for each product or plan, and a default for everyone else. {{product}} fills in their product.

  • Best-time sending

    Scheduled workflows send at the hour each person is usually active, with a comparison group so you can see the difference.

  • A/B tests that finish themselves

    Test two versions of a scheduled workflow's first email; once one is clearly better, Atlis keeps it and ends the test.

  • Key page workflows

    Email people who visit pricing, upgrade or cancel pages, without writing code.

  • Safe when tracking breaks

    If your app stops sending data, Inactive and Not activated emails wait for anyone who may still be active, so a broken snippet never tells active users you miss them.

  • Invite links in any email

    {{referralLink}} gives each person their own invite link to your app, and Atlis credits every signup it brings.

  • Results and a lifecycle overview

    Sent and the result that matters on every workflow, plus an overview of what is running, what's a draft and what can't send yet.

Use cases

How founders use it

Get signups to their first win

Not activated in 48h nudges people toward your activation milestone and stops as soon as they reach it.

Turn trials into customers

Trial expiring emails go out three days before the end, at each person's usual hour.

Recover failed payments

Connect Stripe or Paddle and Payment failed emails the customer straight away.

FAQ

Lifecycle workflows: questions and answers

Plan and limits

Every plan, including Free; billing triggers need Stripe, Paddle, the Server API or a CRM mapping.

Good to know
  • Email only; Atlis doesn't send SMS, push or in-app messages.
  • Scheduled emails to one person are spaced at least 20 hours apart; billing emails and emails triggered by an action are never held.
  • Billing triggers need a source: Stripe or Paddle (Starter and above), the Server API (Growth and Scale) or a CRM status mapping.
Compare every plan
01

What is a lifecycle workflow?

An email, or a short sequence of up to 5, that Atlis sends when a user hits a moment in their lifecycle, such as signing up without activating or a payment failing.

02

Do I have to write the emails?

No. Each built-in trigger has three ready-written templates, each with a follow-up. Use one as it is or edit it.

03

How is this different from a drip campaign?

A drip sends on a fixed schedule. Atlis sends when something happens, waits for the right hour and stops the moment the person does what the email asks.

04

Can one workflow send different emails for each product?

Yes. Split a workflow by product, or any field, and write a version of each email for up to 4 values. Everyone else gets the default, and timing and stop rules stay shared.

05

What happens if my tracking breaks?

When no data arrives for 3 days, Inactive, Usage dropped and Not activated hold their emails for anyone who may still be active, and their cards say On hold. People who were already inactive before still get them, and the rest are checked again once data is back.

06

Which plan includes workflows?

Every plan, including Free. Billing triggers need a billing source such as Stripe or Paddle, available from Starter.

See who's about to buy or cancel, this week.

Connect your app in about 10 minutes. Atlis sorts every user, ranks your next best moves and sends the right email for you.

14 days of Growth free, then free forever up to 250 users · No credit card