> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/api/webhooks/task-status-changed.md).

# task.status\_changed

The status of tasks changed, by a user or by Kick. A bulk status change arrives as one delivery listing every task with its previous status.

### When it fires

The event fires when a task's `status` gets a new value:

* A user changes the status of one task, or of several at once with a bulk action, in Kick.
* Kick changes the status on its own, for example when it completes a task once the work the task tracks is done.

One action over several tasks sends one delivery listing all of them, and more than 100 tasks are split into several deliveries of up to 100 each.

### Payload

```json
{
  "event": "task.status_changed",
  "version": 1,
  "occurredAt": 1761746400,
  "payload": {
    "workspaceId": "8d3a1b52-9f1d-4a7e-b0a1-2c5d6e7f8a90",
    "tasks": [
      {
        "taskId": "0f6e2b9a-4c1d-4e8f-a3b7-5d9c1e2f4a68",
        "entityIds": ["b6c4d2e1-7a3f-4c8b-9e0d-1f2a3b4c5d6e"],
        "status": "done",
        "previousStatus": "in_progress"
      }
    ]
  }
}
```

`payload` carries:

| Field                    | Type       | Notes                                                                       |
| ------------------------ | ---------- | --------------------------------------------------------------------------- |
| `workspaceId`            | uuid       | Workspace the tasks belong to                                               |
| `tasks`                  | array      | 1 to 100 items, one per changed task                                        |
| `tasks[].taskId`         | uuid       | The task's `id` on [Tasks](https://docs.kick.co/api/api-reference/tasks.md) |
| `tasks[].entityIds`      | uuid array | Entities of the workspace the task is assigned to                           |
| `tasks[].status`         | string     | Status after the change: `todo`, `in_progress`, `done`, or `cancelled`      |
| `tasks[].previousStatus` | string     | Status before the change                                                    |

The fields around it are the same on every event. See [The event envelope](https://docs.kick.co/api/webhooks.md#the-event-envelope).

### Handling it

Switch on `status`. When a task reaches `done`, read it with [Retrieve a task](https://docs.kick.co/api/api-reference/tasks.md#retrieve-a-task) to get `completedById` and `completedAt`. When a task leaves `done`, those two fields are cleared.

A task can change status several times in a short time, and a retried delivery can arrive after a newer one. Compare `occurredAt` with the last event you applied for the task, or read its current `status`, rather than applying events in arrival order.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/api/webhooks/task-status-changed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
