Resources · Make integration

LearnWorlds Make integrationAutomate LearnWorlds with Make.

What happens in your school after a learner finishes a course, pays or cancels? The LearnWorlds Make integration gives you 27 modules, 15 of them instant triggers. This guide shows course creators how to link the account and build a first scenario step by step.

Try the LearnWorlds integration on MakeSee the 27 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the LearnWorlds Make integration automate?

The LearnWorlds Make integration lets your online school react on its own. LearnWorlds tells Make when a learner buys, completes a course or cancels a subscription, and Make then runs a scenario (the automation you build: a chain of modules) that tags, enrolls, updates or suspends that user for you.

A learning path that moves by itself. Watch Course Completed fires when someone finishes a course, and Enroll the User to a Product opens the next one. The learner never waits for a manual unlock.

Cleaner access when money stops. Watch Subscription Cancelled can feed Suspend a User or Unenroll the User from a Product, so a cancelled plan does not leave content open. Unsuspend a User brings the person back if they return.

Segments your marketing tools can use. Watch Lead Created catches each captured email, and Add a Tag to the User labels buyers, trial users or finishers. Tags then drive Watch Tag Added in other scenarios. The same pattern works with a CRM, and the Agile CRM Make integration shows the other side.

One limit to know: Make's own documentation for LearnWorlds is marked as limited, because little public information exists about the app. Expect to learn the data by testing, and keep Make troubleshooting handy for the first runs. If you are weighing tools, LearnWorlds may also appear in n8n; the n8n vs Make comparison sets out the criteria.

Connect

How do you connect LearnWorlds to Make?

  1. 01

    Add a LearnWorlds module

    In a scenario, click the + and search for LearnWorlds, then pick any module, such as Watch Course Completed. Click Create a connection. A connection is your LearnWorlds account linked to Make once and reused by every LearnWorlds module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you run more than one school, so you can tell them apart later. Then follow the window Make opens: either approve access on the LearnWorlds page, or paste the key that LearnWorlds gives you.

  3. 03

    Save and check the module

    Click Save. The module now shows your connection, and Make can list the LearnWorlds objects it reads through it. Every other LearnWorlds module in any scenario can pick this same connection from its dropdown.

First scenario

Your first scenario: enroll finishers in the next course

GoalWhen a learner completes a course in LearnWorlds, Make enrolls them in the follow-up product.

  1. 01

    Create the scenario

    Open the Scenarios page and create a new scenario. The empty editor shows one big +, which is where the first module goes. A module is one brick of the scenario: a trigger, an action or a search.

  2. 02

    Add Watch Course Completed

    Click the +, search for LearnWorlds and choose Watch Course Completed. Pick the connection you created. This trigger is instant, so LearnWorlds calls Make through a webhook as soon as a learner finishes.

  3. 03

    Add Enroll the User to a Product

    Click the + on the right of the trigger and add Enroll the User to a Product. Map the user from the trigger's output, then tell the module which course, bundle or manual subscription opens next.

  4. 04

    Test with Run once

    Click Run once, then have a test learner complete the course. Open the bubbles above each module to read the bundles, the items passed from one module to the next, and check the enrollment landed.

  5. 05

    Switch the scenario on

    Save and turn the scenario on. From now on each completion runs it, and every module execution counts as one operation on your Make plan. A Free plan allows 2 active scenarios.

Triggers

What can start a LearnWorlds scenario?

15 modules start a scenario when something happens in LearnWorlds. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by LearnWorlds as soon as it happens.

LearnWorlds1Watch Certificate Created

Watch Certificate Created

Instant trigger

In Make“Triggers when a user is awarded a certificate.”

Each time LearnWorlds awards a certificate, this trigger hands the learner and the certificate event to your scenario. It is the natural moment to congratulate someone or record a qualification elsewhere.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the certificate is awarded.
When to use it
you issue certificates for compliance or professional training and a manager or HR sheet must know who earned one.
Watch out
a certificate and a course completion can arrive close together, so pick one of the two triggers per scenario to avoid duplicate messages.
LearnWorlds2Watch Course Completed

Watch Course Completed

Instant trigger

In Make“Triggers when the course is completed by the user.”

Finishing a course becomes a signal Make can act on. The scenario starts with the learner and the course they just completed, ready to map into the next module.

