- Home
- Resources
- Integrations
- LifterLMS
LifterLMS Zapier integrationAutomate LifterLMS with Zapier.
LifterLMS Zapier integration: 9 triggers, 8 actions, 2 searches. LifterLMS runs online courses and memberships on WordPress. With Zapier, enrollments, new students and lost access can start Zaps, and other apps can enroll, cancel or expire a student's access.
Verified Trustpilot reviews · AI, automation & growth agency
What the LifterLMS Zapier integration handles for you
The LifterLMS Zapier integration connects your LifterLMS site to other apps through a Zap, the automation you build on Zapier. LifterLMS can start a Zap when a student signs up, enrolls or loses access, and it can take orders from other apps: create a WordPress user, enroll them, or cancel and expire their access.
Three results stand out. A follow-up that starts with the enrollment: New Course Enrollment watches a course and hands each new student to your email tool or your records. Access that follows what happens elsewhere: Enroll in a Course and Enroll in a Membership open the doors when another app says so, while Cancel Course Access and Expire Membership Access close them. And clean exits: Course Access Expired and Membership Access Cancelled tell the rest of your tools that someone has left, so nobody keeps writing to a student who is gone.
Now the limits. All nine triggers are polling ones, so nothing is instant, and several of them ask for the ID of the course or membership to watch. Most actions ask for WordPress IDs rather than names or emails, so a search step often has to come first, which makes the Zap multi-step and pushes it onto a paid plan. There is no step to edit or delete a course. If you would rather have someone set this up with you, our Zapier agency builds Zaps like these.
Zapier vocabulary in one minute
Eight terms come back on every screen of the editor. Here they are, one plain line each.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
- Trigger
- The event in an app that starts the Zap; once it is on, Zapier waits for it. LifterLMS has nine, such as New Student.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, such as Enroll in a Course.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
- Polling vs instant trigger
- Polling: Zapier asks the app for new items at a fixed interval. Instant: the app calls Zapier itself. Every LifterLMS trigger polls.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something that already exists, here a WordPress user, so the next steps can use what it found.
- Connection
- Your LifterLMS account linked to Zapier once, then reused by every step of every Zap that touches LifterLMS.
What LifterLMS Zaps really cost
Zapier bills tasks, meaning actions that complete. Your LifterLMS trigger never costs a task, and the checks Zapier runs on your site to spot new enrollments cost nothing either.
- Free plan100 tasks per month
- Zaps on the free planUnlimited, two steps each
- Premium appNo
- Search or filter in the ZapMulti-step, paid plan
A Zap that sends each new enrollment to your email tool costs one task per student. A three-action Zap costs three times that, since each successful action counts on its own. Failed actions are not billed. LifterLMS is not a premium app, so the free plan accepts it, but only for two-step Zaps. The moment you add a search to find the WordPress user, a filter or a second action, you have a multi-step Zap, and that needs a paid plan. With nine polling triggers, your plan also sets how long a new enrollment waits before the Zap sees it.
Connect LifterLMS to Zapier
- 01
Open the Apps page
In your Zapier account, go to the Apps page, which keeps every connection you have made. Click + Add connection. The connection you create here is reused by any Zap that works with LifterLMS.
- 02
Select LifterLMS
Search for LifterLMS in the dialog, pick it, then click Add connection. A new tab opens so you can sign in to your LifterLMS site; keep the Zapier tab open behind it.
- 03
Sign in and grant access
Log in to LifterLMS in that tab and allow Zapier in. You need an account on the site, plus access to any course, membership or student you do not own yourself but want the Zap to read or change.
Your first LifterLMS Zap: welcome new course students
GoalEvery new student in a chosen LifterLMS course who passes your condition is added as a contact in your email tool.
- 01
Build: start on New Course Enrollment
Create a Zap, pick LifterLMS as the trigger app and New Course Enrollment as the event. Choose your connection, then enter the Course ID of the course this Zap should watch.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent enrollments in that course, so pick a real one; its fields are what you will map in the next steps.
- 03
Add the filter
Click the plus icon and add Filter. Set the field to check, the rule and the value to compare with. Use a text rule for text and a number rule for numbers, or the filter never passes.
- 04
Add the email contact
Add your email tool as the action, on the event that adds a contact. Map the student's details from the trigger, then test the step and read what came back.
- 05
Publish
Publish the Zap to switch it on. Only enrollments made from now on go through. The filter makes this Zap multi-step, so it runs on a paid plan.
LifterLMS triggers
9 events start a Zap when something happens in LifterLMS. Zapier checks for them at the interval your plan allows.
Course Access Cancelled
Polling triggerIn Zapier“Triggers when a WordPress user's access to a course is cancelled.”
Starts the Zap when a WordPress user loses access to a course because it was cancelled. The student's details move on to the next step, so you can stop a reminder sequence, update a record or alert whoever looks after that course.
Course Access Expired
Polling triggerIn Zapier“Triggers when a WordPress user's access to a course expires.”
Fires when a student's access to a course expires. Where Course Access Cancelled reports a cancellation, this one reports an expiry, a natural moment to offer a renewal or ask for feedback through another app.
Membership Access Cancelled
Polling triggerIn Zapier“Triggers when a WordPress user's access to a membership is cancelled.”
Kicks off when a WordPress user's access to a membership is cancelled. Everything the trigger brings back can feed a cleanup elsewhere: remove the person from a members-only list, close a support thread or log the departure.
Membership Access Expired
Polling triggerIn Zapier“Triggers when a WordPress user's access to a membership expires.”
Runs when a WordPress user's access to a membership expires. It is the counterpart of Membership Access Cancelled, and a fitting signal for a win-back message or a renewal reminder sent from your email tool.
New Course
Polling triggerIn Zapier“Triggers when a new course is created.”
Goes off when a new course is created in LifterLMS. It needs no course ID, since it is the course itself that is new, and it hands the course details to the next step, ready to announce or to record in a catalogue kept elsewhere.
New Course Enrollment
Polling triggerIn Zapier“Triggers when a WordPress user enrolls in a given course.”
Triggers each time a WordPress user enrolls in the course you pick. It is the natural start for a welcome flow: the new student's details travel down the Zap to an email tool, a spreadsheet or a community app.
New Membership
Polling triggerIn Zapier“Triggers when a new membership is created.”
Starts when a membership is created on your LifterLMS site, not when someone joins one. It suits admin flows: telling the team a new offer is live, or adding the membership to a list of products you track elsewhere.
New Membership Enrollment
Polling triggerIn Zapier“Triggers when a WordPress user enrolls in a given membership.”
Picks up every WordPress user who joins a given membership. The member's details become available to the next steps, which can open access in another app, add them to a members list or greet them by email.
New Student
Polling triggerIn Zapier“Triggers when a new student is created.”
Reacts to every new student created on your LifterLMS site, whatever course or membership comes next. With no ID to set, it is the widest net of the nine triggers and the simplest one to start with.
LifterLMS actions
LifterLMS gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Cancel Course Access
ActionIn Zapier“Cancels a WordPress user's access to a course.”
Cancels a student's access to a course, identified by the user ID and the course's post ID.
Cancel Membership Access
ActionIn Zapier“Cancels a WordPress user's access to a membership.”
Removes a student's access to a membership, from their user ID and the membership's post ID.
Create a WordPress User
ActionIn Zapier“Create a WordPress user if none is found.”
Adds a user to your WordPress site, the account a student needs before any enrollment. Only the email address is required.
Enroll in a Course
ActionIn Zapier“Enrolls a WordPress user to a course.”
Puts a WordPress user into a course. You give the student's user ID and the course's post ID.
Enroll in a Membership
ActionIn Zapier“Enrolls a WordPress use to a membership.”
Adds a WordPress user to a membership, from their user ID and the membership's post ID.
Expire Course Access
ActionIn Zapier“Expires a WordPress user's access to a course.”
Marks a student's course access as expired instead of cancelled, using the same two IDs.
Expire Membership Access
ActionIn Zapier“Expires a WordPress user's access to a membership.”
Ends a student's membership access as an expiry, from the user ID and the membership's post ID.
Retrieve a WordPress User
ActionIn Zapier“Retrieve a WordPress user based on their ID.”
Fetches a WordPress user from its ID and passes the details on. It is a lookup dressed as an action: nothing changes on your site.
LifterLMS searches and their settings
2 search steps look for data that already exists in LifterLMS, so a later step can use it.
Most LifterLMS actions want a WordPress user ID, and the two searches are how a Zap gets one from an email or a username. Every Zapier search also carries three settings that decide what happens when it finds nothing, or more than one match.
Search WordPress User by Email
SearchFind or createIn Zapier“Search for a WordPress user based on their email.”
Looks up a WordPress user from an email address and returns them, user ID included, for the steps that follow.
Search WordPress User by Username
SearchIn Zapier“Search for a WordPress user based on their username.”
Finds a WordPress user by comparing your search term with all the usernames on your site.
The three settings every search exposes
- Successful if no search results are found?Left on its default, an empty search stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns the search into a find-or-create. It then drops the setting above and asks for what it needs to create the missing user.
- If multiple search results are found?Three ways out when several users match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When a LifterLMS Zap breaks
Zapier attaches no help article to LifterLMS and lists no limit specific to it. The failures to plan for are those every Zap shares, and LifterLMS makes two of them easy to hit.
LifterLMS has triggers and actions on the same courses and memberships, so loops are a real risk. Read the cases below before publishing. If a Zap still misbehaves, our Zapier troubleshooting page is where to begin.
The enrollment loop
New Course Enrollment followed by Enroll in a Course on the same course writes where the trigger watches. Each run sets off the next and drains your tasks.Students from before are skipped
A Zap only reacts to what happens after it is switched on. Existing students and enrollments are never sent; moving that backlog is a separate job.Bulk enrollments held back
Enroll a whole cohort at once, or import students after a migration, and the trigger suddenly returns a huge batch. Zapier's flood protection can hold it back.No double welcome
On a polling trigger, Zapier keeps track of what it has already seen, so the same enrollment does not start the Zap twice.
Need help automating LifterLMS with Zapier?
A person reads every message.



