Integrations overview
The ways Coassemble connects to other tools: media in courses, courses inside your tools, SCORM in and out, data through the API, and AI assistants over MCP.
Yes, in a few different ways depending on what you're trying to do: bring media into your courses, put courses inside your other tools, run courses in your existing LMS, move data between Coassemble and other systems, and connect your AI assistant.
Coassemble is built to fit into the stack you already have. Because a course can be shared as a link, embedded in other tools, exported to SCORM, or driven through an API, it connects to your tools in whichever way suits the job. Here are the main things people connect Coassemble to, and how.
How do I bring media and content into my courses?
Several integrations let you add content to a course without leaving the editor:
- Video, from YouTube, Vimeo and Loom, embedded directly into screens.
- Images, from the built-in Pexels stock photography library, royalty-free and inserted straight into a screen.
- GIFs, from GIPHY, to add energy or humour to a screen.
- Interactive demos, from Arcade, for product walkthroughs inside a course.
Your team pulls in the media they need from tools they already use, in the flow of building.
How do I put courses inside the tools my team uses?
You can place learning where work already happens:
- Embed courses in your tools, such as Notion pages, HubSpot landing pages and knowledge base articles, intranets, and wikis like Confluence and SharePoint. Copy the course's share link from its Share window and paste it into the tool's embed block, so training sits inline with your other content. You don't need embed code.
- Share through communication tools, such as Slack, so people can start a course from a message or a dedicated training channel.
Because a Coassemble course is a shareable link, you aren't limited to a fixed list: you can drop it almost anywhere that accepts a link or an embed.
Can I run courses in my existing LMS?
Yes. If you already use a learning management system, you can export a course as a SCORM package and upload it there. This is how Coassemble works with platforms like 360Learning, Docebo and aNewSpring, as well as other SCORM-compatible systems, with completion and results reported back through the LMS. SCORM export isn't available on the legacy Flow plan.
You can also go the other way. A SCORM package from Articulate Rise or Storyline, Adobe Captivate or iSpring can be hosted in Coassemble as authored, or converted into a fully editable Coassemble course, with anything that couldn't be converted listed for review.
How do I move data between Coassemble and other systems?
For a deeper connection, you can move data between Coassemble and your other tools using the API and webhooks. Pass results such as completions and quiz scores into a CRM, data warehouse or internal app, for example sending completions into HubSpot contact records, and receive a server-to-server message the moment a course is started or completed so your systems stay in sync. This works with any system that can call an API or receive a webhook.
Webhooks are set up in the Developer console: select Developer in the navigation, then the Webhooks tab. Each endpoint gets its own signing secret when you create it, so you can verify that a delivery really came from Coassemble.
The legacy Flow plan has no API access. The legacy Hub plan has read-only API access, without webhooks or the Generate API.
Can I connect my AI assistant?
Yes. You can connect an AI assistant such as Claude to your workspace over MCP (the Model Context Protocol), and have it build and manage courses for you. Create a connection in your Settings, add the connection URL to your assistant, and sign in once to authorise it. From then on it can create courses, edit content, add your own images, review a course with Course Coach, preview screens the way learners see them, restructure and organise, publish and share, export SCORM where SCORM export is available to you, and read your course analytics, using over 50 tools.
MCP is an open standard, so this works with any assistant that supports connecting to a remote MCP server and signing in.
If you build your own product on Coassemble, the same agent tools are available to your application over MCP or REST, so your product can create and change courses for your users directly.
Frequently asked questions
Does Coassemble integrate with a specific tool?
Often yes, and even where there's no dedicated integration, you can usually share a course as a link or paste its share link into the tool's embed block, so it works with most tools that accept a link or an embed. For data, anything that can call the API or receive a webhook can connect.
Can I use Coassemble with my existing LMS?
Yes. Export your course as SCORM and upload it to your LMS, including platforms like 360Learning, Docebo and aNewSpring.
Can I get Coassemble data into my CRM or other systems?
Yes, through the API and webhooks. You can pass results such as completions and quiz scores into other tools, for example HubSpot, and have your systems notified automatically.
What happens if a webhook delivery fails?
Coassemble makes up to six attempts, waiting roughly a minute, then five minutes, thirty minutes, two hours and six hours between them. A delivery counts as successful on any 2xx response, and each request times out after ten seconds.
Can I connect my AI assistant to Coassemble?
Yes. Connect it over MCP from the Settings area, sign in once to authorise it, and it can build and manage courses in your workspace. Course generation still runs on Coassemble's own AI, so the courses it produces behave the same as ones you build in the app.