LMS Integrations That Matter: HRIS, CRM, Webinars and SSO
Which LMS integrations are worth building and how to specify them: what data moves each way for HR systems, CRMs and webinar tools, SAML and OIDC for SSO, webhooks or scheduled sync, and failure handling.

Most LMS integrations are specified in one line ("connect it to the HR system") and then spend months being argued about, because nobody wrote down which data moves, in which direction, how often, and which system wins when the two disagree. The connection itself is rarely the hard part, and those decisions nearly always are.
This guide covers the four integrations that earn their cost on most learning platforms, what each should carry, and the engineering choices that stop them failing quietly.
Decide which system owns each piece of data
Before any API is opened, make a list of the fields involved and name one owner for each. The HR system owns who is employed, their department and their manager. The identity provider owns how they log in. The LMS owns enrollments, progress and certificates. The CRM owns the commercial relationship. A field has exactly one owner, and every other system holds a copy that it never edits.
It sounds bureaucratic and saves real trouble. When a manager corrects a job title inside the LMS and the nightly sync overwrites it, that is an ownership problem, and no amount of code fixes it.
Also choose the key that links a person across systems. Use an identifier that does not change, such as an employee or customer number. Email addresses change when people marry, move teams or switch from a personal to a company address, and every change produces a duplicate account.
What LMS integrations should carry in each direction
| System | Into the LMS | Out of the LMS |
|---|---|---|
| HRIS | People, department, role, manager, location, start date, leaver status | Completions, certificate expiry dates, overdue status |
| CRM or store | Purchases and deals that grant access, the buyer's company, seats bought | Enrolled, started, completed and certified, as a small set of fields or events |
| Webinar tool | Session join links, recordings | Registrations, and attendance returned to mark the session complete |
| Identity provider | Authenticated identity and a few profile attributes at login | Nothing |
HRIS
The HR feed is what makes assigned training possible. With department, role and location on each account, rules such as "all warehouse staff take manual handling" enroll people without anyone touching a list. The manager field drives team reports. The leaver flag is the one to get right: a leaver's account should be suspended on the day, with their training records kept, not deleted.
Going the other way, send HR the outcome and not the detail. A completion date and a certificate expiry date on the employee record are useful. A row for every lesson viewed is noise.
CRM
For a training business, the CRM or store decides who has paid, so it triggers enrollment. In return, sales and customer success want to see adoption: which customers have started, which have stalled, who is certified. Push a handful of status fields and milestone events. Resist syncing every quiz attempt, which fills the CRM's timeline and burns through API limits.
Webinars and virtual classrooms
The useful loop is registration out, attendance back. The LMS registers the learner for the session and shows the join link. Afterwards it pulls the attendance report and marks the session complete for those who met your rule, for example present for most of the scheduled time.
Identity is the usual failure. People join from a personal account or dial in by phone, and the attendance report cannot be matched to a learner. Require registered or authenticated joining for any session that counts toward a certificate. Before writing custom code, check whether the tool supports LTI, the standard for launching external tools from an LMS with the user's identity attached. Moodle also ships a BigBlueButton activity in core.
Single sign-on: SAML, OIDC and what neither does
SSO lets learners use the account they already have, and it lets IT enforce password and multi-factor rules in one place. Two protocols cover nearly every case. SAML 2.0 exchanges signed XML assertions and is the long-standing choice in enterprises and universities. OpenID Connect (OIDC) is built on OAuth 2.0 and passes identity as a signed token. Ask the customer's IT team which their identity provider prefers, and support that one.
In Moodle, OIDC providers are set up under Site administration > Server > OAuth 2 services (see the OAuth 2 services documentation), LDAP is a core authentication plugin, and SAML is added with an additional plugin. On WordPress, both protocols come from plugins.
Three points are missed again and again:
- SSO is login, not account management. Accounts can be created at first login from the attributes the provider sends, but nothing in SAML or OIDC tells the LMS that someone has left. That takes the HR feed or a provisioning protocol such as SCIM.
- Old passwords are a back door. If users who now sign in through SSO still have a working local password, the identity provider's rules are not being enforced. Disable local login for those accounts.
- Keep one way in for administrators. When the identity provider's certificate expires on a Sunday, someone needs a local admin login to fix the configuration.
Webhooks or scheduled sync
A webhook is a message one system sends another the moment something happens. A scheduled sync is a job that runs every few minutes or every night and compares the two sides.
Webhooks are fast, which matters when a customer has just paid and expects access now. They are also easy to lose. The receiving server may be down, the same message may arrive twice, and two messages may arrive in the wrong order. A receiver has to verify the signature on each message, answer quickly, and tolerate duplicates.
Scheduled sync is slower and far more forgiving. If last night's run failed, tonight's run corrects everything. It suits data that changes slowly, such as the HR feed.
The arrangement that holds up is both together: events for speed, and a nightly reconciliation that compares the full picture and repairs whatever the events missed. Our comparison of REST, GraphQL and webhooks goes further into the choice.
Plan for failure before the first request
Every integration fails sometimes. Whether anyone notices depends on decisions made at the start.
- Queue outgoing calls. Never call the CRM inside the page request in which the learner completes a course. Record the event, return the page, and let a background job deliver it. On WordPress a queue library such as Action Scheduler does this. In Moodle it is an ad hoc task.
- Retry with increasing delays, and stop after a set number of attempts.
- Make every operation repeatable. "Enroll user 4821 in course 17" run twice must leave one enrollment.
- Keep a visible failure list. Messages that ran out of retries go to a screen an administrator can read and replay, not to a log file nobody opens.
- Alert on age, not only on errors. "Oldest undelivered message is two hours old" catches a silent stall.
- Decide the business rule for downtime. If the store cannot reach the LMS, does the customer wait, or get access that is reconciled later? Choose on purpose.
We expand on these patterns in designing integrations that survive third-party API failures.
How the two common platforms connect
Moodle exposes its functions through web services. You enable them, turn on the REST protocol, create a custom service containing only the functions the integration needs (for example core_user_create_users and enrol_manual_enrol_users), and issue a token to a dedicated user with a restricted role. Outbound, a plugin observes events such as a course completion and queues the message.
WordPress LMS plugins sit on the WordPress REST API and its hooks. LearnDash, for example, fires learndash_course_completed, which a small plugin can use to queue an outbound call. Inbound enrollment usually arrives through the store or an authenticated REST endpoint.
On either platform, give each integration its own credentials with the narrowest permissions that work, so one can be revoked without breaking the others.
Buy the connector or build it
If a maintained connector exists for your exact pair of systems and carries the fields you listed, use it. Ready-made connectors suit simple, low-volume flows. Build when the mapping has rules of your own, when volumes are high, when records carry compliance weight, or when a failed sync would cost you a customer. A written data map with owners, directions and frequency is the right brief either way, and it is what we start from on eLearning platform projects, whether the work is Moodle integration or WordPress API integration.
Frequently asked questions
Which LMS integration should we build first?
Usually single sign-on together with the user feed, because every later integration depends on accounts being right. For a business that sells courses, the store or CRM link that grants access after payment comes first, since it touches revenue.
Is SAML or OIDC better for an LMS?
Neither is better in general. Both are secure when configured properly, and both are widely supported. Pick the one your organization's or your customers' identity provider already uses, and if you serve many client organizations, plan to support both.
How often should the HR system sync with the LMS?
Nightly is enough for most organizations, with one exception: leavers. If access to training content is sensitive, send suspensions as events or run that part of the sync more often. Starters can usually wait until the next morning.
Can a no-code automation tool handle LMS integrations?
For light flows, yes: adding a buyer to a mailing list or posting a completion to a chat channel. Be careful with anything that needs guaranteed delivery, ordering or an audit trail. Check how the tool retries failures and where you would see a message that never arrived.
Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.
