Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "ClickUp" |
| 4 | description: "Public support knowledge for ClickUp." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "clickup" |
| 10 | --- |
| 11 | # ClickUp |
| 12 | |
| 13 | |
| 14 | ## ClickUp supports managed OAuth, custom OAuth, and API-key credentials |
| 15 | |
| 16 | Use Composio-managed OAuth for the standard connection flow. Use a custom |
| 17 | ClickUp OAuth app or API-key credentials when the customer needs greater control. |
| 18 | In newer SDK/API flows, use the v3 auth config nano ID (`ac_...`) rather than |
| 19 | older v1/v2 integration assumptions. |
| 20 | |
| 21 | ## ClickUp custom OAuth should use the Composio callback URL registered in the ClickUp app |
| 22 | |
| 23 | For ClickUp custom OAuth, make sure the redirect URL in the ClickUp app matches the callback shown by the current Composio auth-config flow. A mismatch between the current auth config and an old callback copied from a legacy SDK example is a common cause of setup failure. |
| 24 | |
| 25 | ## ClickUp folders and tasks are supported through `CLICKUP_GET_FOLDERS` and `CLICKUP_GET_TASKS` |
| 26 | |
| 27 | For ClickUp folder/task-list workflows, use supported tools such as `CLICKUP_GET_FOLDERS` and `CLICKUP_GET_TASKS`. If a more specific ClickUp endpoint is missing, route it as a tool request. |