Skip to main content
The trigger is chosen when you create the automation and changed in Settings → What starts it. In every case, the person must be subscribed (not unconfirmed, not unsubscribed) on the automation’s list, and inside its segment when it has one.

Someone subscribes to the list

Every new confirmed subscriber comes in: straight away on a list without double opt-in, at the click on the confirmation link otherwise. Whatever they came from: a form, an import, the API, or being added by hand. It is the trigger of welcome series.

A tag is added

The subscriber comes in as soon as the chosen tag is put on them, by anyone: the team, an import, the API, another automation, or the subscriber themselves on their preferences page. Any tag sets it off on every tag added.
Your shop adds the abandoned-basket tag through the API; the automation sends a reminder two hours later, unless the “buys something” goal is reached in the meantime.

A tag is removed

The same, when the tag is taken off.

A date of the subscriber comes round

Checked every day. Settings:
attribute name
required
The custom attribute that holds the date: birth_date, joined_on. Write the dates as YYYY-MM-DD (1990-11-01) to leave no doubt between day and month. Only the day and the month count.
0 to 365
default:"0"
Come in a few days before the date. 0 means the day itself.
The subscriber comes in once a day at most, so once a year for a birthday.

A webhook is called

Your application sends an e-mail address to the automation’s address, shown with a Copy button:
The person is subscribed to the list if they are not on it (without confirmation), then enters the journey; the first actions run at once. The address holds a secret: treat it like a password.
From a server, prefer the API with its token, which works with any trigger: see Automations through the API.

Nothing: subscribers are added by hand

Nobody comes in on their own. You pick who does, from the Subscribers → Add subscribers tab, or your application brings them in through the API.