How to Build a Welcome Email Sequence in systeme.io (Tested End to End)

Every welcome-sequence tutorial for systeme.io teaches the same shape: someone joins your list, a tag gets added, and an automation fires off a welcome email, waits two days, sends the second, waits, sends the third. It looks simple on the whiteboard. I tried to build it in a real systeme.io account in October 2026, on the free plan, with double opt-in turned on, and it fell apart in two different places before a single welcome email could go out.

First, the pattern can't be built the way the tutorials draw it: automation rules have no wait step, and the free plan gives you one rule. Second, the per-form automation I built instead applied its tag to zero of three confirmed subscribers, at ten minutes and again at twenty-four hours. The confirmation emails arrived fine. The automation actions just never fired.

This guide walks through exactly what I built, where it broke, and the one delivery pattern that actually worked.

Who this is for

• You have a free systeme.io account and want new subscribers to receive welcome content reliably.
• You run double opt-in (or plan to). Every result here was measured with it on.
• You'd rather know the limits before you build than discover them after launch.

Who should skip this

• You're on a paid plan building sequences in Workflows. I couldn't test that surface on free, and this guide gives no verdict on it.
• You don't use double opt-in. Everything below was tested with it on, because that's the compliant setup I test.
• You need a timed three-email sequence running this week on the free plan. It can't be built the way the tutorials teach it. The honest alternative is below.

The problem

The most-shared tutorial pattern, wignaledwards' "minimum viable automation" is the clearest example, goes like this: tag added, send welcome email immediately, wait 2 days, send email 2, wait, send email 3. Their troubleshooting section covers tag mismatches. It doesn't cover double opt-in at all.

systeme.io's own help article (284) teaches a different entry point, a form-subscribed trigger feeding a subscribe-to-campaign action. But guide #1 already proved that action delivers zero emails to double-opt-in confirmed subscribers. So the official pattern and the popular pattern both rest on actions I had already watched fail.

And then there's the structural problem nobody mentions. The "wait 2 days" step has nowhere to live. I'll show you where it dies.

The tested setup

Step 1 — Know your constraints before you build

I started by surveying the account. Exactly one automation rule existed: rule 2444498, active, wired as "Funnel step form subscribed" on the live funnel, action "Subscribe to campaign", campaign "Checklist delivery". Its execution history was empty from September 30 to October 10, despite seven contacts joining in that window. The rule simply never fired for double-opt-in signups.

The account had zero tags (the single tag slot was free), double opt-in was on for the test funnel, and the free plan allows exactly one automation rule and one tag. I left the live funnel and the live rule untouched for the whole test.

Screenshot: the one automation rule in the account before testing, October 2026.

Step 2 — Try to build the tutorial pattern: the 1-rule wall

To build the tutorial pattern I'd need a rule that triggers on tag-added, sends an email, waits two days, and sends two more. Two problems showed up immediately.

First, the rule builder opens fine. Nothing stops you from starting a second rule. But the moment you try to save it, systeme.io answers:

"You have exceeded the limits of your plan."

The rule is not saved. The limit is enforced at save time, not at the builder door, which means you can do the whole configuration dance before learning it was pointless. (The message above is quoted verbatim from the test session; no screenshot of that moment is used in this guide.)

Second, the action list in automation rules has no wait or delay step at all. There is nowhere to put "wait 2 days." Sequencing with pauses is a Workflows thing, and I couldn't test Workflows on the free plan. So even with unlimited rules, the tutorial pattern as drawn cannot be assembled inside a free-plan rule.

Step 3 — Try the per-form route instead

The test funnel's form editor has its own "Add automation rule" option, separate from the global rules list. I created one: on form submit, "Add a tag", tag "TEST - welcome tag" (a tag I created for the test, filling the single tag slot). The page saved. The global rule count stayed at one. Per-form rules don't consume the global slot, which makes them the obvious workaround when you're out of rule slots.

If this fired, I'd have a tag applied at signup, the trigger the tutorial pattern needs. Worth testing. (The rule saved and stayed saved — its effect, or lack of it, is what the next step measures.)

Step 4 — Run three signups through it: 0 for 3

I signed up three controlled addresses (wel1, wel2, wel3), double opt-in on. All three confirmed, "Registration confirmed", and all three confirmation emails arrived within a minute or two. The delivery plumbing works.

The tag did not. Ten minutes after the third confirmation, I checked all three contacts: no "TEST - welcome tag" on any of them, and every contact's Automation tasks tab was empty. The tag's own page showed total contacts: 0.

Screenshot: confirmed contact with no tag and no automation activity, October 2026.

Screenshot: the test tag's own page — 0 contacts today, yesterday, and in total, October 2026.

Twenty-four hours later I checked again. Still 0 for 3. No tag, no automation activity, and no late welcome email in Gmail (I searched for the test subject, nothing). I checked again at three days and at five days. Same result every time: 0 for 3, tag total 0, zero late emails. The per-form tag automation isn't slow. It's dead under double opt-in, the same way the email and campaign actions were dead in guide #1's tests. The failure isn't about tags specifically. It's that automation actions don't fire for double-opt-in funnel signups on this plan. Five days, no movement — I'm done checking.

