Currently, updating custom fields on an existing task requires one PUT request per field (PUT /task/{task_id}/field/{field_id}). For tasks with 10-15 custom fields, that's 10-15 sequential API calls to update a single task.

The gap:

Creating a task already supports a custom_fields array in one POST. Updating should work the same way.

Every comparable platform (Notion, Airtable, Monday, Jira) handles multi-field updates in a single request.

There is no workaround. Automations are rigid, the bulk bar only handles one field type at a time, and middleware (Latenode, Make, Zapier) still has to fire N individual calls to ClickUp's API under the hood.

Impact:

-Integrations and automations are slower and more fragile than they need to be

-Partial failures leave tasks in inconsistent states (5 of 12 fields updated, then a timeout)

-Rate limits hit faster when every field is a separate call

-AI agents (Brain, Super Agents) burn context window and response time making sequential calls that should be atomic

Requested behavior:

A single endpoint like PUT /task/{task_id}/fields (or extend the existing task update endpoint) that accepts an array of { field_id, value } objects and applies them atomically.

Precedent:

-ClickUp's own task creation endpoint already supports this pattern

-Notion: single PATCH to page properties

-Airtable: single PATCH with all fields

-Monday: one GraphQL mutation, multiple columns

-Jira: single PUT to /issue/{id}