> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/other/coassemble.md).

# Coassemble

Connect Coassemble to Coupler.io to export learner progress, course completion, and training tracking data into Google Sheets or BigQuery.

Coassemble is an online training platform that lets you build, deliver, and track employee training courses. It's used by teams to create structured learning content and monitor how learners progress through it. Connecting Coassemble to Coupler.io lets you pull your training data into any destination for analysis and reporting.

## Why connect Coassemble to Coupler.io?

* **Track learner progress** by exporting completion and tracking data into Google Sheets, BigQuery, or your BI tool of choice
* **Analyze course performance** by combining course metadata with tracking records to see which courses drive the most engagement
* **Feed AI tools** like ChatGPT, Claude, or Gemini with your training data to surface insights, flag at-risk learners, or generate training summaries
* **Automate reporting** so your L\&D or HR team always has up-to-date data without manual exports

## Prerequisites

* A Coassemble account with at least one course created
* API credentials (User Token and Organization Token) from your Coassemble account settings
* A Coupler.io account (free plan works to get started)

## Quick start

{% hint style="success" %}
Start with the **Trackings** entity — it contains the richest data for reporting on learner progress and course completion.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, go to the Data Flows section, and click **Add data flow**. Search for and select **Coassemble** as your source.
{% endstep %}

{% step %}
**Enter your Coassemble API credentials.** You'll need your **User Token** and **Organization Token**. Find these in your Coassemble account under Settings → API. Paste both tokens into the Coupler.io connection form.
{% endstep %}

{% step %}
**Select an entity.** Choose what data you want to pull — Courses, Screen types, or Trackings. You can add more sources to the same data flow later to bring in multiple entities.
{% endstep %}

{% step %}
**Choose your destination.** Pick where you want the data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your Coassemble data will appear in your destination.
{% endstep %}
{% endstepper %}

## Coassemble data overview

Coassemble exposes three entities through Coupler.io: course definitions, screen type configurations, and learner tracking records. The richest data for reporting lives in Trackings, which captures how individual users move through your training content.

## Entities

| Entity       | Best used for                                               |
| ------------ | ----------------------------------------------------------- |
| Courses      | Course catalog, metadata, content structure                 |
| Screen types | Understanding how content is structured across your courses |
| Trackings    | Learner progress, completion rates, time-on-course analysis |

## Courses

#### Course fields

| Field          | Description                                      |
| -------------- | ------------------------------------------------ |
| id             | Unique identifier for the course                 |
| name           | Course title                                     |
| description    | Course description or summary                    |
| status         | Whether the course is active, draft, or archived |
| created\_at    | When the course was created                      |
| updated\_at    | When the course was last modified                |
| lessons\_count | Number of lessons in the course                  |
| screens\_count | Total number of screens across all lessons       |

## Screen types

#### Screen type fields

| Field       | Description                                 |
| ----------- | ------------------------------------------- |
| id          | Unique identifier for the screen type       |
| name        | Screen type name (e.g., video, quiz, slide) |
| description | What the screen type is used for            |

## Trackings

#### Tracking fields

| Field         | Description                                          |
| ------------- | ---------------------------------------------------- |
| id            | Unique tracking record identifier                    |
| user\_id      | ID of the learner being tracked                      |
| course\_id    | ID of the course being tracked                       |
| status        | Completion status (e.g., in progress, completed)     |
| progress      | Percentage of course completed                       |
| started\_at   | When the learner started the course                  |
| completed\_at | When the learner finished the course (if applicable) |
| score         | Assessment score, where applicable                   |

## Common field combinations

* **Courses + Trackings** — Join on `course_id` to see completion rates and scores broken down by course. Use the **Join** transformation in Coupler.io to merge these two entities.
* **Trackings over time** — Use `started_at` and `completed_at` to calculate time-to-completion per course or per learner cohort.
* **Screen types + Courses** — Understand what content formats are most used across your course catalog.

## Use cases by role

{% tabs %}
{% tab title="L\&D teams" %}

* Monitor which courses have low completion rates and prioritize updates
* Identify learners who started but haven't finished training
* Compare average scores across courses to spot content that may be too difficult
* Build a live completion dashboard in Looker Studio or Google Sheets
  {% endtab %}

{% tab title="HR & People ops" %}

* Report on mandatory training compliance across teams or departments
* Track when employees completed onboarding courses
* Combine Coassemble tracking data with HRIS data to correlate training completion with performance metrics
  {% endtab %}

{% tab title="Managers" %}

* See a snapshot of your team's training progress without logging into Coassemble
* Get automated reports in your inbox or Slack using scheduled data flows
* Use AI destinations like ChatGPT or Claude to generate plain-language summaries of your team's training status
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Coassemble's API is accessed via Airbyte connector in Coupler.io — both User Token and Organization Token are required for authentication
* The Trackings entity is updated as learners progress, so more frequent refreshes give you a more current view of completion status
* Screen types is a relatively static reference entity — you don't need to sync it frequently unless you're actively building new course content
* If you manage multiple Coassemble organizations, you'll need a separate data flow per organization token; use the **Append** transformation to combine tracking data across organizations into one destination

## Coassemble common issues

### Connection issues

<details>

<summary>Authentication fails when entering API credentials</summary>

