ClickUp integration

What it does

The ClickUp integration lets your agency drive your clients' ClickUp workspaces without leaving TaskJuice. Connect a workspace once and your workflows can work across the whole hierarchy (workspaces, spaces, folders, lists, and tasks), manage checklists, comments, tags, goals, custom fields, views, docs, chat, and time tracking, and react in real time to any of the 28 events ClickUp publishes.

Container fields are pickers, not text boxes. When a step needs a workspace, space, folder, or list, you choose it from a dropdown that loads live from the connected account, and each level filters by the one above it.

Connect a ClickUp account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose ClickUp and click Connect.
3. Sign in to the ClickUp account that owns the workspace you want to wire up, then choose which workspaces to authorize. ClickUp lets you approve one or several.
4. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

ClickUp has no OAuth scope system. The connection can reach whatever the authorizing user can reach, so connect an account whose access matches the work you intend to automate.

To revoke access, open your ClickUp profile, navigate to Apps, and remove the TaskJuice authorization.

Triggers

TaskJuice ships one trigger for every event ClickUp publishes, 28 in total. TaskJuice registers and maintains the workspace webhook for you when you publish a workflow.

• Tasks (13): created, updated, deleted, plus granular triggers for priority, status, assignee, due date, tag, and move changes, comment posted and updated, and time estimate and time tracked updates.
• Lists (3): created, updated, deleted.
• Folders (3): created, updated, deleted.
• Spaces (3): created, updated, deleted.
• Goals and key results (6): created, updated, deleted for each.

Every inbound delivery is authenticated by recomputing HMAC-SHA256 over the raw request body using the workspace webhook secret and comparing the hex digest against the X-Signature header ClickUp sends. Deliveries that fail the check are rejected before they reach your workflow.

These triggers deliver identifiers, not records. A ClickUp delivery carries the webhook_id, the event name, the id of the thing that changed, and a history_items array naming the fields that changed. It does not carry the task itself. Add a Get Task step on the incoming task_id to read the record, or filter on history_items to narrow the trigger without a fetch.

Actions

168 actions cover ClickUp's published API surface. The families are:

• Tasks: create, get, update, delete, list, filter across a workspace, merge, move to another list, create from a template, and manage task links and dependencies.
• Hierarchy: full create, read, update, and delete for spaces, folders, and lists, including folderless lists, creation from templates, and shared hierarchy.
• Comments: task, list, and threaded comments, with update and delete.
• Checklists: create, update, and delete checklists and their items.
• Custom fields: read the fields accessible at list, folder, space, or workspace level, and set or remove a value on a task.
• Tags: add and remove task tags, and manage space tags.
• Time tracking: create, read, update, and delete time entries, start and stop a running timer, read entry history, and manage time entry tags. The older per task time endpoints are also available for workspaces with existing legacy intervals.
• Goals: create, read, update, and delete goals and key results.
• Views: create and read views at workspace, space, folder, and list level, read the tasks in a view, and update or delete a view.
• Docs: search, read, and create docs and pages.
• Chat: create and read channels, direct messages, messages, replies, and reactions.
• Members and groups: read workspace members, seats, plan, and custom roles, and manage user groups, guests, and users.
• Attachments: upload to a task and read attachments on a parent entity.

Known limitations

• Rate limits are low on most plans. ClickUp allows 100 requests per minute per token on Free Forever, Unlimited, and Business, 1,000 on Business Plus, and 10,000 on Enterprise. A 429 is surfaced as a retryable error so the workflow backs off. Because the ceiling is low, prefer triggers over polling loops.
• Several families need a paid plan. Guest and user management answer 403 unless the workspace is on Enterprise. Time in Status needs a plan that includes it. The Docs API answers 403 on Free, including creating a doc. Adding a task to a second list requires the Tasks in Multiple Lists feature. Each affected action says so in its description.
• Chat is experimental. ClickUp describes its chat endpoints as experimental and subject to change, so those actions may move without notice. Chat reactions take a literal emoji character rather than a name.
• Some list filters are not exposed. ClickUp declares several task filters as repeated query parameters, which the action contract cannot express. Filter downstream instead. The affected actions name the omitted filters in their descriptions.
• Custom fields cannot be created through the API. ClickUp publishes read, set, and remove only, so create the field in ClickUp first and then set values from a workflow.
• Webhooks are scoped to one workspace. To listen across several workspaces, connect each one.
• A stale token can surface as a 404 on newer endpoints. The Docs and Chat endpoints resolve the workspace before checking the token, so an expired connection can read as "not found" there rather than as an authentication error. Reconnect the account if those actions start failing.