Feature Requests

When creating a task, I have an error message that is not helping { "err": "Invalid Value, expected an object { add?: string[], rem?: string[] }", "ECODE": "FIELD_375" } FIELD_375 doesn't match anything : it's not a custom field ID, it's not a label, it's nowher to be found on the documentation. I would like to understand what field is problematic with an ID or a label in your API error message

https://www.anthropic.com/news/integrations The built-in AI are good, but we also need access to external services. Asana has already integrated, and I hope our more advanced ClickUp will not take long to wait �

When a task is archived/unarchived, trigger a webhook with this update

kms

A webhook has been established for task-related events such as task creation, task updates, and task comment postings. However, there is an issue where the webhook endpoint is being triggered multiple times upon task creation. I need guidance in resolving this issue. Thank you.

We need the ability to create Docs from saved templates using either: ClickUp Automations (e.g. “When folder is created → create Doc from template”) ClickUp API (e.g. POST /docs using template_id) This is essential for: Client onboarding (automated strategic briefs) SOPs and internal documentation Creative and marketing briefs Currently, we can do this manually, but automation support would significantly streamline workflows and ensure consistency across projects.

This would be helpful in creating custom external AI workflows that integrate with all tasks and the knowledgebase of the company

Related to https://api.clickup.com/api/v2/task/abcdef/comment API endpoint. Allow using markdown syntax (tables, h1, embedded images etc) while adding a comment to a task. It is possible to use markdown with markdown_content paragraph while creating a new task. I would expect the same behaviour for comments.

test

We currently use the API to integrate ClickUp with custom enterprise software systems and databases. Currently, the API actions have to be performed under a user account so all of these automated actions appear to be from a single user. It would be useful for the workspace owner to be able to generate an API Key where the actions are shown to be performed by an API Bot, similar to how automations show that they are performed by ClickBot.