LiveLoop integrations · LTI 1.3 · Native Databus ERP bridge · CSV everywhere else
Every video vendor's integrations page promises connectors with every LMS, CRM and HRMS on the planet. Most are aspirational. LiveLoop puts every integration in one of three honest tiers — open-standard (LTI 1.3 with your LMS), native Databus (SchoolDeck / CampusAlly / TutorDesk), or CSV bridge (everything else) — so your IT team knows exactly what they're signing up for at procurement.
LiveLoop Integrations is the buyer-side story of how an Indian institution's existing stack — LMS, SIS, school or college ERP, calendar, identity provider — connects to LiveLoop video sessions, organised into three honest tiers. Tier 1 is open standards: LTI 1.3 for LMS launch with Moodle, Canvas, Blackboard, D2L Brightspace, and any LMS that implements the spec; OAuth 2.0 sign-in with Google Workspace and Microsoft Entra ID; iCalendar feeds. Tier 2 is the native Databus stack: deep partnership-grade integration with SchoolDeck, CampusAlly and TutorDesk because they're sister products from the same engineering team. Tier 3 is the CSV bridge: for every other LMS, HRMS, ERP or CRM, attendance exports as CSV and uploads via the destination's bulk-import screen. We do not claim partner-API integrations with vendors we don't have agreements with.
Most institutions over-commit to integration complexity that delivers no real benefit. Run your existing stack through this triage — your IT lead picks the lowest tier that does the job, and procurement signs off in one read.
If/then logic for picking how LiveLoop talks to your existing stack. The same triage your IT lead will run during the demo.
A modern LMS that documents LTI 1.3 support — Moodle, Canvas, Blackboard, D2L Brightspace, or another spec-compliant platform.
A Databus product as your primary ERP — SchoolDeck (K-12 schools), CampusAlly (colleges) or TutorDesk (coaching / tuition centres).
Any platform LiveLoop doesn't have native or open-standard coverage for — including HRMS, generic ERPs, or older LMS versions without LTI 1.3.
The CTO at an Indian institution has seen 30 of these slides. Here's what they're tired of — and what we deliberately do differently.
Every vendor's logo grid shows 50+ platforms. None of the logos tell you whether the integration is a deep API partnership, an open-standard implementation, or a CSV import dressed up as automation. The buyer learns the truth six months later.
Many edtech video vendors list Salesforce, HubSpot, Workday, Cornerstone. They don't have partner-API status with any of them. They're CSV exports. When IT discovers this after signing, the relationship sours and the integration project slips a quarter.
LTI 1.1 is end-of-life. LTI 1.3 + LTI Advantage is current. Saying "LTI Certified" without the version is meaningless — and yet half the slides do exactly this. Your LMS admin needs to know the version to configure anything.
You can't evaluate an integration without reading the docs. Vendors who keep API documentation behind a sales-call wall are signalling that their developer story is thin. The integration matters too much to procure blind.
Procurement teams ask for the standards register. Here's the verified set — every line cites the maintaining body and the version your IT lead can search for.
Learning Tools Interoperability 1.3, including Names & Role Provisioning Services (NRPS) and Assignment & Grade Services (AGS) where the LMS supports them. Open specification — every spec-compliant LMS works.
OAuth 2.0 sign-in with Google Workspace and Microsoft Entra ID (formerly Azure AD). Minimum-scope discipline — calendar event read/write only, never inbox, drive or contacts.
Standards-compliant ICS feed for calendar apps including Apple Calendar. Subscribe to the feed URL; LiveLoop sessions appear in the calendar at the granularity the feed publishes.
Digital Personal Data Protection Act 2023 governs how LiveLoop processes student personal data flowing through any integration. Data fiduciary is the institution; LiveLoop is data processor.
UGC permits blended-mode delivery up to a defined component of regular HE programmes. The LMS-integrated session record + attendance CSV serves as the audit trail.
Chapter 9 requires schools to retain attendance + lesson records as part of the academic record retrievable during inspection. SchoolDeck integration plus LiveLoop recording satisfies this without manual reconciliation.
My team evaluated four video platforms for our 2,400-student college last September. Every other vendor sent a 40-page integrations PDF that claimed connectors for everything from Zoho to Workday. I asked for a one-pager describing depth per integration; none of them could produce it cleanly. The LiveLoop deck had three rows — LTI 1.3 for our Moodle, native bridge to CampusAlly, CSV for our HRMS. When my registrar asked what would actually flow on day one, I had an answer in writing. The board meeting took twelve minutes.
The right rollout starts at Tier 1, works down. Most institutions never need Tier 3 for their primary stack — they use Tier 1 or 2 for the main flow and Tier 3 for one or two edge platforms.
List every system that needs to talk to LiveLoop. Mark each as Tier 1 (open standard available), Tier 2 (Databus native), or Tier 3 (CSV bridge). Most institutions land on a 2-3 platform map within an hour.
For Tier 1, configure LiveLoop as an LTI 1.3 tool in your LMS admin console — the LMS vendor's docs explain the steps. For Tier 2, the Databus account team handles the wiring during onboarding; the IT lead reviews the SIS field map.
For platforms on Tier 3, decide who runs the CSV upload weekly. It's usually the L&D coordinator or the registrar's office assistant — a 5-minute weekly task, not a 5-week integration project. Document the column-map once; it never changes.
The "right answer" depends on what your existing stack already supports. Six common configurations seen across Indian institutions.
Schools running SchoolDeck as their ERP get the cleanest integration. LiveLoop session auto-launches from the timetable period, attendance flows to the SIS, recordings auto-share with confirmed absentees. CBSE Chapter-9 record-keeping satisfied without manual reconciliation.
Colleges typically run an LMS (Moodle) for content and an ERP (CampusAlly) for SIS. LTI 1.3 handles Moodle launch + roster; CampusAlly bridge handles attendance pipe-back. UGC blended-mode audit trail satisfied through Moodle's records.
Larger private universities often run Canvas or Blackboard for academics, plus separate HRMS for faculty (Workday/Darwinbox) and a CRM for admissions (no native LiveLoop bridge). LTI 1.3 covers academics; HR and CRM go through Tier 3.
IIT-JEE / NEET / Banking / UPSC coaching classes on TutorDesk get the native bridge: batch in TutorDesk = roster-gated LiveLoop session, attendance per session to the parent dashboard, recordings to absent students automatically.
Many state-board-affiliated schools run older LMS versions that pre-date LTI 1.3, or run their own custom-built portal. Tier 3 CSV is the realistic path until the school upgrades. We tell schools this upfront rather than promising integration that won't work.
Corporate L&D teams running LiveLoop for training (see the corporate-training-webinars solution) almost always use Tier 3 — exported attendance CSV uploads to Darwinbox / SAP SuccessFactors / Cornerstone / Zoho People via the existing bulk-attendance screen. No fake partner-API claim.
Every video vendor's integrations page shows a logo grid. Salesforce, HubSpot, Moodle, Canvas, Workday, SAP, Zoho, SuccessFactors, Slack, Teams — fifty or more logos in a 5×10 wall. The buyer's instinct is "wow, they cover everything." The IT team's instinct, six months later, is "wait, that 'Salesforce integration' is a CSV import you have to do manually every Friday."
LiveLoop's integrations page is deliberately structured the opposite way. We tell you which integrations are open-standard implementations, which are native Databus-cluster engineering, and which are CSV bridges — before you sign. The honesty is the buying signal. A procurement team that has been burned by aspirational integration claims signs faster with a vendor who labels the bridge as a bridge.
LiveLoop is built to the LTI 1.3 specification published by 1EdTech (formerly IMS Global). LTI 1.3 covers the secure launch flow, Names & Role Provisioning Services (NRPS) for roster sync, and Assignment & Grade Services (AGS) where the LMS exposes them. The implementation works with any LMS that documents LTI 1.3 support — Moodle, Canvas, Blackboard, D2L Brightspace, and others.
Where we get specific: the certification badge with 1EdTech is a separate audit process that institutional procurement may want in writing. We don't put "Certified" on this marketing page that the technical team would later have to retract. The technical compatibility is what powers your day-to-day workflow; the certification status is the procurement-audit layer. Ask your account team for the current certification documentation, and have your IT lead test the LTI launch in your sandbox LMS before signing.
LiveLoop, SchoolDeck, CampusAlly and TutorDesk are all built by Databus Technology Solutions in Chennai. That means the "integration" between LiveLoop and any of those three ERPs is not actually an external integration — it's internal engineering between sister teams that share an office, a data architecture, and a release cadence. The timetable period in SchoolDeck knows about the LiveLoop session because SchoolDeck wrote the auto-launch directly; not via a partner-API agreement that could change next year.
The boundary matters: Tier 2 is only the three Databus ERPs. We don't dress up Tier 1 (LTI 1.3 with third-party LMSes) as "native" because it isn't — it's open-standard implementation. The distinction protects the buyer from over-paying for "native depth" where the actual mechanism is the same LTI launch every spec-compliant LMS gets.
Half the institutions that procure LiveLoop run something that LiveLoop doesn't have native or LTI 1.3 coverage for — usually an older LMS, a custom-built portal, or a non-academic platform (HRMS, generic ERP). For those cases, we use the CSV bridge: after each session, LiveLoop produces a standard CSV with email, join time, duration, exit time. The institution uploads it via the destination's bulk-import screen.
This is the same pattern the corporate-training-webinars page uses. It is deliberately positioned as a feature because universal compatibility is more valuable than partner-API depth that breaks every two years. Every modern LMS, HRMS, ERP and CRM accepts CSV imports. The format never changes. The bridge doesn't break when the vendor changes their API or deprecates a SDK. It's a 5-minute weekly habit, not a 5-week integration project.
This is the most-bordered page in the cluster — four internal LiveLoop siblings plus three cross-cluster Databus pages all sit close to it. The discipline:
This page (/liveloop/solutions/integrations-api/) owns the IT-lead buyer story — the three-tier triage, the procurement narrative, the honest landscape.
/liveloop/features/integrations/ owns the developer mechanism — REST API endpoints, authentication scheme, webhook payload schemas, rate limits, sandbox environment, OAuth scope details, Zapier connector list. The page the engineer writes against; not the procurement deck.
/liveloop/features/calendar/ owns the calendar-sync mechanism specifically — Google Calendar, Outlook, two-way RSVP. This page references it; it doesn't duplicate it.
/schooldeck/features/virtual-classroom/ (cross-cluster) owns the SchoolDeck-side wrapper that surfaces LiveLoop inside the K-12 ERP timetable. The native Tier 2 bridge is documented from the SchoolDeck side there.
/schooldeck/features/auto-timetable/ (cross-cluster) owns the timetable build. LiveLoop reads it; SchoolDeck builds it. Two sides of one calendar; no overlap.
/liveloop/solutions/corporate-training-webinars/ uses the Tier 3 CSV pattern from this page for corporate-training attendance. Same mechanism, different buyer story.
/liveloop/solutions/certification-completion/ uses the integrations-API trigger matrix to disclose what's LiveLoop-native vs. needs-LMS vs. external-NCVET. Trigger-source honesty depends on the tier disclosure here.
Each sibling owns one thing. This solution page is the answer to the IT lead's first question: "Without reading 40 pages of docs, what does my integration with LiveLoop actually look like?" The feature page is the answer to the engineer's next question: "Now I'm building it — where are the endpoints?"
Most video vendors land in the left column. The right column is the honesty discipline this page exists to publish.
| What the IT lead needs to see | Logo-grid vendor | LiveLoop honest tiers |
|---|---|---|
| Depth labelled per integration | ✗ One logo wall, no depth | ✓ Tier 1 / 2 / 3 labelled |
| LTI version declared explicitly | ✗ "LTI certified" with no version | ✓ LTI 1.3 with Advantage scope |
| CSV labelled as CSV, not "automation" | ✗ "Native Salesforce" = CSV | ✓ CSV bridge named as Tier 3 |
| No partner-API claim without agreement | ✗ Claims first, verifies never | ✓ Only what we can back up |
| Native ERP integration named | ~ Generic "ERP supported" | ✓ SchoolDeck / CampusAlly / TutorDesk |
| OAuth scope discipline disclosed | ✗ "OAuth supported" — no scope detail | ✓ Calendar event read/write only |
| No grade-passback overclaim | ✗ "Quiz grades to LMS gradebook" | ✓ Boundary respected — LMS grades |
| DPDP Act 2023 posture stated | ✗ Global compliance, no India anchor | ✓ Data-processor relationship clear |
| Developer docs accessible without sales call | ~ Often behind a form | ✓ Linked on the feature page |
| Tier 3 path is honest, not hidden | ✗ "Fallback to CSV" — not headlined | ✓ Tier 3 is a feature, not shame |
Through LTI 1.3 — the open Learning Tools Interoperability standard maintained by 1EdTech / IMS Global. LiveLoop is built to LTI 1.3, which lets your students launch a LiveLoop session from inside a Moodle course page, a Canvas assignment, a Blackboard module, or a D2L Brightspace activity, with single sign-on and roster synchronisation via Names and Role Provisioning Services (NRPS). The integration uses an open standard, so it works with any LMS that documents LTI 1.3 support — your IT team configures LiveLoop as an LTI tool the same way they would any other LTI-compliant product.
LiveLoop is built to the LTI 1.3 specification. Certification status with 1EdTech is something we recommend your institution's IT team verify in writing before going to procurement — we don't put a marketing claim on this page that the technical team would have to retract. The technical compatibility is what matters for the day-to-day integration; the certification badge is the audit-trail layer your procurement may also need.
Native, because they're sister products. SchoolDeck (K-12 school ERP), CampusAlly (college ERP) and TutorDesk (coaching/tuition centres) are built by the same Databus engineering team in Chennai. LiveLoop sessions auto-launch from the period in the SchoolDeck (or CampusAlly / TutorDesk) timetable, roster-gating is automatic, recordings auto-share with absentees, and attendance pipes back into the SIS without any CSV step. The cross-cluster wrapper for SchoolDeck lives at /schooldeck/features/virtual-classroom/.
No, and we do not claim a partner-API integration with any of them. LiveLoop is a video conferencing platform, not a marketing-automation or HR tool. If you need to land LiveLoop session data in one of these platforms, the honest path is the CSV bridge — export session attendance, upload via the platform's existing bulk-attendance or bulk-activity screen. We do not record CRM lead activities or push webinar attendance as marketing leads, because that's not what LiveLoop is for.
LiveLoop does not grade quizzes. Polls during a live session are observable participation signals — not assessments. The grading, scoring and gradebook write-back belong to your LMS (or to SchoolDeck for K-12 schools) where the assessment is actually authored. Where the LMS supports LTI Assignment and Grade Services (AGS), an external assessment tool can write its score using that — but the score wasn't computed inside LiveLoop. We honour the same boundary the certification-completion solution does: examinations live in SchoolDeck / TutorDesk / external LMS, not in LiveLoop.
The developer-mechanism content — REST API endpoints, authentication, webhook payloads, rate limits, sandbox environment — lives on the feature page at /liveloop/features/integrations/. This page (the solution page) is for IT leads and integration architects evaluating which tier fits their stack. The feature page is for the developer who is actually writing the integration code. The two pages are split deliberately so the buyer story doesn't drown the developer reference and vice versa.
Google Workspace and Microsoft Entra ID (formerly Azure AD) via OAuth 2.0, with minimum-scope discipline — we ask only for sign-in and calendar event read/write, never for inbox, drive, or contacts. For institutions using their LMS as the identity source, LTI 1.3 handles sign-on through the LMS's own session — students don't need a separate LiveLoop password. Other SAML 2.0 identity providers are roadmap items; verify the current status with your IT lead before procurement.
Two-way sync with Google Calendar and Microsoft Outlook (Exchange Online). Schedule a LiveLoop session from either calendar, the join URL is added automatically, RSVPs sync back. Recurring sessions get one permanent join URL for the whole series — a Class 9-A Maths class on Mondays gets one URL for the full term, not a new URL every week. Apple Calendar / iCal support via standards-compliant ICS feed; the granular two-way RSVP sync is documented per provider on the feature page.
After each session, LiveLoop produces a CSV with email, join time, total minutes attended, exit time and (optionally) poll-vote rows. The institution's coordinator downloads it and uploads it to the destination platform's existing bulk-import screen — every modern LMS, HRMS or ERP accepts CSV imports. The format is plain CSV with documented column headers; no proprietary schema to learn. This is the same CSV-bridge pattern used on the corporate-training-webinars solution.
Yes, but the configuration is the developer's job on the feature page, not the IT lead's choice on this page. The honest event list — session.started, session.ended, recording.ready, transcript.ready, attendance.export — and the payload schema, retry policy, and signing key rotation live at /liveloop/features/integrations/. For most institutions the CSV bridge and the native SchoolDeck/CampusAlly/TutorDesk integration cover the day-to-day flow without anyone writing webhook handlers.
Walk through the triage with our team. We'll map your current stack to a tier in real time — LMS, ERP, calendar, HRMS — and you'll leave the call with a one-page procurement deck.
