MailerLite Automations
How to Add a Subscriber to a MailerLite Group When a User Enrols on a LifterLMS Course
A MailerLite automation that starts when somebody joins a group can run a whole onboarding sequence. Zapify adds new students to that group with the A user is enrolled on a course trigger and the Add a subscriber to a group action. LifterLMS and MailerLite are both Zapify PRO integrations.
What this automation does
The automation is one trigger plus one action:
- Trigger: A user is enrolled on a course (
LIFTERLMS_COURSE_ENROLLED, LifterLMS) - Action: Add a subscriber to a group (
MAILERLITE_ADD_TO_GROUP, MailerLite)
When somebody is enrolled on the course, Zapify adds their email to the MailerLite group you choose. A MailerLite automation that triggers on that group does the rest.
Before you start
- LifterLMS installed and active, with at least one course.
- A MailerLite account (the current MailerLite, not MailerLite Classic).
- A MailerLite API key — create one in MailerLite under Integrations → API. MailerLite's own page for it is here.
- A group in MailerLite for new students, and optionally a MailerLite automation that starts when someone joins it.
PRO feature
MailerLite is a Zapify PRO integration and needs a Connection under Settings → Connections. The A user is enrolled on a course trigger needs Zapify PRO as well.
How to build the automation
Step 1: Connect MailerLite
- Go to Settings → Connections and click Add New.

- Choose MailerLite, paste in your API key, and name the connection something like Newsletter MailerLite.

- Click Test. Zapify asks MailerLite to accept the key and answers MailerLite accepted the credentials. If the key is wrong it says MailerLite refused the credentials. instead, so you find out before building anything.
- Save.
See Connections for how this screen works generally.
Step 2: Create a new automation
- In the WordPress admin, go to Zapify → Automations.
- Click Add New to open the builder.
- Name it clearly, such as Group new LifterLMS students in MailerLite.

Step 3: Add the "A user is enrolled on a course" trigger
- Click Add Trigger.

- Choose LifterLMS as the app.

- Select A user is enrolled on a course.

- In the Course field, pick the course, or leave it as any course.
Step 4: Add the "Add a subscriber to a group" action
- Click Add Action.

- Choose MailerLite as the app.

- Select Add a subscriber to a group.

Step 5: Configure the action
| Field | Required | What it does |
|---|---|---|
| Connection | Yes | The MailerLite connection from Step 1. |
| Email address | Yes | Insert the student's email with the { } token picker, using the user's email token. |
| Group | Yes | The group that starts your onboarding sequence in MailerLite. |
| Create if missing | No | On by default. |
Step 6: Set the steps Live and save
Each trigger and action has its own Live / Off / Draft switch. A new automation starts as a Draft and does nothing until its steps are Live.
- Set the trigger and every action to Live.
- Click Save.

Step 7: Test it
Enrol a test student. Check the group in MailerLite, or Zapify → Logs.
Tokens you can use
| Token | What it holds |
|---|---|
| Course ID | The numeric ID of the course. |
| Course title | The course's name. |
| Course URL | The permalink to the course. |
| User tokens, such as the user's email | The student the run is about. |
The action makes one token available to later actions: Subscriber ID.
Conclusion
With the A user is enrolled on a course trigger and the Add a subscriber to a group action, every new student starts your MailerLite onboarding without a manual step. For the end of the journey, see grouping learners when they complete a LearnDash course.
FAQs
Is this free in Zapify?
No. The A user is enrolled on a course trigger and the MailerLite actions both need an active Zapify PRO licence, and MailerLite needs a Connection.
What if the student unenrols later?
Nothing is removed automatically. Use Remove a subscriber from a group in a second automation if you want that.
Why is my new group or custom field not in the dropdown?
Zapify keeps the groups and fields it reads from MailerLite for a minute, so the builder does not call MailerLite on every dropdown. Wait a moment and reopen the field. If the dropdown stays empty, use Test on the connection, because an unreachable MailerLite gives an empty list.
Does this work with MailerLite Classic?
No. Zapify uses MailerLite's current API, and the older Classic API is not supported. Create the API key in the current MailerLite under Integrations → API.
Do I need to write any code?
No. The API key is the only thing you copy from outside Zapify.