Skip to main content
bthebigclass
All help topics

For creators

Build an automation (when → do)

An automation is one rule: when something happens, do something. Pick a trigger (a purchase, or a contact getting a tag), pick an action (send an email, send a WhatsApp, or add a tag), optionally make it wait a few days, and switch it on.

Last updated Jun 4, 2026

On Marketing (/dashboard/marketing), use the Automations card. Name the rule, choose a trigger and an action, fill in the action's details, and click create. It runs on every matching event from then on.

Triggers — what starts it

  • When someone makes a purchase — fires the moment an order is paid.
  • When a contact gets a tag — fires when a tag is added. Leave the tag blank to match any tag, or name one (e.g. lead) to fire only for that tag.

Actions — what it does

  • Send an email — subject + body. Use {{name}} and it's replaced with the contact's name (or 'there' if unknown).
  • Send a WhatsApp message — text, same {{name}} support. Goes only to contacts who have a phone number.
  • Add a tag — tags the contact, which can itself trigger another automation (that's how you chain steps today).

Wait before running

Set 'Wait (days)' above zero and the action is scheduled for later instead of running immediately — e.g. 'when someone buys → wait 3 days → send a check-in email'. A background job runs due steps about every 30 minutes.

Email and WhatsApp use the same senders as your class invites and announcements. If a sender isn't configured yet, the message is logged on the backend instead of sent — the automation never errors or blocks the purchase that triggered it.
A single automation is one step. To build a multi-step sequence today, chain rules: 'buy → add tag onboarding-1', then 'tagged onboarding-1 → wait 2 days → email'. Native multi-step sequences as one object are on the roadmap.

Related