Tasks
Create and manage tasks (action items, follow-ups, to-dos)
Tasks are action items that can be assigned to users and linked to other records. Clarify automatically creates tasks from meeting action items, but you can also create them via the API.
Fields
| Field | Type | Description |
|---|---|---|
title | string | Task title (required) |
description | object | Rich text body (BlockNote JSON format) |
status | string | To Do, In Progress, Done, or Canceled |
priority | string | Urgent, High, Medium, or Low |
due_date | date | Due date in YYYY-MM-DD format |
assignee_id | string | User ID of the assignee |
Tasks also support relationship fields to link them to other records — see relationships.
| Relationship | Field | Description |
|---|---|---|
| Person | person_id | Associated contact |
| Company | company_id | Associated company |
| Deal | deal_id | Associated deal |
| Meeting | meeting_id | Meeting this task came from |
Create a task
POST /objects/task/records
{
"data": {
"type": "task",
"attributes": {
"title": "Send proposal to Acme Corp",
"status": "To Do",
"priority": "High",
"due_date": "2024-04-01",
"assignee_id": "usr_01HX9Z2K3M4N5P6Q7R8S9T0U"
}
}
}Tasks don't have a unique field for upsert matching — every POST creates a new record.
Update a task
PATCH /objects/task/records/{id}
{
"data": {
"type": "task",
"attributes": {
"status": "Done"
}
}
}Link a task to a record
Set the relationship field when creating or updating:
{
"data": {
"type": "task",
"attributes": {
"title": "Follow up after discovery call",
"status": "To Do",
"priority": "Medium",
"person_id": "per_01HX9Z2K3M4N5P6Q7R8S9T0U",
"deal_id": "deal_01HX9Z2K3M4N5P6Q7R8S9T0V"
}
}
}List tasks
GET /objects/task/resources
Returns a paginated list of tasks. Supports the same filtering and sorting as other record types — see search and filter.
Common filters:
# Open tasks assigned to a user
GET /objects/task/resources?filter[status][In]=To Do,In Progress&filter[assignee_id][Equals]=usr_01HX...
# Overdue tasks
GET /objects/task/resources?filter[due_date][LessThan]=2024-04-01&filter[status][In]=To Do,In ProgressBulk operations
Tasks support the same bulk create, update, and delete endpoints as other record types — see records for details. Use object type task in the path:
POST /objects/task/records/bulk— bulk create (max 25)PATCH /objects/task/records— bulk updateDELETE /objects/task/records— bulk delete