Public API

I am using Claude to add time entries for tasks via the MCP, it says it cant add tags to the time entries becuae the MCP doesnt have the option available. It requires manual tagging, which makes using the MCP pointless for time entries.

It would be nice to have a API endpoint that would return all list or even workspace automations. Something that would return the trigger_id, auto_id and the name of the automation. For teams who are using a lot of automations it is painful to trace back a webhook call and find the CU automation that triggered the webhook. To be able to pull a list of all the automations would also be helpful in cataloging them.

I need to be able to use the internal API to extract the history of a task as it is displayed on the web. After some research, I found that this functionality already exists, but it is not exposed via the public API and can be extracted from the internal web API.

Use Case I'm developing MKiTFlow, a Figma plugin designed for creative agencies in the DACH region (Germany, Austria, Switzerland). The plugin integrates with ClickUp via n8n middleware to streamline the workflow between design tools and project management. Current Problem Creative agencies need to automatically set cover images for ClickUp tasks when assets are created or updated in Figma. Currently, there is no public API endpoint to programmatically set or update task cover images. The only way to set a cover image is through the ClickUp UI, which breaks automation workflows and requires manual intervention. Technical Requirements We need an API endpoint (similar to the internal frontend endpoint) that allows: Setting a cover image for a task using an attachment ID or filename Updating cover image position (x, y coordinates) Setting cover image color/overlay options Removing a cover image Example payload structure (based on internal frontend API): { "coverimage": "attachment-id-or-filename.png", "cover_image_color": "none", "cover_position_x": 0, "cover_position_y": 0 } Business Impact Automation: Enables fully automated workflows between design tools (Figma) and project management (ClickUp) Efficiency: Saves creative agencies significant time by eliminating manual cover image setup Consistency: Ensures all tasks have proper visual representation in Board View Scalability: Allows agencies to manage hundreds of tasks with proper visual assets Current Workarounds (Insufficient) Manual UI interaction: Users must manually set cover images after attachment upload - breaks automation First attachment rule: Board View shows first image as cover, but this is unreliable and can't be controlled programmatically Internal frontend API: Exists but requires browser session cookies, not suitable for server-side integrations There was already a feature request for this functionality: https://feedback.clickup.com/public-api/p/api-set-cover-image-pin

Ship an official ClickUp CLI as a deterministic alternative to MCP for agent workflows Problem We are building AI-driven workflows where agents run locally or in CI and need a tool surface that is: deterministic and cheap at runtime self-describing (so agents do not guess capabilities) stable across time (versioned contracts) MCP introduces overhead and token cost due to tool discovery and repeated schema/context exchange. We want a CLI-first interface that is always up to date and can be invoked by agents and automation systems. Request Please ship an official ClickUp CLI that wraps core ClickUp APIs and Automation Webhooks, with the following requirements: Help-first, machine-readable contracts clickup --help and clickup <cmd> --help must be complete and structured include input flags, examples, output schemas, and exit codes JSON by default All commands output strict JSON by default (--human optional) Stable schemas with versioning Stable exit codes 0 success 2 needs_input/validation error 3 blocked/permission/auth/rate limit 4 failed/unexpected Authentication OAuth device flow (ideal), plus optional support for personal tokens for power users Clear scoping to a workspace Core commands (v1) tasks get|search|create|update comments create|list lists get|search webhooks create|test (or automation webhook helpers) docs get|search (if feasible) Safety controls --dry-run to show mutations without applying explicit confirmation flag for destructive operations Auto-update / version pinning ability to force update before run (agent-friendly) ability to pin versions for CI reproducibility Why this matters This enables a “ClickUp as coordination layer” architecture where: ClickUp is the UI + state machine external agents/CLIs do deterministic work in codebases updates are written back to ClickUp reliably This is lower cost and higher control than MCP-style tool calling for many teams. Related Automation webhooks already exist and work well; a CLI would complement them as the execution surface.

Firts of all love the official Clickup MCP server. Our SDLC workflow has been trasnformed with it. One issue we seeing is it uses 34K tokens and that's roughly 17% of claude's 200K context window. Any optimisation that can be done ? Screenshot is from Claude code's "/context" command.

Enable user to add header to the webhook for better security control The Automation webhook can add header but i cannot control what it return. it always return a standard list of data. https://developer.clickup.com/docs/automationwebhookpayload however, if i create webhook myself, i cannot add header on it. It makes it less secure and cannot be used for integration

It would be nice to access the inbox and new reminders via the API in the future.

Hello, I saw that there's the possibility to update/delete a custom field value from ClickUp API, but there's no chance to edit/update the options of a dropdown. That's my use case: I have another platform with its own list of users, that increase on a daily base I have a ClickUp list, with a custom field that holds the user to whom the task is related I wish that the custom field was a dropdown, restricting the access only to the existing users, but cannot mantain it manually whenerever a new user is added on the other platform

Description: Currently, while task descriptions support Markdown formatting through the API, long text Custom Fields do not. Implementing Markdown support for these fields would allow for consistent rich text formatting across tasks and Custom Fields, enhancing data presentation and user experience. ​I am working on replicating Azure DevOps' commit history view within ClickUp tasks for my team. To achieve this, I'm using a combination of Webhooks and the ClickUp REST API. Implementing Markdown support for long text Custom Fields via the API would greatly assist in this endeavor. Thanks!