How to Set Up Automation in Systeme.io (2026): A Beginner’s Step-by-Step Guide

Affiliate Disclosure: This article contains an affiliate link to systeme.io. We may earn a commission from a qualifying paid purchase at no extra cost to you.

By Creator Tool Bench · Official documentation and connected account settings checked October 14, 2026.

Featured photo: Kari Shea on Unsplash. This is an illustrative workspace photo, not a screenshot of systeme.io.

To set up a simple automation in Systeme.io, connect a form-submission trigger to the Subscribe to campaign action, choose your email campaign, and save the rule. Your campaign then controls which emails go out and when.

The useful part is knowing what belongs in the rule, what belongs in the campaign, and how to check the connection between them. A beautiful opt-in page and four finished emails can still leave subscribers waiting if nothing connects the two.

This guide focuses on that connection. For building the pages, use our sales funnel setup guide. For writing and activating the emails, use our email campaign guide. Here, we will choose the automation method, connect the right form, prevent duplicate delivery, and test the journey.

What we verified—and what comes from documentation

Creator Tool Bench’s previously verified journey is: signup → contact creation → Day 0 welcome email → working PDF link → nurture sequence. For this article, we read the current connected account configuration without changing the funnel, emails, rules, or customer records.

The active rule has one form-submission trigger and two actions: Send email and Subscribe to campaign. The campaign, “Creator Tool Bench – Free PDF Nurture,” contains four active follow-up emails. That confirms the configuration; it is not a new inbox-delivery test or a measurement of conversion performance.

The button-by-button instructions below follow current official Help Center guides. The browser session used for this review required login, so we did not independently operate the authenticated dashboard UI. Advanced Workflows features are documentation-based, not features we tested in production. Screenshots of the official interfaces are available in the linked Help Center articles.

Automation Rules vs Workflows: which should you use?

Our recommendation for a first lead magnet is one rule plus one campaign. In this article, “workflow” can mean the overall subscriber journey; the capitalized Workflows feature is the separate visual builder.

For example, a person asking for a checklist needs the checklist and useful follow-up. You do not need a branching canvas just to send that same sequence to each new subscriber. Start with a clear entry point and a single delivery route you can explain.

Systeme.io’s official Rules guide shows form subscription, purchase, and tag assignment as trigger examples. Its Workflows guide explains the visual builder and its branching options.

Can you do this on the Free plan?

The official pricing information lists a Free allowance of 1 automation rule, 1 workflow, and 1 email campaign, alongside 2,000 contacts, 3 sales funnels, and unlimited email sending. One campaign is a sequence container; it does not mean just one email.

These are capacity limits, not a promise that every business setup will fit. If your existing lead magnet already uses your rule or campaign allowance, check your account usage before planning another independent sequence. A saved but unused setup is also worth reviewing before you assume you have space.

We checked the official pricing page and its indexed comparison on October 14, 2026. The live comparison values did not render in our browser, although the page’s FAQ confirmed the rule and campaign limits; the indexed official comparison also listed one workflow. Recheck the account allowance before relying on that workflow limit. For wider plan choices, see Systeme.io Pricing Explained.

The smallest useful beginner automation

For a new setup, use this design:

1. A visitor submits the opt-in form.
2. The automation subscribes that contact to one campaign.
3. The first campaign email delivers the resource with no intentional wait.
4. The remaining campaign emails follow the schedule you choose.

Give the welcome email one owner. If it is the first campaign email, do not also send the same welcome from a separate rule action. If the rule sends the welcome, begin the campaign with the later follow-up.

CTB uses the second arrangement. Its rule sends “Your Free Creator Tools Checklist” separately and enrolls the subscriber in the nurture campaign. The four active campaign steps are configured as follows:

No send-at time or skipped weekdays are configured on those four steps. The nominal follow-up days are 1, 3, 5, and 8 if earlier messages send as scheduled. These are settings, not a guarantee of arrival in a recipient’s inbox.

Before you create the rule

Have the opt-in page and campaign ready. Name them so you can identify them in a dropdown: “Checklist opt-in” and “Checklist nurture” are easier to check than “Page 1” and “Campaign 1.” Keep a note of which email delivers the PDF.

Review the public signup page, the promised resource, the sender configuration, and the active campaign steps. If the PDF route is not ready, follow our PDF delivery walkthrough first. Automation cannot fix a download link that requires your own login.

Step by step: connect registration to a campaign

1. Open the Rules editor

Go to Automations → Rules → Create. The editor separates the trigger from the action. This path is documented in the official campaign automation guide.

2. Select the registration trigger

Click the plus button under Trigger. Choose Funnel step form subscribed, then select the opt-in page. Use the page that collects the email address.

Check the selected page against the actual URL you plan to share. A similarly named old page can make a rule look correct while new visitors are signing up elsewhere. Simply visiting a page is a different event from submitting its form.

3. Add Subscribe to campaign

Click the plus button under Action, choose Subscribe to campaign, and select your intended campaign.

Read the campaign name again before saving. The action connects the subscriber to the sequence; it does not author the messages or choose their individual delays.

