Your team already has tools. Put them in the lesson.
Nobody wants to rebuild a Figma file, a Google Doc or a Zoom session inside a learning platform. Paste the link and it opens where the learner already is — no rebuild, no export, no second copy to keep up to date.
One link, and it plays where the learning happens.
Video, meetings, design files, spreadsheets, forms and whiteboards sit inside the lesson rather than behind it — so a learner is never sent somewhere else and told to come back.
Search for the tool you actually use
Every connection below is grouped by how it works, because the difference matters more than the logo does. Anything still being built says so.
32 Integrationen
Anthropic
NativBring your own Anthropic key. Drafting, marking suggestions and the tutor run against it.
Google Gemini
NativBring your own Google Gemini key, or fall back to the platform's.
OpenAI
NativBring your own OpenAI key so AI generation runs on your account, per organisation.
Pexels
NativSearch Pexels without leaving the lesson you are writing.
Pixabay
NativSearch Pixabay for illustration and photography as you build.
Resend
NativConnect your own Resend account so mail sends from your domains, under your reputation.
Unsplash
NativSearch Unsplash from inside the editor and drop a photo straight into a lesson.
Airtable
EinbettungAirtable views and records, embedded.
Any URL or iframe
EinbettungAnything else with a URL that permits embedding. The escape hatch, and it is used.
Canva
EinbettungCanva designs and decks, embedded rather than exported.
CodePen
EinbettungA live CodePen, for teaching anything where the code has to run.
Figma
EinbettungA Figma file or prototype, live — so the lesson never shows a stale screenshot.
Google Docs
EinbettungGoogle Docs render in place, so edits show without a re-upload.
Google Forms
EinbettungGoogle Forms for collection you already run there.
Google Meet
EinbettungA Google Meet link sits in the lesson rather than in a separate calendar invite.
Google Sheets
EinbettungA Google Sheet, live — data that changes without anyone reissuing the lesson.
Google Slides
EinbettungGoogle Slides decks play inline.
HTML5 activity
EinbettungAny HTML5 activity with a launch URL, played in the lesson.
Kahoot
EinbettungA Kahoot game inside the lesson. Scores stay in Kahoot.
Loom
EinbettungDrop in a Loom recording — useful when a walkthrough beats a written step.
Microsoft Teams
EinbettungMicrosoft Teams meetings open from inside the course.
Miro
EinbettungA Miro board for workshops and group work, inside the lesson.
Notion
EinbettungNotion pages stay in Notion and appear in the course, current.
SurveyMonkey
EinbettungSurveyMonkey questionnaires, embedded.
Typeform
EinbettungTypeform surveys and feedback, in the flow of the course.
Vimeo
EinbettungVimeo videos play inline, including anything private to your account.
YouTube
EinbettungPaste a YouTube link and it plays in the lesson, at the timestamp you choose.
Zoom
EinbettungPut a live Zoom session in the sequence, where learners already are.
LTI 1.3
StandardIn EntwicklungLTI 1.3 tool launch. Modelled in the product; not running yet.
SCORM 1.2
StandardIn EntwicklungSCORM 1.2 packages. Modelled in the product; the runtime is still being built.
SCORM 2004
StandardIn EntwicklungSCORM 2004 packages. Modelled in the product; the runtime is still being built.
xAPI
StandardIn EntwicklungxAPI statements to an LRS. Modelled in the product; not running yet.
What an embed does, and what it does not do
An embed renders someone else's page inside a lesson. That is genuinely useful — the learner stays in one place, and the content stays current because it is still living in the tool that owns it. It is also the limit of what happens. Lurno does not read the contents of your Figma file, does not receive a score back from a Kahoot game, and does not know whether anyone spoke in the Zoom call. Progress in Lurno is recorded against the lesson, not against what the embedded tool thinks happened inside it.
- Embed versus native
- An embed needs no credential and exchanges no data — you paste a link and it renders. A native integration means Lurno holds a key and calls that service's API, which is how bring-your-own AI keys and sending mail from your own domain work. Both are on this page and each card says which it is, because a buyer who assumes the first is the second will be disappointed at exactly the wrong moment.
What buyers ask about integrations
Bring the tools you have.
Show us your stack on a demo call and we will tell you which parts drop straight in, which need an embed, and which we cannot do yet.