Resources · Make integration

TalentLMS Make integrationAutomate TalentLMS with Make.

What if new TalentLMS learners landed in the right course on their own? The TalentLMS Make integration gives you 18 modules (5 triggers, 11 actions, 2 searches) to link your LMS with your other tools. Written for training and ops teams, this guide walks you from the connection to a first working scenario.

Try the TalentLMS integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TalentLMS Make integration automate?

The TalentLMS Make integration links your TalentLMS account to Make, a visual tool where you build a scenario: a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick of that chain, and here the bricks watch, create, update or look up users, courses, groups and branches, so the admin work between your LMS and your other apps happens without code.

Onboarding with no manual enrollment. Watch Users spots each user created in TalentLMS, and Enroll a User to a Course signs that person up for the course you picked. HR keeps adding people as usual, and the course assignment follows without an admin clicking through the LMS.

A catalog your other tools can read. List Courses returns every course as a separate bundle, one item per course passed to the next module, ready to land in a table like the ones described on the Airtable Make integration page. Watch Courses then reports each course added afterward.

A tidy structure for partners and clients. When a new branch or group appears, Watch Branches or Watch Groups picks it up, and Add a User to a Branch or Add a User to a Group puts the right people inside.

What Make does not do here: none of the 5 triggers is instant. They are all scheduled, so Make checks TalentLMS on the scenario's schedule, every 15 minutes by default. When the listed modules stop short, Make an API Call reaches the rest of the TalentLMS API with the same connection.

Weighing another automation tool? The n8n vs Make comparison sets out the criteria, and the Make training covers the editor from the very first module.

Connect

How do you connect TalentLMS to Make?

  1. 01

    Copy your TalentLMS API key

    In TalentLMS, open Account & Settings, then Basic Settings, then the Security section, where the API key is displayed on screen. Copy it. Make needs an active TalentLMS account and this key to talk to your portal.

  2. 02

    Add a TalentLMS module and create the connection

    In a Make scenario, add any TalentLMS module and click Create a connection. A connection is your TalentLMS account linked to Make once; every TalentLMS module in your scenarios reuses it afterward.

  3. 03

    Name it and paste the key

    Type something you will recognize in the optional Connection name field, such as the name of your portal. Then paste the credentials you copied, or follow the instructions Make shows on screen, and save.

First scenario

Your first scenario: enroll each new user in a course

GoalWhen a user is created in TalentLMS, Make enrolls that person in the course you choose.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. The editor opens empty, waiting for the module that will start everything.

  2. 02

    Add Watch Users

    Search for TalentLMS, pick Watch Users, then click Create a connection or select the one you already made. This trigger starts the scenario whenever it finds a newly created user.

  3. 03

    Add Enroll a User to a Course

    Click the + on the right of Watch Users and add Enroll a User to a Course. Map the user coming from Watch Users, then pick the course: Make lists the courses it can read once the connection exists.

  4. 04

    Test with Run once

    Create a test user in TalentLMS, then click Run once. Each module shows the bundles it received, so you can read the new user on one side and the enrollment on the other before trusting the flow.

  5. 05

    Schedule and switch it on

    Open the clock on Watch Users to set the Scheduling: every 15 minutes by default, down to 1 minute on paid plans. Switch the scenario on, and new users get enrolled with nobody touching it.

Triggers

What can start a TalentLMS scenario?

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

TalentLMS1Watch Branches

Watch Branches

Scheduled trigger

In Make“Triggers when a new branch is created.”

Watch Branches tells your scenario that a new branch now exists in TalentLMS and passes that branch along as a bundle for the next module. It is the entry point when opening a branch should set off work somewhere else.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so the branch shows up at the next check rather than at once.
When to use it
a partner network opens a branch and the regional manager should hear about it in a team channel or a tracking table.
Watch out
it reacts to branches being created, not to people joining them; to place users, pair it with Add a User to a Branch.
TalentLMS2Watch Categories

Watch Categories

Scheduled trigger

In Make“Triggers when a new category is created.”

Every course category created in TalentLMS can reach your scenario through Watch Categories, which hands over the new category so the rest of the flow can reuse its name and details.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a category created between two checks arrives with the next run.
When to use it
the content team adds a category for a new product line, and the public catalog sheet or the internal wiki should gain the matching entry.
Watch out
this trigger only sees categories. A course filed under a category that already existed will not start it; Watch Courses covers that case.
TalentLMS3Watch Courses

