manage_tasks

WRITE · 5 operations · may change data

Create, update, delete, complete and un-complete tasks and calendar events. There is no top-level mode to pick — a single fields.type decides what’s created.

manage_tasks({
  action: "create" | "update" | "delete" | "complete" | "uncomplete",
  ids?, fields?, confirm_token?
})

delete is an Always-confirm action: the first call returns needsConfirmation with a confirm_token; replay the identical call with that token to actually delete. ids (for update/delete/complete/uncomplete) must be the composite ids search_tasks itself returns (e.g. "12345-task"), not a bare number. fields.type (create only) decides what’s created — a different enum from anything at the top level of this tool:

`fields.type`	Required `fields`	Notes
`Other` / `Call` / `Email` / `Text`	`content`, `leadId`, `type`, `assignedRole` (`Agent`/`Assistant`), `endAt`	`endAt` is the deadline, not a range end. Optional: `startAt` (not used), `timeZoneCode`.
`Appointment`	`content`, `leadId`, `startAt`, `endAt`	Both ISO 8601 with a UTC offset, e.g. `2026-03-01T15:00:00-08:00`. Optional: `timeZoneCode`, `address`.

There is no title/subject/dueDate field — content and endAt are it. A missing required field is rejected before the call reaches the backend, naming exactly which one.

Get Started

Read Tools

Write Tools

Guides