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 件の連携
Anthropic
ネイティブBring your own Anthropic key. Drafting, marking suggestions and the tutor run against it.
Google Gemini
ネイティブBring your own Google Gemini key, or fall back to the platform's.
OpenAI
ネイティブBring your own OpenAI key so AI generation runs on your account, per organisation.
Pexels
ネイティブSearch Pexels without leaving the lesson you are writing.
Pixabay
ネイティブSearch Pixabay for illustration and photography as you build.
Resend
ネイティブConnect your own Resend account so mail sends from your domains, under your reputation.
Unsplash
ネイティブSearch Unsplash from inside the editor and drop a photo straight into a lesson.
Airtable
埋め込みAirtable views and records, embedded.
Any URL or iframe
埋め込みAnything else with a URL that permits embedding. The escape hatch, and it is used.
Canva
埋め込みCanva designs and decks, embedded rather than exported.
CodePen
埋め込みA live CodePen, for teaching anything where the code has to run.
Figma
埋め込みA Figma file or prototype, live — so the lesson never shows a stale screenshot.
Google Docs
埋め込みGoogle Docs render in place, so edits show without a re-upload.
Google Forms
埋め込みGoogle Forms for collection you already run there.
Google Meet
埋め込みA Google Meet link sits in the lesson rather than in a separate calendar invite.
Google Sheets
埋め込みA Google Sheet, live — data that changes without anyone reissuing the lesson.
Google Slides
埋め込みGoogle Slides decks play inline.
HTML5 activity
埋め込みAny HTML5 activity with a launch URL, played in the lesson.
Kahoot
埋め込みA Kahoot game inside the lesson. Scores stay in Kahoot.
Loom
埋め込みDrop in a Loom recording — useful when a walkthrough beats a written step.
Microsoft Teams
埋め込みMicrosoft Teams meetings open from inside the course.
Miro
埋め込みA Miro board for workshops and group work, inside the lesson.
Notion
埋め込みNotion pages stay in Notion and appear in the course, current.
SurveyMonkey
埋め込みSurveyMonkey questionnaires, embedded.
Typeform
埋め込みTypeform surveys and feedback, in the flow of the course.
Vimeo
埋め込みVimeo videos play inline, including anything private to your account.
YouTube
埋め込みPaste a YouTube link and it plays in the lesson, at the timestamp you choose.
Zoom
埋め込みPut a live Zoom session in the sequence, where learners already are.
LTI 1.3
標準規格開発中LTI 1.3 tool launch. Modelled in the product; not running yet.
SCORM 1.2
標準規格開発中SCORM 1.2 packages. Modelled in the product; the runtime is still being built.
SCORM 2004
標準規格開発中SCORM 2004 packages. Modelled in the product; the runtime is still being built.
xAPI
標準規格開発中xAPI 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.