Tasks

Two task records matter#

Matruno has both MatterTask and HumanTask models. A matter task is the workflow execution unit created for a matter workflow. A human task is a person-facing checkpoint created when attorney feedback, action, approval, or information is required.

Matter tasks#

Matter tasks are created when a legal workflow launches. They are tied to a matter workflow, workflow step, workspace, status, dependencies, and completion metadata. Completing or approving a matter task can advance downstream tasks.

GET /api/v1/tasks
GET /api/v1/tasks/{task_id}
PATCH /api/v1/tasks/{task_id}
POST /api/v1/tasks/{task_id}/approve
POST /api/v1/tasks/{task_id}/retry

Human tasks#

Human tasks store assigned user, task type, priority, due date, instructions, user feedback, structured response data, and submitted timestamps. They are the right surface for attorney-review checkpoints and structured feedback that a moderator or workflow step must consume.

GET /api/v1/matters/{matter_reference_id}/feedback-tasks
GET /api/v1/matters/{matter_reference_id}/tasks/{task_id}
POST /api/v1/matters/{matter_reference_id}/tasks/{task_id}/submit-feedback
GET /api/v1/tasks/all

Pending review and approval tasks should align with legal lifecycle stages under_review and awaiting_approval. See Legal Matter Lifecycle.

Use tasks for execution, not awareness#

If a record only informs a user, use notes, notifications, or audit events. Use tasks when there is a clear owner, expected legal outcome, workflow reason, and completion signal.