Grow LMS API Documentation
Grow by Plenum — Integrations & Notifications
A quick-reference map of what Grow connects to, and how.
This document answers the “does it integrate with X?” and “can it notify people via Y?” questions directly — with the actual catalog of built-in connectors, the open standards your own systems use, and an honest read on the boundaries. Where a capability isn’t out-of-the-box, we say so plainly and describe the supported path.
Throughout, <SCHOOL_ID> is your dedicated Grow environment. Named integrations should be confirmed against your environment during onboarding, since native catalogs evolve.
1. The three ways Grow connects
- Native — built-in, officially supported connectors (50+), configured once. Catalogued in Section 2.
- Open standards — Grow speaks SSO (SAML/OIDC), content embedding (LTI 1.3), and its own authenticated API + webhooks. This is how your systems connect, no pre-built connector required (Section 3).
- Automation layer — anything without a native connector is reachable through automation platforms (Zapier and 3,000+ apps, plus Make, Integrately, Pabbly Connect), driven by Grow’s real-time events (Section 4).
Note for a Google-first organization. Grow’s native catalog is especially deep on Google: Google Meet for live instructor-led sessions, Google Analytics 4 and Google Tag Manager for tracking, Google Search Console for site verification, Google Workspace (OIDC) for single sign-on, and Google Calendar via the automation layer. If your stack is Google-centric, most of what you’d ask for is native.
2. Native integration catalog
The built-in connectors, by category. (Tool names are the third-party services; your Grow environment connects to them natively.)
| Category | Native connectors |
|---|---|
| Live sessions & video (ILT) | Zoom, Microsoft Teams, Webex, Google Meet, Calendly |
| Analytics & tracking | Google Analytics 4, Google Tag Manager, Mixpanel, Meta (Facebook) Pixel, TikTok Pixel, LinkedIn Insight Tag, Hotjar, Fullstory, Mouseflow, FullSession |
| CRM | HubSpot |
| Email marketing | Mailchimp, ActiveCampaign, AWeber, Kit (ConvertKit), GetResponse, Moosend, MailerLite, ConstantContact |
| Customer service / chat | Zendesk, Olark, Tawk.to, Freshchat, Intercom |
| Digital credentials | Accredible, Credly |
| Growth & conversion | Google Search Console, BDOW! (formerly Sumo), OptinMonster, Fomo (social proof) |
| Affiliates / referral | ReferralCandy, Refersion |
| Localization | Weglot (multi-language) |
| Accessibility | accessiBe |
| AI | OpenAI |
For live instructor-led training specifically, the Google Meet / Zoom / Teams / Webex connectors are what power scheduled sessions — see Live Sessions, Calendar & Events.
3. Your own systems (open standards)
Native connectors are for commercial SaaS tools. Your systems — warehouse, identity provider, custom apps — connect through standards, which are first-class, not workarounds:
| Need | How | Reference |
|---|---|---|
| Single sign-on | SAML or OIDC (incl. a dedicated Google Workspace path) | SSO & Identity Integration |
| Data warehouse / BI / HRIS | Authenticated API + signed webhooks | Webhooks, Pull-Based Data Access |
| Embedding external tools / assessments | LTI 1.3 (Consumer) with score passback | Section 3.1 below |
3.1 Embedding external tools and assessments (LTI 1.3)
LTI (Learning Tools Interoperability) is the education-industry open standard for plugging a third-party learning tool into a learning platform so it behaves like a native part of the course. Think of it as a universal adapter: instead of a custom-built connector for each tool, any LTI-compliant tool and platform can talk to each other.
Grow supports LTI 1.3 as a Consumer, which means Grow can host external tools inside its courses. Concretely:
- Embed external content, labs, simulations, or assessment engines directly inside a Grow course — the learner doesn’t leave Grow to use them.
- Progress and grades stay centralized in Grow, so your completion and certification reporting still sees a single source of truth.
- Score passback is supported via LTI Assignment & Grade Services (AGS) — the embedded tool reports a score back into Grow, which flows through the same completion/grade records your integration already consumes.
This is the answer when a client asks “can we use our own specialized safety-simulation or assessment tool, but keep one unified record of who passed?” Yes — embed it via LTI 1.3, and its results land in the same compliance record as everything else.
How tools are added. There’s no in-platform app store — you bring any LTI 1.3-compliant tool and connect it once by exchanging credentials (Plenum handles the setup for your environment). To find vetted tools, the industry registry is the 1EdTech Certified Product Directory (the closest thing to an LTI “marketplace”), which lists tools certified to integrate cleanly via LTI 1.3 / LTI Advantage. Grow acts as an LTI Consumer — it hosts external tools; it does not export Grow content into other systems.
4. Automation layer and the capability matrix
For anything without a native connector, Grow’s real-time events feed automation platforms — Zapier (3,000+ apps), Make, Integrately, Pabbly Connect — reaching effectively any modern tool. The honest “does it do X?” summary:
| Capability | Available? | How |
|---|---|---|
| Payments (Stripe, PayPal) | YES · Native | Built-in; card data stays with the processor (see Security & Data Governance) |
| CRM — HubSpot | YES · Native | Built-in connector |
| CRM — Salesforce | NOT NATIVE | Via SSO (SAML/OIDC) for identity, or Zapier / API for data. No built-in data connector — flag early if Salesforce is central. |
| Video / live sessions | YES · Native | Zoom, Teams, Webex, Google Meet, Calendly |
| Analytics / tracking | YES · Native | GA4, Google Tag Manager, Mixpanel, Meta Pixel, + more |
| Single sign-on | YES · Open standard | SAML / OIDC |
| Embedding external tools | YES · Open standard | LTI 1.3 + AGS (Section 3.1) |
| Warehouse / BI / HRIS | YES · Open standard | API + webhooks |
| Email notifications | YES · Native | Built-in email system (Section 5) |
| SMS notifications | NOT NATIVE | Automation layer or SMS provider (Section 5) |
| Thousands of other tools | YES · Via automation | Zapier / Make / Integrately / Pabbly |
Legend: YES = supported · NOT NATIVE = no built-in connector, but a supported path exists.
5. Notifications
Email — native, full lifecycle
Grow’s built-in notification system covers the lifecycle out of the box: signup, password reset, enrollment, course completion, and administrative alerts. Managed centrally, no integration work.
SMS — not native, but buildable (read the caveat)
There is no built-in SMS channel. Two supported paths, differing in delivery guarantees:
- Automation layer (e.g. Zapier → an SMS step). Triggered by the same completion/certificate webhooks you already use. Caveat: on this path a successful action means the message was queued, not confirmed delivered — no guaranteed-delivery acknowledgment. Fine for nudges; not for compliance-critical alerts.
- Direct SMS provider integration (e.g. Twilio). For delivery guarantees and full control, route the same events to a dedicated provider through a small integration Plenum builds.
Honest framing: SMS isn’t out-of-the-box, but it’s buildable on the exact events that drive your completion reporting — the path you choose is a function of how strong a delivery guarantee you need.
6. The native-vs-buildable boundary, stated plainly
- A native connector isn’t required for the integrations that matter most to you. Your warehouse, BI, HRIS, and identity systems connect through open standards (API, webhooks, SAML/OIDC, LTI) — first-class paths, not workarounds.
- Where something is “via automation,” that’s real and supported, but its guarantees depend on the platform in the middle. We’ll tell you which tier any given need lands in, and what that means for reliability.
When you have a specific tool or channel in mind, name it during onboarding and we’ll place it on this matrix for your environment.
7. Where to go next
- Live Sessions, Calendar & Events — the video connectors above, applied to instructor-led training.
- SSO & Identity Integration — the SAML/OIDC detail behind the SSO rows.
- Webhooks / Pull-Based Data Access — the events that power the automation-layer and SMS paths.
Prepared by Plenum Solutions for your evaluation. “Grow by Plenum” is operated and supported by Plenum on your behalf. Named third-party integrations are subject to confirmation for your specific environment. For integration design support, contact your Plenum engagement lead.