Watch Courses

Scheduled trigger

In Make“Triggers when a new course is created.”

A course freshly added to TalentLMS becomes a starting signal with Watch Courses: the scenario receives that course as a bundle and can announce it, log it or copy it wherever your team works.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, or down to 1 minute on a paid plan.
When to use it
you want learners or managers told about a new course by email or in a chat channel without anyone writing the message by hand.
Watch out
the official description covers course creation only, so edits made later to an existing course fall outside what this trigger watches.
TalentLMS4Watch Groups

Watch Groups

Scheduled trigger

In Make“Triggers when a new group is created.”

Watch Groups hands your scenario each group created in TalentLMS, which lets a new cohort, client team or department trigger the setup around it in your other apps.

How it fires
scheduled. Make checks the app on the scenario's schedule instead of waiting for TalentLMS to call, so the group arrives at the next check.
When to use it
a trainer sets up a group for a client cohort and the account manager needs a matching record in the CRM.
Watch out
a group that just appeared may still be empty. To fill it from the scenario, add Add a User to a Group further down the chain.
TalentLMS5Watch Users

Watch Users

Scheduled trigger

In Make“Triggers when a new user is created.”

With Watch Users, every account created in TalentLMS can kick off a scenario, carrying that user as a bundle to the modules that follow. It is the most common starting point for onboarding flows.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, which is also the shortest gap on the Free plan.
When to use it
welcome new learners, enroll them in a starter course or copy their profile into an HR table as soon as the next check runs.
Watch out
because the trigger is scheduled, a welcome message lands after the next check, not the second the account is created.
Modules

What can Make do in TalentLMS?

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

TalentLMS1

Add a User to a Branch

Action

In Make“Adds an existing user to a branch.”

Add a User to a Branch places someone who already has a TalentLMS account into one of your branches, which keeps your learners sorted by client, region or partner without manual moves.

When to use it
right after Create a User, when each new account belongs to a specific partner branch.
Watch out
the module adds, it does not create. Run Create a User or Get a User upstream so the person exists.
TalentLMS2

Add a User to a Group

Action

In Make“Adds an existing user to a group.”

Group membership is what Add a User to a Group handles: an existing user joins the group you pick, which is how a cohort ends up gathered in one place for its trainers.

When to use it
a training deal closes in your CRM and the client's staff should land in their dedicated group.
Watch out
like the branch module, it expects a user who is already there; a brand new person needs Create a User first.
TalentLMS3

Create a Course

Action

In Make“Creates a new course.”

Create a Course adds a new course to your TalentLMS catalog straight from a scenario, which saves copying the same outline by hand from a planning sheet into the LMS.

When to use it
a row approved in a planning base should turn into a course the instructor can start filling.
Watch out
every run that reaches this module creates one more course, so make sure the same row cannot pass twice or you get duplicates.
TalentLMS4

Create a User

Action

In Make“Creates a new user.”

Create a User opens a TalentLMS account for someone new, the step that turns a signup, a hire or a purchase recorded in another app into a learner.

When to use it
a form or a won deal marks a new trainee, and the account should exist before anyone thinks of setting it up.
Watch out
if that person might already have an account, run Get a User or List Users before this module to avoid a second one.
TalentLMS5

Delete a Course

Action

In Make“Deletes an existing course.”

Delete a Course removes a course from TalentLMS for good, which keeps the catalog free of retired material that learners should no longer find.

When to use it
a course is marked as withdrawn in your planning tool and should disappear from the LMS too.
Watch out
a deletion cannot be taken back from Make. Test it with Run once on a throwaway course before you connect real data.
TalentLMS6

Delete a User

Action

In Make“Deletes an existing user.”

Removing an account when someone leaves is the job of Delete a User: the person disappears from TalentLMS, so former staff or contractors no longer keep a login to your training portal.

When to use it
an offboarding step in your HR tool or a contract ending in the CRM.
Watch out
Make has no module to restore a deleted account, so confirm with Get a User that the scenario targets the right account.
TalentLMS7

Enroll a User to a Course

Action

In Make“Enrolls an existing user to a course.”

Enroll a User to a Course signs an existing user up for a course, so the learner has it assigned without an admin clicking through TalentLMS.

