Tasks

The Tasks module lets agents and humans create, list, and complete operational follow-ups.

What it does

Tasks make agent-created next steps visible and accountable. Agents can create follow-ups, list open work, and complete tasks after a business action is done.

Task statuses:

• open
• completed
• canceled

Resource model

The tasks resource is tenant-owned and follows the shared app-plane fields:

Permissions

Use tasks:write to create or complete tasks and tasks:read to list tasks.

Recommended agent scopes for follow-up workflows:

crm:read
tasks:read
tasks:write
activity:write

Example workflow

Prompt:

Create a follow-up task for Jane Doe next Friday and log that it came from a pricing email.

Expected operations:

1. search_contacts
2. create_task
3. log_activity

Audit behavior

Task writes create audit events for create, complete, and status changes. A task completion should preserve:

• actor and source
• previous status
• new status
• linked resource
• request ID
• error status if completion failed

Task audit history is what lets a human see whether an agent merely suggested a task or actually changed workspace state.

MCP tools

{
  "title": "Follow up with Jane Doe",
  "related_resource_type": "contact",
  "related_resource_id": "con_123"
}

{
  "task": {
    "id": "task_123",
    "title": "Follow up with Jane Doe",
    "status": "open"
  },
  "request_id": "req_129"
}

{
  "status": "open",
  "limit": 25
}

{
  "tasks": [
    {
      "id": "task_123",
      "title": "Follow up with Jane Doe",
      "status": "open"
    }
  ],
  "request_id": "req_130"
}

{
  "task_id": "task_123",
  "completed_note": "Jane replied."
}

{
  "task": {
    "id": "task_123",
    "status": "completed"
  },
  "request_id": "req_131"
}

{
  "task_id": "task_123",
  "status": "completed",
  "completed_note": "Jane confirmed the next call."
}

{
  "task": {
    "id": "task_123",
    "status": "completed",
    "completed_note": "Jane confirmed the next call."
  },
  "request_id": "req_131"
}