tasks

Create task

Open one manual work item for a human. With conversation_sid the thread records a task_created pill, person_sid is denormed from its primary link, and the thread turns to needs_you when the task is due today, earlier, or undated; without it the task is standalone and shows on no inbox surface yet. An agent caller puts the context bundle in body. No dedup: every call inserts a row. NOT for the agent's own next move, which is a plan step, and not for automated sequence steps.

Contract:

  • MCP tool create_task, registry package mcp.unibox/tasks, mount unibox.inbox.
  • Operation create, response envelope create.
  • Flags: none.
post/api/tasks

Request

  • Base URL
    https://beta.getsales.io/unibox/v1
  • Auth
    HTTP bearer and API key in header Team-SID

Request body

titlestring required

One line stating the work, 1..255 chars. This is what the human reads in the Tasks view.

bodystring nullable

Free text detail. An agent caller puts the context bundle here: reason, the qualification facts, the trigger - enough to act without re-reading the thread.

conversation_sidstring nullable

Thread to anchor the task to (ub_cv_…). Omit for a standalone task, which renders on no inbox surface yet.

due_atstring nullable

ISO 8601 UTC deadline; omit for undated. Due today or earlier (and undated too) surfaces the thread as needs_you right away.

expires_atstring nullable

ISO 8601 UTC, after now (422 otherwise): still open then, the sweep cancels the task and it reads as expired. Omit for a month ahead (the default, as for every task the product opens); null for a task that never expires.

assignee_user_sidstring nullable

User to own the work (us_mb_…, 18 chars). No server-side default: omit it and the task is unassigned.

Response

create success envelope.

successtrue required
operation'create' required
already_existsboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.