An email automation is not a pile of delayed messages. It is a small system that reacts to a documented event, checks what is true now and stops when its job is done.

That distinction prevents familiar mistakes: sending a sales pitch after purchase, onboarding someone twice, continuing a failed-payment sequence after recovery or emailing a person who withdrew consent.

Specify every automation on one page

For each journey, write:

  • Goal: the customer or operational outcome.
  • Entry event: the exact recorded event that starts it.
  • Eligibility: consent, product, locale and status conditions.
  • Messages: purpose and delay for each message.
  • Exit events: purchase, cancellation, reply, recovery or another terminal state.
  • Exclusions: people who must never enter.
  • Owner: who investigates failures and outdated copy.
  • Success measure: one primary outcome plus safety metrics.

“Joined a list” is weaker than “submitted form X, accepted wording version Y, locale Swedish, at timestamp Z”. The second record can be audited.

Four useful journeys

1. Requested-resource journey

Entry: a person requests a named guide and has the appropriate marketing status. Deliver the resource immediately, explain what they will receive next and send a short series that helps with the same problem. Exit on unsubscribe or when the person moves into a more relevant customer journey.

2. Purchase and onboarding journey

Entry: payment succeeds and access is granted. Send receipt and access information as transactional messages, then show the first useful action, where to get help and what happens next. Exit or branch when activation is recorded. Do not make access dependent on promotional consent.

3. Inactivity support journey

Entry: an enrolled learner has not reached a defined activation event within a defined time. Point to the exact next action and offer help. Stop after activation, support reply, refund or access expiry. Do not label a person “inactive” solely because an email tracking pixel did not load.

4. Failed-payment journey

Entry: the payment provider records a failed renewal. Explain the issue plainly and link to a secure account or hosted payment-update page. Never ask for card details by email. Stop immediately on recovery, cancellation or manual resolution.

Separate transactional and marketing purposes

A receipt, access notice or security message serves a different purpose from a launch promotion. Keep purpose, legal basis, templates and suppression rules explicit. A marketing unsubscribe should not prevent delivery of a necessary receipt, while a transactional event should not become a loophole for promotional copy.

Swedish law generally requires prior consent for email marketing to a natural person, with a limited existing-customer exception and an opt-out requirement; see sections 19–20 of the Swedish Marketing Practices Act. Rules depend on jurisdiction and context, so obtain advice for your operation.

Protect deliverability

Authenticate the sending domain and monitor failures, complaints and unsubscribes. Google currently requires all senders to Gmail to use SPF or DKIM; senders above 5,000 messages per day to personal Gmail accounts have additional SPF, DKIM, DMARC and one-click-unsubscribe requirements. Google says spam rates should stay below 0.3%. Read the current sender guidelines rather than copying an old setup checklist.

Measure state changes, not vanity

Open rates are affected by privacy features and image loading. Use delivery failures and complaints as safety metrics; then measure the journey’s actual job: activation, completed checkout, payment recovery, support resolution or retained membership.

Test with multiple addresses and states before enabling: new lead, existing customer, unsubscribed contact, already activated learner and failed-payment recovery. Keep a change log. An automation is production software even when it is drawn as boxes and arrows.

Idun Blue includes broadcasts, sequences and event-driven automations in the current internal beta. Join the waitlist to be considered when the first external creator workspaces open.