How it fires
instant, LearnWorlds calls Make through a webhook the moment the course is completed.
When to use it
you sell a sequence of courses and want finishers enrolled in the next one with Enroll the User to a Product, or tagged as graduates.
Watch out
test with a real completion during Run once, because Make's LearnWorlds documentation is limited and the bundle is the best guide to what arrives.
LearnWorlds3Watch Enrollment Purchase Created

Watch Enrollment Purchase Created

Instant trigger

In Make“Triggers when a purchase occurs.”

You learn about every purchase that enrolls someone, without opening the LearnWorlds admin. The scenario receives the buyer and the purchase so it can welcome, tag or record the sale.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the purchase occurs.
When to use it
a new buyer should land in your email tool or get a buyer tag with Add a Tag to the User.
Watch out
this watches purchases, not payments in general; subscription renewals have their own trigger, Watch Subscription Started.
LearnWorlds4Watch Lead Created

Watch Lead Created

Instant trigger

In Make“Triggers when an email is captured.”

Every email address your school captures reaches Make here, before the person has bought anything. That gives you a head start on nurturing a prospect.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the email is captured.
When to use it
a lead form or free signup on your LearnWorlds site should push the contact into a newsletter or CRM list.
Watch out
a lead is not yet a user with enrollments, so actions such as Enroll the User to a Product may have no account to act on at this stage.
LearnWorlds5Watch Payment Created

Watch Payment Created

Instant trigger

In Make“Triggers when a payment is created.”

Whenever LearnWorlds records a payment, your scenario gets it straight away. Finance and reporting workflows usually start from this trigger rather than from enrollments.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the payment is created.
When to use it
every payment should add a row to an accounting spreadsheet or notify the person who handles invoices.
Watch out
a single sale can also fire Watch Enrollment Purchase Created, so decide which trigger owns the finance log to avoid counting it twice.
LearnWorlds6Watch Previews

Watch Previews

Instant trigger

In Make“Triggers when a free section is previewed.”

Here Make hears about visitors who open a free section of a course. That preview is a strong buying signal, and this trigger turns it into a follow-up.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the free section is previewed.
When to use it
someone sampled the first lesson and your sales team or email tool should follow up while the interest is fresh.
Watch out
previews can be frequent on a popular course, and each run spends operations, so add a filter before any costly module.
LearnWorlds7Watch Subscription Cancelled

Watch Subscription Cancelled

Instant trigger

In Make“Triggers when a subscription is cancelled.”

A cancelled subscription reaches your scenario the moment it happens, so access and follow-up stay in step with billing. No one has to check a list of churned members by hand.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the subscription is cancelled.
When to use it
pair it with Unenroll the User from a Product or a win-back email to the person who left.
Watch out
removing access is a business decision; check your terms before pairing this trigger with Suspend a User.
LearnWorlds8Watch Subscription Started

Watch Subscription Started

Instant trigger

In Make“Triggers when a payment for a subscription is received.”

This trigger tells Make that a subscription payment has come in. It suits membership schools where access follows the billing cycle.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the subscription payment is received.
When to use it
a new or renewed member should get a tag, a welcome sequence or a line in a members spreadsheet.
Watch out
since it listens to payments, a renewal can fire it again for the same member, so a welcome email may need a filter.
LearnWorlds9Watch Subscription Trial Ended

Watch Subscription Trial Ended

Instant trigger

In Make“Triggers when a subscription trial ends in three days.”

Despite its name, this trigger gives you a warning ahead of time: it fires when a subscription trial ends in three days. That leaves room to convince the trial user before billing starts.

How it fires
instant, LearnWorlds calls Make through a webhook when the trial is three days from its end.
When to use it
send a reminder, a feature tour or an offer to trial users who have not decided yet.
Watch out
do not treat this event as the actual end of the trial when you change access.
LearnWorlds10Watch Subscription Trial Started

Watch Subscription Trial Started

Instant trigger

In Make“Triggers when a subscription trial is started.”

The first day of a trial is when onboarding matters most, and this trigger lets Make start it. The scenario receives the new trial as soon as it begins.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the trial starts.
When to use it
tag trial users with Add a Tag to the User so your email tool can send a dedicated onboarding track.
Watch out
pair it with Watch Subscription Trial Ended in a separate scenario rather than stacking both logics in one.
LearnWorlds11Watch Subscription Updated

Watch Subscription Updated

Instant trigger

In Make“Triggers when a subscription is updated.”

