Reference · built on requestConnectorWork & ticket management

ClickUp

Tasks, Lists, Folders, Spaces, and Custom Fields from ClickUp Workspaces through the ClickUp API and webhooks.

Request accessPricing ↗

About

ClickUp is a work management platform arranged as Workspace, Space, Folder, List, and task. API v2 calls the Workspace a team in its paths, such as /v2/team/{team_id}/space, while v3 paths say workspace. A task carries status, priority, assignees, tags, due dates, points, and Custom Fields, and some fields apply only to a task's custom task type.

Through Fibric, an operator watches task events on a List or Space, reads the task and its Custom Fields, and proposes a status change, a reassignment, a Custom Field value, or a comment for your approval. Every approved change carries its own record: what changed, why, and the way to undo it.

This is a reference listing. It documents what Fibric would read from ClickUp and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Tasks in a List through GET /v2/list/{list_id}/task, filtered by statuses, assignees, tags, due dates, and custom_fields, 100 per page
  • Tasks across a Workspace that match criteria through Get Filtered Team Tasks
  • A single task with its applicable custom_fields, attachments, and time_spent through Get Task
  • A List's Custom Fields, including applied_objects that scope a field to a custom task type
  • Webhook events such as taskCreated, taskStatusUpdated, taskAssigneeUpdated, taskDueDateUpdated, taskMoved, and taskCommentPosted, with before and after history_items
  • List, Folder, Space, and Goal events, filtered to one space_id, folder_id, list_id, or task_id per webhook

Proposed actions

  • Target capability: propose a task update through PUT /v2/task/{task_id}: status, priority, due_date, assignees, parent, or archived
  • Target capability: propose a Custom Field value through POST /v2/task/{task_id}/field/{field_id}
  • Target capability: propose a comment through POST /v2/task/{task_id}/comment with notify_all set
  • Target capability: propose a new task through Create Task in a chosen List

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Follow up on open actions

    The operator lists tasks past their due_date across the Workspace, proposes a reminder comment on each, and suggests a new date the owner can accept or change.

    With Action Follow-up

  • Check a cleaning round

    Cleaning tasks on a List carry a location Custom Field. The operator reads status changes as they arrive and proposes a re-check task when a room is skipped.

    With Cleaning Verification

  • Turn a unit

    Unit turn steps are subtasks under one parent. The operator watches taskStatusUpdated events and proposes the next assignee and due date when a step completes.

    With Unit Turn

  • Track inspections coming due

    A date Custom Field marks the next inspection. The operator proposes a task in the inspection List ahead of the date and comments with what to bring.

    With Inspection Due

Requirements

  • A ClickUp Workspace and a user whose token can see the Spaces and Lists the operator reads
  • For OAuth apps, a client_id and client_secret, with the user authorizing one or more Workspaces
  • A webhook created through POST /v2/team/{team_id}/webhook, which is tied to the creating user
  • An HTTPS endpoint that answers within 7 seconds and checks the X-Signature HMAC
Authentication
A personal API token beginning with pk_ in the Authorization header, or an OAuth 2.0 app using the Authorization Code grant and a Bearer access token.

Limits

  • Rate limits per token depend on plan: 100 requests per minute on Free Forever, Unlimited, and Business, 1,000 on Business Plus, 10,000 on Enterprise
  • A 429 response carries X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers
  • Update Task cannot set Custom Fields; each value goes through Set Custom Field Value, and a field not enabled for the task type returns 400
  • A failing webhook is retried five times per event and the event is then dropped; at a fail_count of 100 the webhook is suspended

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request ClickUp ↗

Questions and answers

Why do some endpoints say team when the UI says Workspace?
API v2 kept the older word. In /v2 paths, team means the Workspace that contains Spaces, Folders, Lists, and tasks. API v3 paths say workspace, for example /v3/workspaces/{workspace_id}/docs. Groups, in both versions, means user groups inside a Workspace.
How does ClickUp sign a webhook?
Each webhook has its own secret, returned when the webhook is created. ClickUp computes an HMAC of the request body with it and sends the hex digest in the X-Signature header. The connector recomputes the digest and rejects a mismatch. A 401 from your endpoint suspends the webhook at once.
Do personal tokens expire?
No. Personal tokens are generated in Settings under Apps, begin with pk_, and never expire. OAuth access tokens currently do not expire either, though ClickUp notes this is subject to change. Rate limits apply per token.
Ask about ClickUp

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with ClickUp through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy