Build an automation

6 min read84
Copy for AI:

In Delivery β€Ί Automations you build rules that send email on their own: someone meets the trigger, enters the automation and goes through the steps at the pace you set. At Casa Moura CafΓ©s, Renata uses the Welcome automation to greet everyone who joins the Store customers list with an introduction email and, two days later, a second email on where to start.

Click New automation to build from scratch, or Use a template to start from a ready one. The editor has four blocks: Identification, Trigger, Steps and Settings.

The trigger: who gets in

In What fires it, pick the trigger. Triggers fall into two groups, and the difference changes how the whole automation behaves.

Date triggers: run once a day

  • Birthday (yearly date) β€” whoever has the field's date that day, looking only at day and month. Only that day's people, never the whole month. Pick the Date field: sign-up date, consent date or a custom field of type date.
  • Days before or after a date β€” whoever is N days from the field's date. In Days relative to the date, positive is after (7 = post-purchase) and negative is before (βˆ’7 = renewal reminder), from βˆ’365 to 365.
  • Is in the segment (daily) β€” whoever is in the segment that day. With Exit when leaving the segment on, anyone who leaves the segment before the next step does not get it.

For these three, Settings shows a Send time field: the sweep runs once a day, from that time on, in the automation's time zone.

Event triggers: watch what happens

  • Joined a list β€” by form, import or API. This is the Welcome trigger, with the Store customers list.
  • New contact with consent β€” whoever just entered the base already with consent. In Consent sources you can limit it to certain sources; empty accepts any.
  • Custom field became β€” when a field changes to a value (became equal to) or to one of several (became one of).
  • Clicked a campaign β€” any link of a sent campaign or, if you fill in Specific link (optional), only that one.
  • Opened but didn't click and Received but didn't open β€” pick the campaign and the Days to wait (1 to 90). The first step only goes out after that period, and anyone who clicks (or opens) in the meantime leaves before receiving it.
  • Completed another automation β€” whoever reached the end of another automation. This is how you chain sequences.

Campaign triggers only offer campaigns that were already sent: before sending, there is no behavior to watch.

An automation never looks back. When it is turned on for the first time, it considers what happens from then on β€” someone who joined the Store customers list last week does not get the welcome because of it.

The steps: what happens to whoever got in

Steps run in list order, top to bottom, and each step's arrows change that order. The counter shows how many of the 20 available you have used, and every automation needs at least one email.

  • Add email β€” Subject, Preheader, Sender, Category and the HTML, with the same tools as the campaign editor: use and save templates, see the variables, generate with AI and check it in the Preview tab.
  • Add wait β€” an amount in hours or days, at most 90 days. In Welcome, the 2-day wait sits between the two emails.
  • Add condition β€” the If step, which splits the path.

Each email's content is frozen the moment it goes out: editing the step later does not change what was already sent.

The condition: splitting the path

In the If step, build the conditions as you would in a segment β€” Contact data, Custom field, List or Engagement β€” and set in How to combine the conditions whether All or Any must hold. Those who match move on to the next step. For those who don't, choose in Those who don't match: jump to a later step or Leave the automation.

In Welcome, Renata added an If after the second email with the custom field cafe_preferido equal to Yellow Bourbon, followed by an email presenting the new lot of that coffee. Anyone who prefers another coffee leaves the automation there.

Three rules the editor enforces, and why:

  • The branch only points forward β€” going back would create an endless loop.
  • There is no branch to the very next step: both paths would end up in the same place.
  • A condition cannot be the last step, because whoever matches it would have nowhere to go.

The branch follows the step, not its number: reordering with the arrows does not make it point to a different step.

Settings: time zone, send time and re-entry

  • Time zone β€” the birthday's "today" and the send time are read in it, not in the time zone of whoever is using the screen.
  • Send time β€” date triggers only.
  • Re-entry β€” whether the same person can go through the automation more than once: Once only, Once per cycle or Again after N days, with the period in Days until it can come back.

Whatever the option, nobody enters twice at the same time: while a person is still going through the steps, they do not enter again.

Mind what the cycle is for each trigger. For Birthday and Days before or after a date, re-entry is locked to Once per cycle: the 2027 birthday is not the 2026 one. For Is in the segment (daily), the cycle is the day β€” with Once per cycle, someone still in the segment can enter again the day after finishing. For re-engagement, prefer Again after N days.

Who would enter today

Next to the editor, the Who would enter today panel shows how many contacts the trigger would find today, plus a few examples. It applies to date triggers; event triggers have no "today" to show. Check it before turning the automation on: if a birthday preview brings far more people than you expected, review the date field you picked.

Saving is not turning on

Saving keeps the automation as a Draft, and nothing is sent. To start, turn it on in the Activation panel β€” what it takes and what happens next is in the Turn on, pause and monitor automations article.

Where to go next

  • Turn on, pause and monitor automations β€” go live and see who is going through.
  • Start from an automation template β€” nine ready automations to adjust.
  • Segments β€” the audiences behind the daily trigger and the conditions.
  • Templates β€” the HTML you reuse in email steps.

In short: pick a date or event trigger, build the steps in the order they should happen (with at least one email), use the condition to split the path, set time zone, send time and re-entry with the trigger's cycle in mind, and remember that saving leaves the automation as a draft until you turn it on.

Was this article helpful?