Instance · Tasks
Tasks Overview
Last updated 1 November 2026
To-dos for you and your team, linked to contacts, companies or opportunities.
Tasks are to-dos for you or your team. Each task has a name, a due date and the person it is assigned to. It can be linked to a contact, a company or a pipeline opportunity. Mark a task complete when it is done, and reopen it if it is not.
Where to find tasks
| Screen | What it shows |
|---|---|
| My Tasks | Tasks assigned to you |
| All Tasks | Every task on the instance |
| A contact or company | The tasks linked to that record |
| An opportunity | The tasks linked to that deal |
What a task holds
| Field | Meaning |
|---|---|
| Task name | What needs doing. Required |
| Description | More detail |
| Due date | When it is due |
| Assignee | Who does it |
| Linked record | One contact, company or opportunity |
| Status | Open or completed. Completing records who did it and when |
From code
The CRM API manages tasks at /crm/api/v2/tasks. Mark one done with PATCH /crm/api/v2/tasks/:uuid/complete, and reopen it with /open; neither needs a body.
POST /crm/api/v2/tasks
{
"task_name": "Follow up with prospect",
"description": "Send a follow-up email and schedule a call.",
"assignee.uuid": "ADMIN_UUID",
"contact.uuid": "CONTACT_UUID",
"due_date": "2026-11-15"
}The list accepts filters such as status, assignee_uuid, a due date range, and one of contact_uuid, company_uuid or opportunity_uuid. Any other parameter is refused with a 400 that names it.
The Dashboard's CRM tab counts overdue tasks and shows how many are due today.
Note
Fields and filters come from the CRM tasks reference in the Insites Logic Engine; the screens from the CRM module routes. The docs instance has no tasks, so none was read.
Common mistakes
- Linking a task to two records. A task links to one contact, company or opportunity.
- Passing two relation filters on the list. Only one is allowed.
- Deleting a finished task. Complete it, so the record shows who did it.