`new_task`

Add a task. Add a task to a department's board. Title up to 200 characters, done_when 1,000; skill: one start lists.

Where it is

Always listed: call it by its name.

Does it need a yes?

Runs at once, no yes card: it changes only the office's own working state, and nothing reaches anyone. Here: a task on the company's own board.

Inputs

Input	Type	Needed	About
`department`	string	yes	The department's id, e.g. sales.
`title`	string	yes
`done_when`	string	yes	How to tell it is done.
`next`	"ai" \| "you"	yes	Who moves next (you: the owner).
`skill`	string	no	e.g. discovery-call-prep. · format `^[a-z0-9][a-z0-9-]{0,59}$`
`kind`	"landing-page-live" \| "invoice-sent" \| "newsletter" \| "film-edit" \| "small-app" \| "social-post" \| "email-reply" \| "import" \| "routine" \| "other"	no	Without a skill: its kind.
`due_on`	string	no	The day it is due, in company time. A follow-up shows on Today from that day, e.g. 2026-10-24.
`request_key`	string	no	Same key, same task. · format `^[A-Za-z0-9][A-Za-z0-9:._-]{0,99}$`
`helper`	string	no	A helper's person:<id>. Settings lists them.
`run_id`	string	yes	The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "new_task",
  "arguments": {
    "department": "sales",
    "title": "Follow up with Ana",
    "done_when": "Ana has an answer",
    "next": "ai",
    "run_id": "the run_id from start"
  }
}

When it is refused

invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.
not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.
not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.
taken: Someone else holds it (another AI on that task). Pick another task.
stale: It changed since you read it. Read it again and use the new version.
failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.