ClickUp support

Last updated date:

Connect, reconnect, and troubleshoot ClickUp without sharing credentials or customer content through support channels.

1. Before you start

  • Generate a personal API token from a dedicated ClickUp admin or service account with only the intended native resource access.
  • Collect workspace, space, or list IDs when the connection should not scan every hierarchy visible to the token.
  • Review ClickUp plan-specific rate limits and the restricted-by-default Seedling audience policy.
  • Do not send ClickUp credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
ClickUp authenticationClickUp's current token authentication guidance.

2. Connect ClickUp

  1. In Seedling, open Connections and choose ClickUp.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the API token, optional account label, workspace IDs, space IDs, and list IDs; Seedling always calls the ClickUp API.
  4. Seedling verifies the token and selected hierarchy, then retains every source and filter on the exact workspace connection.
  5. Allow the first ClickUp synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

ClickUp API token rejected
Confirm the clickup api token is active, was entered without surrounding whitespace, and belongs to the intended ClickUp account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden ClickUp population as empty.
Wrong account or scope
Disconnect before retrying with the intended ClickUp identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the task belongs to a selected workspace, space, and list and remains visible to the token owner.
  2. Check private-space, private-list, guest, archived, and deleted-resource access in ClickUp.
  3. Allow provider throttling retries to finish without widening the configured resource allowlists.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement clickup api token for the same ClickUp account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old clickup api token in ClickUp.