Coassemble requires **two** tokens: a User Token and an Organization Token. If either is missing or entered in the wrong field, the connection will fail. Double-check that you've copied both tokens from Coassemble's Settings → API section and pasted them into the correct fields in Coupler.io.

{% hint style="warning" %}
Tokens are case-sensitive and may contain special characters — copy-paste rather than retyping them manually.
{% endhint %}

</details>

<details>

<summary>Connection succeeds but no data appears in the destination</summary>

This usually means the connected Coassemble account has no data for the selected entity. For example, if you select Trackings but no learners have started any courses yet, the result will be an empty table. Try switching to the Courses entity to confirm the connection is working.

</details>

### Missing data

<details>

<summary>Some courses are missing from the Courses entity</summary>

Only courses that are visible to the authenticated user's organization will be returned. If you have courses in a different organization or workspace, you'll need to create a separate data flow using that organization's token.

</details>

<details>

<summary>Tracking records are missing for some users</summary>

Trackings are only created when a learner actively starts a course. Users who have been assigned a course but haven't opened it yet won't appear in the Trackings entity. This is expected behavior — there's no record until the learner takes action.

</details>

<details>

<summary>completed_at field is empty for some tracking records</summary>

If a learner has started a course but not finished it, `completed_at` will be null. This is correct — only fully completed courses have a value in this field. Use the `status` and `progress` fields to identify in-progress learners.

</details>

### Permission errors

<details>

<summary>"Unauthorized" or "403" error when connecting</summary>

This typically means the User Token belongs to an account that doesn't have API access enabled, or the Organization Token doesn't match the user's organization. Verify in Coassemble that API access is enabled for your account and that both tokens are from the same organization.

{% hint style="danger" %}
If your Coassemble plan doesn't include API access, you won't be able to connect via Coupler.io. Check with your Coassemble account administrator or plan details.
{% endhint %}

</details>

### Data discrepancies

<details>

<summary>Progress percentages don't match what I see in Coassemble</summary>

Coupler.io pulls a snapshot of data at the time of the sync. If a learner completed more of a course after your last data flow run, the progress field in your destination will be out of date. Run the data flow again or increase your refresh frequency to keep the data current.

</details>

### Rate limits

<details>

<summary>Data flow fails or times out with large tracking datasets</summary>

Coassemble's API may throttle requests when pulling large volumes of tracking data. If this happens, try syncing individual entities in separate data flows rather than combining multiple sources in a single run. Splitting the load can help avoid timeout errors.

</details>

## Coassemble FAQ

<details>

<summary>Where do I find my Coassemble API tokens?</summary>

Log in to Coassemble and go to **Settings → API**. You'll find your User Token and Organization Token there. You need both to authenticate the connection in Coupler.io. If you don't see an API section, your plan may not include API access — contact Coassemble support to confirm.

</details>

<details>

<summary>Can I connect multiple Coassemble organizations to Coupler.io?</summary>

Yes, but each organization requires its own data flow with its own Organization Token. Once you have separate data flows running, use the **Append** transformation in Coupler.io to combine tracking data from all organizations into a single destination.

</details>

<details>

<summary>Why do I see null values in the completed_at field?</summary>

The `completed_at` field is only populated when a learner fully completes a course. Learners who are still in progress will have a null value there. Use the `progress` percentage and `status` field together to get a full picture of where each learner stands.

</details>

<details>

<summary>How often should I sync my Coassemble data?</summary>

It depends on the entity. For Trackings, daily or even hourly syncs make sense if you need up-to-date completion data. For Courses, weekly is usually enough unless you're frequently publishing new content. Screen types rarely change, so sync those on-demand only.

{% hint style="info" %}
See [Best Practices](https://docs.coupler.io/sources/category/other/coassemble/best-practices.md) for more guidance on scheduling and refresh frequency.
{% endhint %}

</details>

<details>

<summary>Can I use Coassemble data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your Trackings or Courses data directly to these tools to generate summaries, flag issues, or build natural-language reports without manual analysis.

</details>

<details>

<summary>Can I combine Coassemble data with data from other HR or LMS tools?</summary>

Yes. Coupler.io supports multiple sources in a single data flow. You can use the **Join** transformation to merge Coassemble tracking data with employee records from your HRIS, or use **Append** to combine Coassemble data with data from another LMS platform.

</details>

<details>

<summary>What's the difference between the Trackings and Courses entities?</summary>

Courses describes your training catalog — titles, descriptions, lesson counts, and course status. Trackings describes learner behavior — who started what, how far they've gotten, and whether they've completed it. For most reporting use cases, you'll want both, joined on the course ID.

{% hint style="info" %}
See [Data Overview](#coassemble-data-overview) for a full breakdown of fields available in each entity.
{% endhint %}

</details>

<details>

<summary>Why is my data flow returning no rows for Trackings?</summary>

This is usually because no learners have started any courses yet. Tracking records are only created when a learner opens and begins a course — unstarted assignments don't appear. If courses have been assigned but not started, the Trackings entity will be empty until learners engage.

{% hint style="info" %}
If you're seeing unexpected empty results, check [Common Issues](#coassemble-common-issues) for other possible causes.
{% endhint %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/other/coassemble.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
