@devries-cameron20 / composio Mirror · read-only
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 06:00 UTC

next
md 14 lines 1021 Bytes
Rendered Raw
1 ## ClickUp supports managed OAuth, custom OAuth, and API-key credentials
2
3 Use Composio-managed OAuth for the standard connection flow. Use a custom
4 ClickUp OAuth app or API-key credentials when you need greater control.
5 In newer SDK/API flows, use the v3 auth config nano ID (`ac_...`) rather than
6 older v1/v2 integration assumptions.
7
8 ## ClickUp custom OAuth should use the Composio callback URL registered in the ClickUp app
9
10 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.
11
12 ## ClickUp folders and tasks are supported through `CLICKUP_GET_FOLDERS` and `CLICKUP_GET_TASKS`
13
14 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, request that tool through the standard tool-request flow.