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.
| Who | Agents can call this |
| REST | POST /v1/tasks |
| MCP tool | tasks_create |
| Writes | yes, send an Idempotency-Key |
| Area | Shop |
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
| Field | Type | Required |
|---|---|---|
shop_id | string (uuid) | yes |
title | string | yes |
job_id | string (uuid) | no |
assignee_id | string (uuid) | no |
note_id | string (uuid) | no |
due_on | string (date) | no |
due_at | string (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
| Code | Status | What to do |
|---|---|---|
invalid_input, invalid_token, rate_limited | Can happen on any call. See errors. |