> 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/faq.md).

# 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](/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](/sources/category/other/coassemble/data-overview.md) 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](/sources/category/other/coassemble/common-issues.md) 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.