Tasks

The collection team's manual work (call, visit, review…), created by hand or by rule steps. complete completes a task; bulk-assign create and bulk-complete create assign an owner to or complete up to 100 at once.

Command	HTTP	Description
tasks list	GET /v1/tasks	List tasks
tasks create	POST /v1/tasks	Create task
tasks get	GET /v1/tasks/{id}	Get task
tasks update	PUT /v1/tasks/{id}	Update task
tasks delete	DELETE /v1/tasks/{id}	Delete task
tasks complete	POST /v1/tasks/{id}/complete	Complete task
tasks bulk-assign create	POST /v1/tasks/bulk-assign	Bulk-assign tasks
tasks bulk-complete create	POST /v1/tasks/bulk-complete	Bulk-complete tasks

Examples

--params carries query, path and header parameters (id, page, filters, X-Workspace-Id); --json carries the request body; --fields limits which fields come back — worth using on every list/get to save context. See Global flags for the full reference.

# High-priority pending tasks
kobana dunning tasks list \
  --params '{"status": "pending", "priority": "high"}' \
  --fields "id,title,task_type,assigned_to_id,due_at"

# Create a call task
kobana dunning tasks create \
  --json '{"title": "Ligar para negociar", "task_type": "call", "person_id": "PERSON_ID"}'

# Complete a task
kobana dunning tasks complete --params '{"id": "TASK_ID"}'

# Assign several tasks to an owner
kobana dunning tasks bulk-assign create \
  --json '{"ids": ["TASK_ID_1", "TASK_ID_2"], "assigned_to_id": "USER_ID"}'

Next steps

• Imports
• Schema introspection — every parameter this resource accepts.