When to use it
right after Watch Users or Create a User, for onboarding or compliance training that everyone must follow.
Watch out
the user and the course must both exist already. The module links them together, it creates neither of the two.
TalentLMS8

Get a Course

Action

In Make“Retrieves an existing course.”

Get a Course fetches the record of one course you already know, so later modules can reuse its data without anyone retyping it.

When to use it
the scenario holds a course reference from an earlier step and needs the rest of that course for a report or an email.
Watch out
it returns a single course. To go through the whole catalog, List Courses is the module to add instead.
TalentLMS9

Get a User

Action

In Make“Retrieves an existing user.”

Need the full record of one learner? Get a User retrieves an existing TalentLMS user and hands the profile to the next modules in the chain.

When to use it
before updating or deleting someone, to confirm the scenario is looking at the right account.
Watch out
one user comes out, never a list. When you need everyone at once, reach for List Users.
TalentLMS10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the TalentLMS API from your scenario, using the same connection as the other modules, so you are never stuck with only the listed actions.

When to use it
the ready modules stop short, for instance an operation on groups or categories that no action covers.
Watch out
you build the request yourself, so keep the TalentLMS API documentation open next to the module.
TalentLMS11

Update a User

Action

In Make“Updates an existing user.”

Update a User changes the profile of someone already in TalentLMS, which keeps the LMS in step with the HR tool or CRM where the real change happened.

When to use it
another app records a change for a person and the learner account should match it.
Watch out
the module edits an existing account only. If the person may be missing, check with Get a User first and branch from there.
TalentLMS12

List Courses

Search

In Make“Retrieves all existing courses.”

List Courses returns every course in your TalentLMS account, one bundle per course, which is the simplest way to copy the full catalog into another tool.

When to use it
to feed a catalog table, a web page or a report with all current courses.
Watch out
every module placed after it runs once per course, and each of those runs counts as an operation, one execution Make bills on your plan.
TalentLMS13

List Users

Search

In Make“Retrieves all existing users.”

List Users pulls all existing TalentLMS users into the scenario as separate bundles, one person each, ready to be sorted, copied or checked.

When to use it
to sync the whole learner base into a spreadsheet, or to see who already has an account before Create a User.
Watch out
on a large portal the list gets long, and each following module runs once per user, so a single run consumes more operations.
Need help

Need help automating TalentLMS with Make?

A person reads every message.

FAQ

Questions about TalentLMS and Make

01Is the TalentLMS Make integration free?
Yes on the Make side: TalentLMS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes 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 and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. On the TalentLMS side, you need an active account; the TalentLMS pricing page lists its subscriptions.
02What do you need to connect TalentLMS to Make?
An active TalentLMS account and its API key. The key sits in TalentLMS under Account & Settings, then Basic Settings, then Security, where it is displayed on screen. In Make, add any TalentLMS module, click Create a connection, optionally give the connection a name, and paste the key. That single connection then serves all 18 modules, triggers and actions alike, in every scenario you build, so you only go through these steps once per TalentLMS account.
03Do the TalentLMS triggers in Make react in real time?
No. All 5 TalentLMS triggers are scheduled, and none is instant. Make does not wait for TalentLMS to call it; it checks the account on the scenario's schedule. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan, while paid plans go down to 1 minute. A user created in TalentLMS therefore reaches Watch Users at the next check, not the second it appears. For a welcome email that gap rarely matters; when it does, a paid plan with a shorter interval is the lever.
04What if a TalentLMS module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the TalentLMS API from the scenario, with the connection already in place, so there is no second setup. That covers what the 11 actions and 2 searches leave out, such as more operations on groups or categories. The trade-off is a bit more work: you write the request yourself from the TalentLMS API documentation. Test it with Run once and read the bundle it returns before plugging it into the rest of the scenario.
05Should you use Make or n8n for TalentLMS?
It depends on the tool your team already runs and will keep maintaining. On Make, TalentLMS comes as a standard app with 18 ready modules, available from the Free plan, plus Make an API Call for anything else. n8n is another automation platform, and many apps have a node there as well; check whether TalentLMS does before choosing. The n8n vs Make comparison on this site sets the criteria side by side. In the end, the right pick is the editor your team is comfortable working in.
Same platform

Other docs you might need on this stack.

Browse all integrations