team_assignment_create
[REQUIRES APPROVAL] Delegates a task to a teammate (or yourself) as a new team_assignment; status is workflow-owned and always starts 'pending' — passing status yourself fails validation instead of being silently overridden. Accepts natural language for the common fields: task_name/task for title, due_date/due for due_at ('YYYY-MM-DD', epoch millis, 'today', 'tomorrow', or 'next '), and 'self'/'me'/'yourself' for assigned_to. assigned_to must already be a member of your tenant. NEXT: team_assignment_accept, then _start and _complete, drive the lifecycle from there.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| due | No | Alias of due_at (same accepted forms as due_date). | |
| task | No | Alias of title (same as task_name). | |
| title | No | ||
| due_at | No | ||
| status | No | ||
| due_date | No | Alias of due_at — "YYYY-MM-DD", "today", "tomorrow", or "next <weekday>" (epoch milliseconds also works — pass it via due_at directly instead). | |
| priority | No | ||
| task_name | No | Alias of title — the task's name in plain language. | |
| started_at | No | ||
| accepted_at | No | ||
| artifact_id | No | ||
| assigned_to | No | ||
| declined_at | No | ||
| description | No | ||
| photos_json | No | ||
| completed_at | No | ||
| reassigned_at | No | ||
| reassigned_by | No | ||
| attachment_key | No | ||
| decline_reason | No | ||
| attachment_name | No | ||
| attachment_type | No | ||
| previous_status | No | ||
| completion_notes | No | ||
| previous_assignee | No |