Skip to content

Platform / Email Automations

Give every subscriber a useful next step.

Build welcome, nurture and follow-up journeys. Connect each email to the right audience, timing and customer context.

Start with the trigger
Triggers, waiting periods and follow-up in one flow. Example data.

HOW IT WORKS

A journey you can read from start to finish.

  1. 01

    Choose who enters

    Start from a supported signup, audience, field, tag, conversion or scheduled event. Set how often a person can enter.

  2. 02

    Write the path

    Add emails, waits, conditions, goals and audience updates. Branch on opens, clicks, replies, bounces or unsubscribes within the time window you choose.

  3. 03

    Check the sending setup

    Review the sender, audience, timing and connected accounts. Set send windows and frequency limits before publishing a version.

  4. 04

    Learn from delivery

    Review sends, opens, clicks and replies. Follow the run history to understand what happened and which step needs attention.

Let the next step follow the signal.

A welcome email, an answer to a reply and a later reminder serve different moments.

Read the details

Email Automations lets you describe that sequence on a visual canvas: who enters, which message they receive, how long to wait and what happens when a relevant event is recorded.

Start from a recipe when it matches the job, or use a blank journey for a more specific process. Configure the supported entry event and re-entry behavior before adding messages. This helps you distinguish a one-time welcome from a journey a person may legitimately enter again later.

Engagement conditions can use recorded opens, clicks, replies, bounces or unsubscribes within a chosen time window. Give each branch a reason to exist. A reply can call for personal attention, while a later message may help someone who has not responded. Recorded engagement is evidence for the condition, not proof that the recipient understood or wanted the offer.

Welcome
Explain what the subscriber signed up for and give them the useful first resource or action.
Nurture
Sequence relevant messages with a wait and a clear reason for the next step.
Re-engage
Use current audience eligibility and a deliberate entry rule before contacting an inactive subscriber.
Connect the conditions
Triggers, waiting periods and follow-up in one flow. Example data.

Different answers. Different paths.

Imagine a new subscriber requests information about a service.

Read the details

The journey sends the prepared welcome message, waits for the configured period and checks whether a reply was recorded in the selected window. The team reviews both the reply path and the no-reply path before publishing.

Keep the message relevant to the original request. A subscriber who replies may need the team to continue the conversation; another may benefit from a later explanation or booking link. Where the next step involves broader customer work, use the CRM and supported general Automation actions to coordinate it.

Before publishing a version, check the sender, connected accounts, audience and message content. Set the send window and frequency controls for the journey. Suppression, consent and sending limits still apply. After launch, inspect delivery and run history to understand what happened; an open or click cannot guarantee a sale or inbox placement. This is an illustrative journey, not a promised conversion result.

Control entry
Review the trigger, re-entry rule and cooldown so the same subscriber enters for the right reason.
Control timing
Use waits, send windows and frequency limits to make the sequence suitable for the audience.
Review the evidence
Distinguish recorded sends and engagement from the business outcome your team is trying to achieve.

Keep the message and the next action connected.

Use a dedicated email journey for subscriber follow-up and a general automation when the job spans other channels or modules.

Start with a useful recipe

Adapt a welcome series, re-engagement flow or reply follow-up. Set the audience and message to fit your business.

Explore the workflow

Send from a prepared domain

Set up the sender, check domain readiness and review delivery health. Sending remains subject to consent, suppression, account limits and usage costs.

Explore the workflow

Continue beyond email

Enroll a contact from customer work or an automation. Use the CRM record and general Automations for the next task or connected module action.

Explore the workflow

Before you start

Where do I build an email sequence?

Open Email, then Automations. Choose a recipe or create a journey on the visual canvas. You can configure emails, waits, conditions, goals and audience updates.

Can the path change when someone replies?

Yes. Configure an engagement condition for a reply, open, click, bounce or unsubscribe. Set the applicable time window and review both paths before publishing.

How are Email Automations different from general Automations?

Email Automations manages email nurture and subscriber journeys. General Automations reacts to customer or module events and coordinates actions across tools and channels. It can enroll a record into an email journey.

Can I control how often people receive messages?

Configure re-entry, cooldown, frequency limits and send windows for the journey. Consent, suppression and sending limits also apply.

Are email sends included without limits?

Plan, sender, provider and usage conditions apply. Check the sending setup and current credit terms before activating a journey. Delivery reporting shows recorded events; it cannot guarantee inbox placement or a response.