Coassemble
Education & LMSConnect AI agents to Coassemble, an online employee training platform. Agents manage courses and collections, update learners and clients, and read tracking data so training progress reporting stays hands-off.
What This Integration Enables
Coassemble's headless API is built around a concept most training platforms leave out: the client. Users belong to a client identifier, courses and collections can be owned by one, tracking is filterable by one, and Duplicate Course exists specifically so a template course can be handed to a different client. That shape tells you who this is for. If your training goes to more than one distinct group, franchise locations, portfolio companies, partner networks, or customers you deliver enablement to, Coassemble models that separation natively instead of asking you to fake it with tags.
The connector covers courses and collections, the client and user identities underneath them, and four different views of learner tracking: by course, by collection, by screen, and by user. Get Course Content is the quiet standout, returning normalized text for every screen along with a catalog of media assets. That is what you need when the goal is to feed existing training material into an index, a summarizer, or a search surface rather than to deliver it. Webhook endpoints are managed here too, and it is worth being precise about what that means: this connector registers endpoints that Coassemble calls, and exposes no triggers of its own, so event-driven flows begin at the receiver you operate or on a schedule.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Provisioning a client's training from a template
A new franchise location or customer account is approved. The agent runs Duplicate Course on the standard onboarding course, overriding the client identifier so the copy belongs to the new client from the moment it exists. It then runs Create Collection to group that course with the compliance modules the client needs, in the order they should be taken, and List Users to confirm the client's learners have landed. What used to be an afternoon of copying screens becomes a step in the flow that already created the account.
Mandatory training reporting that nobody has to assemble
Every Monday the agent runs Get Course Trackings for each mandatory course, reading progress_percent along with the score and pass flag that scored quizzes produce. It writes the result into the reporting sheet in Google Sheets that department heads already open, one row per learner per course. Where a learner has not started a course whose due date is approaching, the agent posts the name to their manager in Slack rather than to a group channel, because a reminder that reaches the person accountable for it is the only kind that changes anything.
Turning existing courses into an answerable knowledge surface
The support team wants the product training to be searchable, not just completable. The agent runs List Courses, then Get Course Content on each one, which returns the normalized screen text with titles, descriptions, and asset alt text across every translation variant. That content goes into an index an AI step can query. Before anything is published to the support team, a training lead reviews the extracted set, because course content written to be taught in sequence can read very differently when a single screen is returned on its own as an answer.
Human-in-Loop Highlight
This connector is careful with content and blunt with clients. Delete Course and Delete Collection are soft deletes with Restore Course and Restore Collection sitting right next to them. Delete Client has no counterpart at all, and it removes the client plus every object associated with its identifier, including its users and their tracking data. That asymmetry is the whole gate: Coassemble gave you an undo for the material and no undo for the record of who completed it. So when an offboarding flow reaches that call, the agent stops and posts the blast radius to the training owner: "Contract for Meridian Group ended 31 July. Delete Client would remove 1 client, 214 users, and 1,908 tracking records, including 63 completions of Food Safety Level 2 recorded in the last 12 months. Tracking cannot be restored. Export attached. Delete the client, delete the users only, or leave the record in place?" The agent has already done the part that takes time, which is working out what is actually attached. The person decides whether evidence of completed training should stop existing. That is the digital andon cord in its most literal form: the line stops before the irreversible step, not after it.
Agent Capabilities
29 actionsCourses
6- List Courses Returns a paginated list of courses in the workspace, filterable by title, owning user, or client identifier, and optionally including soft-deleted ones. Used to discover course IDs for tracking, duplication, and content extraction.
- Get Course Returns a single course by numeric ID with its title, description, thumbnail, publish state, and ownership fields. Used to confirm what a course is before acting on it.
- Get Course Content Returns the normalized text of every screen in a course across all translation variants, plus a catalog of media assets with fetchable URLs. Used to feed existing training material into indexing, transcription, or summarization rather than to deliver it.
- Duplicate Course Creates a copy of a course, optionally reassigning it to a different user or client identifier. The provisioning workhorse for anyone delivering the same curriculum to more than one client.
- Delete Course Soft-deletes a course by numeric ID. Reversible with Restore Course, which is what makes routine content cleanup safe to automate.
- Restore Course Brings a soft-deleted course back to active. Used to reverse a cleanup that went further than intended.
Collections
5- List Collections Returns a paginated list of collections, the curated learning paths that group courses, filterable by owning user or client identifier. Used to resolve a path before assigning or reporting on it.
- Get Collection Returns a single collection by numeric ID with its title, description, and active state. Used to confirm the shape of a path before changing it.
- Create Collection Creates a learning path from a title, with optional description, owning user, client identifier, theme, and an ordered list of course IDs to include. Used to assemble a client's curriculum in one call.
- Delete Collection Soft-deletes a collection by numeric ID. Reversible with Restore Collection.
- Restore Collection Brings a soft-deleted collection back to active. Used to reverse a path removal.
Identities
8- List Clients Returns a paginated list of client identifiers with the number of users assigned to each. Used to reconcile Coassemble's client list against the operations system that owns those relationships.
- Get Client Returns a single client by its stable identifier with its user count and timestamps. Used to size an action before taking it.
- Update Client Updates a client's metadata. Note that the supplied metadata replaces the existing metadata rather than merging into it, so a one-field intent needs the full object or it will quietly drop the rest.
- Delete Client Deletes a client and every object associated with its identifier, including its users and their tracking data. Destructive, with no restore, and the reason this page routes it through a person.
- List Users Returns a paginated list of learners, optionally filtered to a single client identifier. Used for roster reconciliation.
- Get User Returns a single learner by stable identifier with display name, avatar, client, and timestamps. Used before an update or a targeted report.
- Update User Updates a learner's metadata and profile fields, merging the metadata object onto the user rather than replacing it. The name and avatar shortcuts set the display fields without building a full object.
- Delete User Deletes a learner by stable identifier, and lets you choose what happens to their courses: reallocate to another user, delete them, or leave them in place. The reallocation option is what makes offboarding an author survivable.
Tracking
7- Get Course Trackings Returns learner progress records for a course, each with progress_percent and, for scored quizzes, a score from 0 to 100 and a passed flag, filterable by user, client, and date range. The core reporting call.
- Get Collection Trackings Returns learner progress for a collection with a per-course breakdown for each learner, filterable by date range. Used to report on a whole pathway rather than a single course.
- Get Screen Trackings Returns per-screen progress for a course, showing how far each learner got screen by screen along with quiz attempts. Used to find where a course loses people.
- Get User Trackings Returns every tracking record for one learner across all courses, with summary totals of viewed and completed courses. Used to answer a question about one person, and to size what an offboarding action would remove.
- Get Tracking Returns a single tracking record by numeric ID. Used to inspect one record referenced elsewhere.
- Get Collection Tracking Returns a single collection tracking record by numeric ID. Used for the same purpose at the pathway level.
- Delete Tracking Deletes a learner's tracking record for a specific course, resetting their progress. Used when a course is reissued and a genuine retake is required, which is a decision rather than a cleanup rule.
Webhooks
3- List Webhook Endpoints Returns every registered webhook endpoint along with the full list of subscribable event names, such as course.commenced, course.completed, and course.created. Signing secrets are never included here.
- Create Webhook Endpoint Registers an https endpoint subscribed to at least one event and generates its signing secret. The secret is returned only in this response, so store it immediately; rotating means deleting the endpoint and creating it again.
- Delete Webhook Endpoint Removes an endpoint by numeric ID. Deliveries stop immediately and the signing secret is invalidated, so sequence a rotation with the gap in mind.
Frequently Asked Questions
What can FlowRunner do with Coassemble?
FlowRunner agents can run List Courses, Get Course, and Get Course Content in Coassemble, plus 26 more actions.
Does connecting Coassemble to FlowRunner require OAuth?
No. Coassemble connects to FlowRunner with an API key, no OAuth flow required.
Can Coassemble trigger a FlowRunner workflow automatically?
Coassemble doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Coassemble
$100 in credits. No card required. Connect in minutes.