Plan changes and other edits to a subscription reach Make through this trigger. It keeps your other tools aligned with what the member actually pays for.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the subscription is updated.
When to use it
a member upgrades or changes plan, and your CRM or members sheet must show the new status.
Watch out
the documentation does not list which changes count as an update, so check a few real bundles after Run once before building filters.
LearnWorlds12Watch Tag Added

Watch Tag Added

Instant trigger

In Make“Triggers when a tag is added to a user.”

Tags become switches you control from LearnWorlds. As soon as a user gets a tag, by hand or by automation, your scenario starts with that user.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the tag is added.
When to use it
a tag such as VIP or partner should trigger an enrollment, a Slack alert or a CRM update.
Watch out
never end this scenario with Add a Tag to the User on the same person without a filter, or each new tag can start the scenario again.
LearnWorlds13Watch Tag Removed

Watch Tag Removed

Instant trigger

In Make“Triggers when a tag is removed from a user.”

Removing a tag can mean something too, and this trigger lets Make react to it. The scenario receives the user whose tag was taken away.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the tag is removed.
When to use it
dropping a partner tag should withdraw access with Unenroll the User from a Product or update a list elsewhere.
Watch out
a removal made by Remove a Tag from the User in another scenario will likely fire it too, so test that case with Run once.
LearnWorlds14Watch User Created/Updated

Watch User Created/Updated

Instant trigger

In Make“Triggers, when a new user has been created, or an existing one was updated.”

New signups and profile edits both land here, which makes it the trigger for keeping a contact list in sync with your school. One module covers both events.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as a user is created or updated.
When to use it
your CRM or mailing list must mirror every LearnWorlds user and every change to their profile.
Watch out
ending the scenario with Update a User on the same person may fire the trigger again, so filter or avoid that pairing.
LearnWorlds15Watch User Unenrolled

Watch User Unenrolled

Instant trigger

In Make“Triggers when a user is unenrolled from the product.”

When someone loses access to a product, Make hears about it and can close the loop in your other tools. No one has to report the departure by hand.

How it fires
instant, LearnWorlds calls Make through a webhook as soon as the user is unenrolled.
When to use it
remove the person from a course community, a mailing segment or a coaching calendar once they leave the product.
Watch out
an unenroll made by another scenario with Unenroll the User from a Product will likely fire it too, so check for loops.
Modules

What can Make do in LearnWorlds?

LearnWorlds gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

LearnWorlds1

Add a Tag to the User

Action

In Make“Adds an array of tags to the user.”

Label a learner with one or several tags in a single step, so segments build themselves as people buy, finish or sign up.

When to use it
after a purchase or a completion, to mark buyers or graduates for your marketing tools.
Watch out
a scenario that starts on Watch Tag Added and ends here can run in circles without a filter.
LearnWorlds2

Create a User

Action

In Make“Creates a new user.”

Open a LearnWorlds account for someone who came from another tool, such as a form, a shop or a CRM, without typing it in the admin.

When to use it
a customer paid outside LearnWorlds and needs an account before you enroll them.
Watch out
check first with List Users that the person does not already exist, to avoid duplicate accounts.
LearnWorlds3

Enroll the User to a Product

Action

In Make“Enrolls the user to the product, regarding the course, bundle, manual subscription.”

Give a user access to a course, a LearnWorlds bundle of courses or a manual subscription straight from the scenario.

When to use it
a payment in another system or a completed course should unlock the next product automatically.
Watch out
a LearnWorlds bundle is a product package, not the Make bundle that carries data between modules.
LearnWorlds4

Get a User

Action

In Make“Returns the user specified by the provided user ID.”

Fetch the full profile of one learner when you already know their user ID, so later modules can use details the trigger did not include.

When to use it
a trigger hands you only an ID and the next step needs the name or email.
Watch out
it needs the exact ID; when you only have other details, List Users is the module to search with.
LearnWorlds5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any part of the LearnWorlds API that the listed modules leave out, with the same connection you already set up.

When to use it
you need an operation none of the 27 modules offers, such as data outside users, tags and enrollments.
Watch out
you write the request yourself, and Make's LearnWorlds documentation is limited, so test each call with Run once.
LearnWorlds6

Remove a Tag from the User

Action

In Make“Removes an array of tags from a user.”

Take one or several tags off a learner so they leave a segment the moment their situation changes.

When to use it
a trial user converts and should lose the trial tag, or a cancelled member leaves the active group.
Watch out
expect this removal to fire Watch Tag Removed in any scenario listening for it, which may start more automations than planned.
LearnWorlds7

