Skip to main content
PATCH
Update Action
action_id is matched directly against the tasks table’s id — the route does not additionally filter by deal_id in the path, so any task id belonging to the caller’s org (not just ones on this specific deal) can be patched through this path. Row-level security still scopes it to the caller’s organization.

Auth

Requires a CRM manage scope and an active organization on the token. Any *:manage scope qualifies — in practice contacts:manage, deals:manage, companies:manage, or activities:manage.

Response

The updated tasks row.

Errors

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

deal_id
string
required

The deal's id; not used to scope the lookup — action_id alone determines the task.

action_id
string
required

The task's id, matched directly against the tasks table (not additionally scoped to this deal).

Body

application/json
text
string | null

New task description.

due_date
string | null

New due date, YYYY-MM-DD.

priority
string | null

New priority: high, medium, or low.

assignee_id
string | null

Reassign the task to this user id.

is_completed
boolean | null

Mark the task complete/incomplete; setting true stamps completed_at.

Response

Successful Response