Learn how to query monday.com board or item updates using the platform API
Updates are item or board-specific communication threads where teams can share notes, files, and key information. They help users collaborate across organizations, stay aligned, and communicate asynchronously, all within the context of their work.
Within an update, users can reply and react, attach files, pin important messages to the top, and see who has viewed the conversation. Many teams use updates as their main hub for ongoing communication in monday.com.
Queries
Get updates
- Required scope:
updates:read - Returns an array containing metadata about one or a collection of updates in reverse chronological order
- Can be queried directly at the root (returns all updates across an account) or can be nested inside a
boardsoritemsquery (returns updates from a specific board or item)
query {
updates(
limit: 50
to_date: "2025-06-04"
from_date: "2025-01-01"
) {
body
id
created_at
creator {
name
id
}
}
}Arguments
| Argument | Type | Description |
|---|---|---|
| board_updates_only | Boolean | Whether to only include board-level updates. Can only be used when nesting updates in a boards query. |
| from_date | String | Filters updates created on or after this date. Accepts ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:mm). Must be used together with the to_date argument, and only when querying updates directly at the root (not nested in a boards query). |
| ids | [ID!] | The specific ID(s) to return updates for. |
| limit | Int | The number of updates per page. The default is 25, and the maximum is 100. |
| page | Int | The page number to get. Starts at 1. |
| to_date | String | Filters updates created on or before this date. Accepts ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:mm). Must be used together with the from_date argument, and only when querying updates directly at the root (not nested in a boards query). |
Fields
| Field | Type | Description |
|---|---|---|
| assets | [Asset] | The update's assets/files. |
| body | String! | The update's HTML-formatted body. |
| created_at | Date | The update's creation date. |
| creator | User | The update's creator. |
| creator_id | String | The unique identifier of the update's creator. |
| edited_at | Date! | The date the update's body was last edited. |
| id | ID! | The update's unique identifier. |
| item | Item | The update's item. |
| item_id | String | The update's item ID. |
| likes | [Like!]! | The update's likes. |
| pinned_to_top | [UpdatePin!]! | The update's pinned to the top data. |
| replies | [Reply!] | The update's replies. |
| text_body | String | The update's text body. |
| updated_at | Date | The date the update was last edited. |
| viewers | [Watcher!]! | The update's viewers. |
Mutations
- Required scope:
updates:write
Create update
Creates and adds a new update to an item. Returns Update.
mutation {
create_update(
item_id: 9876543210
body: "This update will mention user 1234567890 on an item"
mentions_list: [
{
id: 1234567890
type: User
}
]
) {
id
}
}Arguments
| Argument | Type | Description |
|---|---|---|
| body | String! | The update's text. |
| item_id | ID | The item's unique identifier. You don't need to use this argument if you're replying to a post using parent_id. |
| mentions_list | [UpdateMention] | The user, team, or board to mention in an update. |
| original_creation_date | String | The update's original creation date. Follows DD-MM-YYYY format. |
| parent_id | ID | The parent updates's unique identifier. This can be used to create a reply to an update. |
Like update
Likes an update. Returns Update.
mutation {
like_update(update_id: 1234567890) {
id
}
}Arguments
| Argument | Type | Description |
|---|---|---|
| update_id | ID | The update's unique identifier. |
Unlike update
Unlikes an update. Returns Update.
mutation {
unlike_update(update_id: 1234567890) {
creator_id
item_id
}
}Arguments
| Argument | Type | Description |
|---|---|---|
| update_id | ID! | The update's unique identifier. |
Edit update
Edits an update. Returns Update.
mutation {
edit_update(
id: 1234567890
body: "The updated text!"
) {
creator_id
item_id
}
}Arguments
| Argument | Type | Description |
|---|---|---|
| body | String! | The update's new text. |
| id | ID! | The update's unique identifier. |
Pin to top
Pins an update to the top of an item. Returns Update.
mutation {
pin_to_top(
id: 1234567890
item_id: 9876543210
) {
creator_id
body
}
}Arguments
| Argument | Type | Description |
|---|---|---|
| id | ID! | The update's unique identifier. |
| item_id | ID | The item's unique identifier. |
Unpin from top
Unpins an update from the top of an item. Returns Update.
mutation {
unpin_from_top(
id: 1234567890
item_id: 9876543210
) {
creator_id
body
}
}Arguments
| Argument | Type | Description |
|---|---|---|
| id | ID! | The update's unique identifier. |
| item_id | ID | The item's unique identifier. |
Clear item updates
Clears all updates on a specific item, including replies and likes. Returns Update.
mutation {
clear_item_updates(item_id: 1234567890) {
id
}
}Arguments
| Arguments | Type | Description |
|---|---|---|
| item_id | ID! | The item's unique identifier. |
Delete update
Deletes an item's updates. Returns Update.
mutation {
delete_update(id: 1234567890) {
id
}
}Arguments
| Argument | Type | Description |
|---|---|---|
| id | ID! | The update's unique identifier. |