Suspend a User

Action

In Make“Suspends a user from loging in or creating another account.”

Block a learner from logging in or opening another account, without deleting anything from your school.

When to use it
a refund, a chargeback or an abuse report means access must stop right away.
Watch out
a suspended person cannot sign in at all, so keep Unsuspend a User ready in case of a mistake.
LearnWorlds8

Unenroll the User from a Product

Action

In Make“Unenrolls the user from a product specified by the provided product ID.”

Withdraw access to one product while the account itself stays active, which is gentler than a suspension.

When to use it
a subscription is cancelled or a cohort closes and the learner should keep their other courses.
Watch out
it targets one product by its ID, and it will likely fire Watch User Unenrolled wherever that trigger listens.
LearnWorlds9

Unsuspend a User

Action

In Make“Unsuspends a user.”

Restore sign-in for a learner you suspended earlier, so they get back into the school with their history intact.

When to use it
a payment issue is resolved or a support ticket is closed in favor of the learner.
Watch out
it only lifts a suspension; product access removed by an unenroll needs Enroll the User to a Product.
LearnWorlds10

Update a User

Action

In Make“Updates an existing user.”

Change an existing learner's profile from data held in another tool, so both sides tell the same story.

When to use it
your CRM is the reference for contact details and LearnWorlds should follow each change.
Watch out
an update can fire Watch User Created/Updated, so a scenario that starts there and ends here needs a filter.
LearnWorlds11

List Courses

Search

In Make“Lists all existing courses.”

Pull the catalog of courses that exist in your school, one bundle per course, ready to copy or report on.

When to use it
a spreadsheet or website section should show your current course list.
Watch out
each course passes through the following modules separately, and each of those executions counts as an operation.
LearnWorlds12

List Users

Search

In Make“Lists all existing users.”

Return the users of your school as separate bundles, which lets a scenario loop through people for exports or checks.

When to use it
you want to check whether someone exists before Create a User, or export the whole audience once.
Watch out
a large school sends many bundles, and every one runs the next modules, so watch your operations.
Need help

Need help automating LearnWorlds with Make?

A person reads every message.

FAQ

LearnWorlds and Make: common questions

01Is the LearnWorlds Make integration free?
Yes, on the Make side. LearnWorlds is a standard app, so its 27 modules are available on the Free plan. That plan has limits: 2 active scenarios, 15 minutes at least between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift those limits and count usage in credits per month. Your LearnWorlds subscription is separate and is not covered here.
02What do you need to connect LearnWorlds to Make?
A LearnWorlds account and a Make account are enough to start; Make's documentation lists no other prerequisite. Add any LearnWorlds module, click Create a connection, name it if you like, then either approve Make on the LearnWorlds page or paste the key LearnWorlds provides, and click Save. The connection is reused by every LearnWorlds module, so you only do this once per school. If the window asks for a key rather than a login, paste it exactly as LearnWorlds gives it, with no extra spaces.
03Do LearnWorlds triggers in Make fire in real time?
Yes. All 15 LearnWorlds triggers are instant: LearnWorlds calls Make through a webhook as soon as the event happens, whether a payment, a completed course or a new tag. There is no schedule to wait for, unlike a scheduled trigger that Make checks every 15 minutes by default. The one nuance is Watch Subscription Trial Ended, which fires three days before the trial actually ends. For a first test, Watch Course Completed or Watch Payment Created are easy events to reproduce with a test learner while Run once is waiting.
04What if a LearnWorlds module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the LearnWorlds API with the connection you already have, so you are not limited to the 27 listed modules. Keep in mind that Make marks its LearnWorlds documentation as limited because little public information is available, so plan to test each request with Run once and read the returned bundles before relying on it. Every call still counts as an operation on your plan, just like any listed module, so group requests when a single call can return what you need.
05Should you use Make or n8n for LearnWorlds?
It depends on the tool your team already works in. On Make, LearnWorlds brings 27 ready modules, including 15 instant triggers, plus Make an API Call for the rest. n8n may also offer a LearnWorlds node, so check what it covers before choosing. Compare the modules you actually need, the way each tool counts usage, and who will maintain the scenarios, rather than picking on reputation. If your team already runs other automations in Make, keeping LearnWorlds there saves learning a second tool.
Same platform

Other docs you might need on this stack.

Browse all integrations