Naar de inhoud
Integrations

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.

OpenAIAnthropicGoogle GeminiResendUnsplashPexelsPixabayYouTubeVimeoLoomZoomGoogle MeetMicrosoft TeamsFigma
What connects

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.

CanvaMiroNotionGoogle DocsGoogle SlidesGoogle SheetsAirtableGoogle FormsTypeformSurveyMonkeyKahootCodePenHTML5 activityAny URL or iframe
The full list

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 integraties

  • Anthropic

    Native

    Bring your own Anthropic key. Drafting, marking suggestions and the tutor run against it.

  • Google Gemini

    Native

    Bring your own Google Gemini key, or fall back to the platform's.

  • OpenAI

    Native

    Bring your own OpenAI key so AI generation runs on your account, per organisation.

  • Pexels

    Native

    Search Pexels without leaving the lesson you are writing.

  • Pixabay

    Native

    Search Pixabay for illustration and photography as you build.

  • Resend

    Native

    Connect your own Resend account so mail sends from your domains, under your reputation.

  • Unsplash

    Native

    Search Unsplash from inside the editor and drop a photo straight into a lesson.

  • Airtable

    Insluiting

    Airtable views and records, embedded.

  • Any URL or iframe

    Insluiting

    Anything else with a URL that permits embedding. The escape hatch, and it is used.

  • Canva

    Insluiting

    Canva designs and decks, embedded rather than exported.

  • CodePen

    Insluiting

    A live CodePen, for teaching anything where the code has to run.

  • Figma

    Insluiting

    A Figma file or prototype, live — so the lesson never shows a stale screenshot.

  • Google Docs

    Insluiting

    Google Docs render in place, so edits show without a re-upload.

  • Google Forms

    Insluiting

    Google Forms for collection you already run there.

  • Google Meet

    Insluiting

    A Google Meet link sits in the lesson rather than in a separate calendar invite.

  • Google Sheets

    Insluiting

    A Google Sheet, live — data that changes without anyone reissuing the lesson.

  • Google Slides

    Insluiting

    Google Slides decks play inline.

  • HTML5 activity

    Insluiting

    Any HTML5 activity with a launch URL, played in the lesson.

  • Kahoot

    Insluiting

    A Kahoot game inside the lesson. Scores stay in Kahoot.

  • Loom

    Insluiting

    Drop in a Loom recording — useful when a walkthrough beats a written step.

  • Microsoft Teams

    Insluiting

    Microsoft Teams meetings open from inside the course.

  • Miro

    Insluiting

    A Miro board for workshops and group work, inside the lesson.

  • Notion

    Insluiting

    Notion pages stay in Notion and appear in the course, current.

  • SurveyMonkey

    Insluiting

    SurveyMonkey questionnaires, embedded.

  • Typeform

    Insluiting

    Typeform surveys and feedback, in the flow of the course.

  • Vimeo

    Insluiting

    Vimeo videos play inline, including anything private to your account.

  • YouTube

    Insluiting

    Paste a YouTube link and it plays in the lesson, at the timestamp you choose.

  • Zoom

    Insluiting

    Put a live Zoom session in the sequence, where learners already are.

  • LTI 1.3

    StandaardIn ontwikkeling

    LTI 1.3 tool launch. Modelled in the product; not running yet.

  • SCORM 1.2

    StandaardIn ontwikkeling

    SCORM 1.2 packages. Modelled in the product; the runtime is still being built.

  • SCORM 2004

    StandaardIn ontwikkeling

    SCORM 2004 packages. Modelled in the product; the runtime is still being built.

  • xAPI

    StandaardIn ontwikkeling

    xAPI statements to an LRS. Modelled in the product; not running yet.

The honest version

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.
Questions

What buyers ask about integrations

Not yet. SCORM 1.2, SCORM 2004, xAPI and LTI 1.3 are modelled in the product but their runtime is still being built, so courseware locked in a SCORM package is not something we can run today. If your library is mostly SCORM, that is a real reason to wait for us rather than switch now, and it is better to know that before a demo than during one.

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.