> 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-updated.md).

# task.updated

The title, priority, due date, assignee, group, or entities of tasks changed. A bulk update arrives as one delivery listing every changed task.

### When it fires

The event fires when at least one of these task fields gets a new value, from a single edit in Kick or a bulk action over several tasks: `title`, `priority`, `dueDate`, `assigneeId`, `groupId`, or `entityIds`.

It is held back in these cases:

* A status change sends [`task.status_changed`](https://docs.kick.co/api/webhooks/task-status-changed.md) instead. An edit that changes the status and a field above sends both events.
* Changes to the description, and to fields outside the list above, send no event.
* Deleting a task group ungroups its tasks without sending this event. Their `groupId` becomes `null`.

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. The event is sent after the change is saved, to every organization with Platform API access that the workspace belongs to. A task internal to one organization is sent only to that organization.

### Payload

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

`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 the task is assigned to after the change                                                                   |
| `tasks[].changedFields` | string array | At least one of `title`, `priority`, `dueDate`, `assigneeId`, `groupId`, `entityIds`, named as on the task resource |

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

The payload names the changed fields but not their values. Read the tasks with [Retrieve a task](https://docs.kick.co/api/api-reference/tasks.md#retrieve-a-task), or pass the ids to [List tasks](https://docs.kick.co/api/api-reference/tasks.md#list-tasks) as `ids`. When `changedFields` holds `entityIds`, the task may have left an entity you filed it under, so re-file it under the new `entityIds`.

A task can change several times in a short time, and a retried delivery can arrive after a newer one. Read the task's current state 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-updated.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.
