Features · Automations
Sequences that run themselves, per site.
Pick one trigger, add Send Email, Wait, Condition and tag steps, and activate. Automations run about once a minute inside the workspace they belong to, only ever for subscribed contacts.
01 · What you get
How automations work in SendBeam.
- 01 Fourteen triggersContact created, Joined a list, Submitted a form, Tag added, Tag removed, Field updated, Anniversary of a date, On a specific date, Started via the API, Started by another automation, Cart abandoned, Product viewed, Order placed, Something happened elsewhere. Targets are optional — a specific tag, list or form, or any of them — and an automation may carry up to 3 triggers, any of which starts it. Triggers never fire retroactively; to run a sequence for existing contacts, tag them in bulk.
- 02 Ten step typesSend Email from a saved template or a custom subject and body; Wait in minutes, hours or days; Condition on status, tags, name, email or source, which FORKS — a yes branch and a no branch, both of which can carry on; Add Tag and Remove Tag; Update Field; Unsubscribe; Trigger Automation, which hands the contact to another automation; and Call Webhook, which tells your other systems the contact reached this point.
- 03 Templates stay liveA step that references a template sends whatever the template says at the moment of sending, so fixing a typo in the template fixes every future email in the sequence. Merge tags, open and click tracking, the unsubscribe link and the one-click unsubscribe header apply exactly as they do to campaigns.
- 04 Safe by defaultOnly contacts whose status is subscribed are enrolled, and status is checked again before every step, so an unsubscribe mid-sequence ends it without a Condition. A contact is never enrolled twice in the same automation while an earlier run is active; runs across different automations are independent.
- 05 See where everyone isThe automation’s Enrolled Contacts table shows each person’s status, current step and when their next action is due. Pause and activate from the dashboard or the API. Each email sent counts towards the account’s monthly allowance; if it is used up, the send is logged as failed and the contact moves on.
Plans. Live (active) automations, per workspace: Free 1, Starter 5, Pro and Business unlimited. Paused automations do not count. Compare plans.
02 · How it works
From zero to live.
The steps as they appear in the dashboard today. Each one is covered in more depth in the docs linked below.
- Step 01 Create the automationAutomations → add, in the workspace for the site it belongs to. Name it and choose the trigger and its target (which tag, list or form).
- Step 02 Add steps in orderSend Email, Wait, Condition, Add Tag, Remove Tag, Update Field, Unsubscribe and Trigger Automation. Steps run in order, and a Condition splits the path in two.
- Step 03 Point emails at templatesCreate a template per email in the sequence so you can edit copy later without touching the automation.
- Step 04 ActivateFrom then on, matching events enrol subscribed contacts. Processing happens about once a minute.
- Step 05 Check enrolmentsWatch the Enrolled Contacts table after the first few signups, then leave it running.
03 · Questions
Asked before choosing automations.
- Can an automation in one workspace email contacts from another?
- No. Automations, contacts and templates are all scoped to their workspace. Build the sequence again in the second workspace (or ask for it as a Move-in setup item).
- Is there branching?
- Yes. A Condition forks: one path for contacts who match and another for those who do not, each with its own steps, and the two can rejoin later. You do not need two automations with opposite conditions.
- Will importing a CSV fire my welcome series?
- Contact Created fires for every newly created subscribed contact in an import, so pause the welcome automation first or import with the default status set to Unsubscribed. Contacts that already existed are not enrolled.
- How quickly does a lead magnet arrive?
- Steps are processed about once a minute, so a Form Submitted trigger followed by an immediate Send Email step lands within a minute or so of the submission.
More features
- Sending guardrail A brake that stops one bad send becoming a dead domain.An automatic brake on a workspace whose mail has started going wrong — before a provider or a blocklist does it for you.
- Workspaces Run every site’s email from one account.One account for every site you run. A workspace per site, one plan for all of them.
- Forms Signup and contact forms that fit any site.Signup forms with double opt-in and contact forms that email you, both protected by Turnstile and an origin allow-list.
- Sending domains Every site sends from its own domain.A verified domain per site, DKIM and an aligned return path, and the CNAME records to publish.
- API One REST API for every workspace.A REST API per workspace for contacts, lists, segments, campaigns, forms and single transactional sends.
04 · Start
Start with the site you run today.
Free to start, no card, no trial clock. Each site keeps its own domain, list and rules; you add the next one as a workspace whenever you launch it.
Checking system status