tasks.update

Change a task's title, job, worker or due time (due_on or due_at; null clears it). A new due time re-arms the one reminder. The owner, office, the worker it is for or the person who made it can change it.


Who	Agents can call this
REST	`POST /v1/tasks/update`
MCP tool	`tasks_update`
Writes	yes, send an Idempotency-Key
Area	Shop

When to use it

Lead rules (requests.setLeadSettings, owner or office) decide what happens to a new request. With auto_reply on, Doing Work sends one first reply within a minute: a text only where the customer already agreed to texts or texted the shop, and the shop's own number is approved for business texting; otherwise an email; otherwise nothing.

What to tell the owner

Say what you did in plain words and what happens next.

Input

Field	Type	Required
`task_id`	string (uuid)	yes
`title`	string	no
`job_id`	['string', 'null', ' ', '(', 'u', 'u', 'i', 'd', ')']	no
`assignee_id`	['string', 'null', ' ', '(', 'u', 'u', 'i', 'd', ')']	no
`due_on`	['string', 'null', ' ', '(', 'd', 'a', 't', 'e', ')']	no
`due_at`	['string', 'null', ' ', '(', 'd', 'a', 't', 'e', '-', 't', 'i', 'm', 'e', ')']	no

Example

POST https://doingwork.work/v1/tasks/update
content-type: application/json
Idempotency-Key: 3f1c...

{
  "task_id": "00000000-0000-4000-8000-000000000000"
}

Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.

Errors

Code	Status	What to do
`invalid_input`, `invalid_token`, `rate_limited`		Can happen on any call. See errors.