4. Choose where the welcome email lives

For the minimum setup described above, keep the welcome in the campaign. To mirror CTB’s separate delivery route instead, use a Send email action for the resource and keep that same message out of the campaign.

Do not depend on the order of two rule actions to solve a timing problem. Make the campaign’s first wait intentional, then test what the subscriber actually receives.

5. Save and check the rule

Click Save rule. Reopen it to check the selected page and campaign, and confirm that the rule is active before testing.

You can also reach rules through a funnel step’s Automation Rules tab, as shown in the official automatic-email tutorial. Use one route while learning so you can find the setup again.

Set email timing in the campaign

Open Emails → Campaigns and your campaign. Save each email, then use its three-dot menu and Activate to configure sending. Choose its preceding email, delay, and any time or weekday restrictions. See the official campaign setup guide.

The delay for a later email is measured from the selected preceding email’s delivery time. Optional sending windows must also be satisfied. A one-day wait plus a weekday-only window can therefore produce a longer elapsed wait.

For a new lead magnet, our starting recommendation is no intentional wait on the resource email and no unnecessary weekday window. Put the useful follow-up later. If the welcome is outside the campaign, as at CTB, the first campaign message is already a follow-up.

Our campaign tutorial covers email creation in detail. Before editing an active sequence, consider contacts already progressing through it; a change to your plan is not automatically a replay for past subscribers.

When the visual Workflows builder becomes useful

Use it when the next step depends on a condition—for example, sending a different follow-up to someone who has bought an offer. Decide the behavior first; a larger canvas is not itself an improvement.

The current official workflow instructions, updated October 12, 2026, describe this setup:

1. Open Automations → Workflows → + Create, name the workflow, and save.
2. Open the canvas and click + Add a trigger. For a funnel signup, choose Funnel form subscribed, select the asset, and click Create.
3. Use the next plus icon to add an Action, Decision, or Delay. An Action can subscribe a contact to a campaign; a Decision creates Yes/No paths.
4. When ready, return to the list and use the three-dot menu’s Activate option. New workflows are inactive by default.

The documented triggers apply to new events after activation, not past events. This section is based on official documentation, not a CTB production test. Before adding it alongside a rule, map which setup owns each email so the same signup does not start duplicate delivery paths.

Test the whole journey, not just the email preview

Use a fresh test address you control and the public opt-in URL. Avoid adding unrelated existing subscribers to a sequence for testing.

1. Submit the form: verify the confirmation or thank-you page.
2. Find the contact: confirm the signup reached the account.
3. Check enrollment: confirm the intended campaign is attached and inspect available automation history.
4. Check the inbox: confirm the resource email arrives once, with the expected subject and sender.
5. Open the PDF: test as a reader without relying on an admin login. Read the file to confirm the version.
6. Check the follow-up: compare the next configured send with the expected schedule, then confirm actual receipt when that time arrives.

Record the test time, received messages, and failed step. Do not record “passed” for later emails merely because their settings look right. CTB’s earlier end-to-end result is the existing verified example; we did not submit another live signup during this read-only review.

A campaign email’s Save and test option can help inspect an individual message. However, the official testing guide says substitution variables do not populate in test sends, and emails created directly in rules or workflows cannot currently be tested that way. Test-email preview is therefore not proof that the trigger or enrollment worked.

If the automation does not work, locate the broken connection

Change one setting at a time and repeat the relevant test. If the timing is wrong, inspect the schedule before replacing the whole automation. If the form never creates the contact, rewriting the email is unlikely to help.

The Rules documentation also notes that tag-based triggers require a new tag assignment after setup, that repeated triggering by the same contact has a limit, and that task history is retained for only a month. Use a fresh address for a clean test and record evidence promptly; missing old history does not prove an event never happened.

Frequently asked questions

Do I need a Workflow to send a welcome sequence?

For the simple form-to-campaign setup here, a rule is enough. Consider the visual builder when a decision changes the path.

Does Subscribe to campaign send the PDF by itself?

It enrolls the contact. Put the download route in the email that owns delivery, then test that route. CTB uses a separate welcome action followed by its nurture campaign.

Why did the email arrive later than the delay I chose?

Check the preceding message and any time or day restrictions. Distinguish the configured sending time from actual inbox arrival.

Will my new automation automatically process old subscribers?

Do not assume that it will. The documented workflow behavior uses events after activation. Plan any handling of existing contacts separately and check permission before starting a new sequence.

Should I use Send email or Subscribe to campaign?

Decide whether the message is a single delivery email or part of a sequence. For a first setup, putting delivery and follow-up in one campaign gives you one place to review the emails. Keep two delivery routes only when you can explain their separate jobs.

Your next step

Connect one form to one sequence and prove that a subscriber receives the promised resource. Then review whether the later emails help them use it. More branches can wait until you have a reason for them.

Continue with our funnel guide, campaign guide, and PDF delivery guide as needed.

Start with systeme.io for free and check your account’s remaining capacity before building another automation. This is an affiliate link.