# FAQ

<details>

<summary>Where do I find my ClickUp API token?</summary>

In ClickUp, click your **avatar** in the bottom-left corner, go to **Settings**, then scroll down to **Apps**. Your personal API token is listed there — click **Generate** if you haven't created one yet, or copy the existing token.

</details>

<details>

<summary>Why am I only seeing list names, not the tasks inside them?</summary>

The **Lists** entity in Coupler.io returns list-level metadata — the list name, ID, and settings — not the tasks inside. To get task data, add the **Tasks** entity to your data flow.

</details>

<details>

<summary>Can I export custom fields from ClickUp?</summary>

Yes. Add the **List Custom Fields** or **Team Custom Fields** entity to your data flow. Custom field values also appear as separate columns in the Tasks export. If you recently added new custom fields in ClickUp, re-run the data flow to pick them up.

</details>

<details>

<summary>Why doesn't my data flow return all my tasks?</summary>

Two common reasons: first, closed tasks are excluded by default — enable **Include closed tasks** in Advanced settings. Second, if you're running many entities at once, some API calls may fail and return partial data. Try splitting entities across separate data flows.

</details>

<details>

<summary>Why are deactivated team members missing from time tracking exports?</summary>

ClickUp's API does not return time tracking entries for deactivated users. This applies even to historical entries logged before the user was deactivated. Unfortunately, this is a ClickUp API limitation that cannot be resolved through Coupler.io settings.

</details>

<details>

<summary>Can I combine ClickUp data from multiple workspaces?</summary>

Yes. Create a separate data flow for each workspace (using the API token of a user in that workspace), then use the **Append** transformation in Coupler.io to combine them into a single dataset in your destination.

</details>

<details>

<summary>Should tasks and time trackings go into the same table in BigQuery?</summary>

No — they have different schemas and should be stored in separate tables. Use a Join transformation in Coupler.io if you want to combine them, or reference them with separate queries/views in BigQuery. Appending them into the same table will cause schema conflicts.

</details>

<details>

<summary>Can I send ClickUp data to AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. This lets you query your ClickUp task or time tracking data conversationally — useful for generating status summaries or identifying blockers.

</details>

<details>

<summary>Why does my data flow run successfully but show no data?</summary>

This usually means the API token you used doesn't have access to the spaces or tasks you're trying to export. ClickUp respects workspace permissions — private spaces and tasks you're not a member of won't appear. Make sure the token belongs to a user with the appropriate access level.

</details>

{% hint style="info" %}
For a full list of available fields and metric combinations, see the [Data Overview](https://docs.coupler.io/sources/category/project-management/clickup-api/data-overview) article. For connection errors and partial data issues, check [Common Issues](https://docs.coupler.io/sources/category/project-management/clickup-api/common-issues).
{% endhint %}