tasks.create

Make a tracked task from a crew message or plain words: a title, and optionally the job, the worker it is for, the note it came from and when it is due (due_on is a day, 5 PM shop time; or due_at). Past due and still open, the worker gets one reminder email, then the owner is told once. Any worker on the shop can make one.

WhoAgents can call this
RESTPOST /v1/tasks
MCP tooltasks_create
Writesyes, send an Idempotency-Key
AreaShop

When to use it

Lead rules (requests.setLeadSettings, owner or office) decide what happens to a new request. With auto_reply on, Doing Work sends one first reply within a minute: a text only where the customer already agreed to texts or texted the shop, and the shop's own number is approved for business texting; otherwise an email; otherwise nothing.

What to tell the owner

Say what you did in plain words and what happens next.

Input

FieldTypeRequired
shop_idstring (uuid)yes
titlestringyes
job_idstring (uuid)no
assignee_idstring (uuid)no
note_idstring (uuid)no
due_onstring (date)no
due_atstring (date-time)no

Example

POST https://doingwork.work/v1/tasks
content-type: application/json
Idempotency-Key: 3f1c...

{
  "shop_id": "00000000-0000-4000-8000-000000000000",
  "title": "..."
}

Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.

Errors

CodeStatusWhat to do
invalid_input, invalid_token, rate_limitedCan happen on any call. See errors.