Mailing scripts, sequences and system emails

Writing the emails, sending one to a list, drip sequences as flows, and the site's system emails.

Scripts

/scripts — a script is one email: subject, HTML body, and the placeholders it uses. Available in every script:

• {{first_name}} {{last_name}} {{email}}
• {{site_name}} {{sender_address}}
• {{unsubscribe_url}} — required in broadcast mail; a body without it is refused
• {{preferences_url}}

Scripts are shared with Newsletters as templates, where a Monaco editor, MJML import and AI assistance (subject lines, copy improvement, spam check) are available.

Send a mailing

Send mailing (/apacs?mail) sends one script to one list, now. For scheduling, A/B subjects, analytics and deliverability, use a newsletter campaign — same script, more control. See Newsletters.

Sequences (drips)

A sequence is a flow: add subscriber → send email → set delay → send email … Build it on the canvas (/apacs-flows shows the ones that are sequences), or let the create-flow tool build it. A person is enrolled by an opt-in, a purchase, another flow or an agent, and the engine sends each email when its delay elapses.

System emails

The emails the site itself sends — welcome, verification code, password reset, ticket received — are scripts too, edited under System emails in APACS. Placeholders specific to each are listed on its edit page.

Cost

Sequence and newsletter mail is metered per recipient in service credits; system mail is not. See Service credits.