Step 5 — What actually works: skip the automation, redirect the form

Here's the part that saves the guide. Guide #1 already proved the working pattern: don't rely on an automation action to deliver your welcome content. Redirect the form to a thank-you page and put the content, the download button, the welcome message, the next step, right there on the page. The subscriber sees it the second they confirm, with no automation in the middle to silently fail.

That's not a "sequence" in the tutorial sense. It's one reliable delivery instead of three unreliable ones. On the free plan with double opt-in on, it's the only welcome delivery I could verify end to end. The full walkthrough, with every click, is in How to Set Up Email Automation in systeme.io (Tested End to End).

Evidence — what happened when I ran it

• Oct 10, free plan — Survey account: 1 active automation rule (2444498), history empty Sept 30 to Oct 10 despite 7 contacts in window. 0 tags. Double opt-in on. Observed: the rule never fired for double-opt-in signups.
• Oct 10 — Build second automation rule (tag-added trigger pattern). Blocked: "You have exceeded the limits of your plan" at save time. Rule not saved.
• Oct 10 — Inspect rule action list for a wait/delay step. Not there: no wait action exists in automation rules.
• Oct 10 — Create "TEST - welcome tag" (fills the 1-tag slot). Pass: tag created, 0 contacts.
• Oct 10 — Create per-form rule on test page: Add a tag, TEST - welcome tag. Pass: saved; global rule count stayed at 1. Per-form rules don't consume the global slot.
• Oct 10 — 3 controlled signups, double opt-in on, all confirmed. Confirmations arrived 3/3 in 1 to 2 min. Pass on delivery plumbing.
• Oct 10 (~10 min after) — Check 3 contacts for the tag. Fail: 0/3 tagged; Automation tasks tabs empty; tag total contacts 0.
• Oct 11 (24h check) — Re-check contacts, tag page, rule history, Gmail. Fail: still 0/3; no late tag, no welcome email, rule history still empty. The automation isn't delayed, it's dead.
• Oct 13 (3d check) — Re-check contacts, tag page, rule history, Gmail. Fail: still 0/3; no late tag, no welcome email, rule history still empty.
• Oct 15 (5d check, final) — Re-check contacts, tag page, Gmail. Fail: 0/3 across 5 days; tag "TIMES ADDED: 0"; no late welcome emails. Phase 2 closed — no further delivery checks.
• Oct 18, free plan — Deleted the silent funnel-level rule and added a form-level rule on the live funnel's hero form: Subscribe to campaign "Checklist delivery". Fire test: 1 controlled signup, double opt-in confirmed; the checklist email landed ~35 seconds after confirmation. Pass — the form-level campaign-subscription action fires under double opt-in where the form-level tag action did not. Test contact deleted; funnel live and delivering.

Cross-links: the automation-action failure this guide extends is documented in How to Set Up Email Automation in systeme.io (Tested End to End); the 1-tag limit is covered in How to Organize Your Email List with Tags in systeme.io (Tested End to End); double opt-in mechanics are isolated in How to Turn On Double Opt-In in systeme.io.

Trade-offs — the honest limitations

1. The tutorial pattern can't be built on the free plan. No wait step in rules, one rule total. This isn't a workaround situation. The pieces the pattern needs don't exist at this tier.

2. Per-form automation under double opt-in: tags are dead, campaign subscription works. I hoped the form-level rule would dodge the global-rule problem. A form-level "Add a tag" rule saved fine and then did nothing: 0 for 3 across five days of checks. But on Oct 18 I tested a form-level "Subscribe to campaign" rule on the live funnel's hero form — it fired, and the delivery email landed about 35 seconds after double opt-in confirmation. So the action matters: form-level tag actions stay silent under double opt-in; form-level campaign subscription delivers. (Caveat: the tag test ran on a test page, the campaign test on the live funnel's hero form — one controlled signup each pattern, not a large sample.) The funnel-level "form subscribed" trigger stays deaf either way.

3. I didn't test paid Workflows. Sequencing with waits lives there. Whether it delivers under double opt-in is untested by me. No verdict, no guess.

4. I didn't test at newsletter scale. Three controlled signups prove the mechanism fails. They don't measure anything about bulk sends.

5. The working alternative isn't a sequence. The thank-you-page redirect delivers your welcome content once, reliably. If you need timed emails days apart, that's the gap the free plan leaves open.

Fit check

Use the redirect pattern if: you're on the free plan, you run double opt-in, and you need new subscribers to actually receive your welcome content. One reliable delivery beats three that never send.

Upgrade or look elsewhere if: you need timed multi-email sequences running now. That needs features I couldn't test on the free plan, and I won't guess about whether the paid tier delivers under double opt-in. That's a test for another guide.

Next action

Affiliate disclosure: FigFroot earns a commission if you sign up through the link below, at no extra cost to you. It's how we fund the hands-on testing behind guides like this.

Set up the delivery that works: create your free systeme.io account, build the opt-in funnel from the landing page guide, and redirect the form to a thank-you page carrying your welcome content. Then confirm it yourself with a test signup before you trust it: Try systeme.io free

Plan details verified October 2026. Screenshots are original, taken in a real systeme.io account during testing.