About LMS Integrations
A reference archive of Learning Management Systems and how they integrate: native direct (OAuth) integrations, middleware support (Zapier, Make, Pabbly, n8n), REST/GraphQL APIs with documented endpoints, and webhook events with their security models.
What we track for each LMS
- Direct integrations
- Native integrations you connect from inside the LMS — usually an OAuth "Connect" flow to an app like Zoom, Salesforce, or a payment processor, with no middleware in between.
- Middleware
- Support for third-party automation platforms (iPaaS) such as Zapier, Make, Pabbly Connect, and n8n, which connect the LMS to thousands of other apps without code.
- API
- Public programmatic access (REST, GraphQL, etc.), documented in a docs-style layout: authentication, base URL, and a breakdown of endpoints by resource.
- Webhooks
- Outbound HTTP callbacks the LMS can send when events happen, including the list of supported event types and the security model (signatures, secret tokens, etc.).
Methodology & accuracy
Records are compiled from public vendor documentation and API references. Each LMS shows a last verified date and links to its sources. APIs and webhook events change over time — treat this archive as a fast orientation, and always confirm specifics against the vendor's official, current documentation before building an integration.