FAQ

Where do I find my Coassemble API tokens?

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.

Can I connect multiple Coassemble organizations to Coupler.io?

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.

Why do I see null values in the completed_at field?

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.

How often should I sync my Coassemble data?

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.

See Best Practices for more guidance on scheduling and refresh frequency.

Can I use Coassemble data with AI tools?

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.

Can I combine Coassemble data with data from other HR or LMS tools?

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.

What's the difference between the Trackings and Courses entities?

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.

See Data Overview for a full breakdown of fields available in each entity.

Why is my data flow returning no rows for Trackings?

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.

If you're seeing unexpected empty results, check Common Issues for other possible causes.