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

# task.commented

A message was posted on a task's thread, by a user, by Kick, or through the Platform API.

### When it fires

The event fires once for each message posted on a task's thread:

* A user posts a message in Kick, on the main timeline or as a reply in a sub-thread.
* Kick posts a message on the task.
* A message is posted with [Post a task message](https://docs.kick.co/api/api-reference/tasks.md#post-a-task-message). Your own messages reach your endpoint too.

It is held back in these cases:

* The description written when a task is created is part of the task, not a message, and sends no event.
* Activity entries, such as the record of a field change, are not messages and send no event.

The event is sent after the message is saved, to every organization with Platform API access that the workspace belongs to. An internal message, visible only to one organization, is sent only to that organization. So is a message on a task internal to one organization.

### Payload

```json
{
  "event": "task.commented",
  "version": 1,
  "occurredAt": 1761746400,
  "payload": {
    "workspaceId": "8d3a1b52-9f1d-4a7e-b0a1-2c5d6e7f8a90",
    "tasks": [
      {
        "taskId": "0f6e2b9a-4c1d-4e8f-a3b7-5d9c1e2f4a68",
        "entityIds": ["b6c4d2e1-7a3f-4c8b-9e0d-1f2a3b4c5d6e"],
        "commentId": "7c1d3e5f-9a2b-4c6d-8e0f-1a3b5c7d9e2f",
        "authorId": "4e2a6c8b-1d3f-4a5c-9b7e-0f2d4a6c8e1b",
        "content": "Uploaded the September statements."
      }
    ]
  }
}
```

`payload` carries:

| Field               | Type         | Notes                                                                                                                                                |
| ------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| `workspaceId`       | uuid         | Workspace the task belongs to                                                                                                                        |
| `tasks`             | array        | Always one item: the task the message was posted on                                                                                                  |
| `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[].commentId` | uuid         | The message's `id` on [List task messages](https://docs.kick.co/api/api-reference/tasks.md#list-task-messages)                                       |
| `tasks[].authorId`  | uuid or null | User who posted the message, as on [Users](https://docs.kick.co/api/api-reference/users.md). `null` for messages from Kick and from the Platform API |
| `tasks[].content`   | string       | Message text in plain text, one line per paragraph or list item                                                                                      |

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

To tell your own messages apart from people's replies, check `authorId`: messages you post through the API arrive with `null`. Compare `commentId` with the id returned by [Post a task message](https://docs.kick.co/api/api-reference/tasks.md#post-a-task-message) to skip them exactly.


---

# 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-commented.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.
