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

You can use the updates query to retrieve updates data via the API.

• Required scope:updates:read
• Returns an array containing metadata about one or a collection of updates
• Can be queried directly at the root (returns all updates across an account) or can be nested inside a boards or items query (returns updates from a specific board or item)
• Updates are returned in reverse chronological order (newest ones first)

query {
  updates(
    limit: 50 
    to_date: "2025-06-04" 
    from_date: "2025-01-01"
	) {
    body
      id
      created_at
      creator {
        name
        id
    }
  }
}

Arguments

You can use the following arguments to reduce the number of results returned in your updates query.

Fields

You can use the following fields to specify what information your updates query will return. Some fields support their own subfields.

Mutations

The API allows you to create, update, and delete updates using the following mutations. These operations let you programmatically control an update's full lifecycle.

Create update

Required scope:updates:write

The create_update mutation creates and adds a new update to an item via the API. You can specify which fields to return in the mutation response.

mutation {
  create_update(
    item_id: 9876543210
    body: "This update will mention user 1234567890 on an item"
    mentions_list: [
      {
        id: 1234567890
        type: User
      }
    ]
  ) {
    id
  }
}

Arguments

You can use the following arguments to define the new update's characteristics.

Like update

Required scope:updates:write

The like_update mutation likes an update via the API. You can specify which fields to return in the mutation response.

mutation {
  like_update(update_id: 1234567890) {
    id
  }
}

Arguments

You can use the following argument to specify which update to like.

Unlike update

Required scope:updates:write

The unlike_update mutation unlikes an update via the API. You can specify which fields to return in the mutation response.

mutation {
  unlike_update(update_id: 1234567890) {
    creator_id
    item_id
  }
}

Arguments

You can use the following argument to specify which update to pin.

Edit update

Required scope:updates:write

The edit_update mutation edits an update via the API. You can specify which fields to return in the mutation response.

mutation {
  edit_update(
    id: 1234567890
    body: "The updated text!"
	) {
    creator_id
    item_id
  }
}

Arguments

You can use the following arguments to specify which update to edit.

Pin to top

Required scope:updates:write

The pin_to_top mutation pins an update to the top of an item via the API. You can specify which fields to return in the mutation response.

mutation {
  pin_to_top(
    id: 1234567890
    item_id: 9876543210
	) {
    creator_id
    body
  }
}

Arguments

You can use the following arguments to specify which update to pin.

Unpin from top

Required scope:updates:write

The unpin_from_top mutation unpins an update from the top of an item via the API. You can specify which fields to return in the mutation response.

mutation {
  unpin_from_top(
    id: 1234567890
    item_id: 9876543210
	) {
    creator_id
    body
  }
}

Arguments

You can use the following arguments to specify which update to unpin.

Clear item updates

Required scope:updates:write

The clear_item_updates mutation clears all updates on a specific item, including replies and likes, via the API. You can specify which fields to return in the mutation response.

mutation {
  clear_item_updates(item_id: 1234567890) {
    id
  }
}

Arguments

You can use the following argument to specify which items' updates to clear.

Delete update

Required scope:updates:write

The delete_update mutation deletes an item's updates via the API. You can specify which fields to return in the mutation response.

mutation {
  delete_update(id: 1234567890) {
    id
  }
}

Arguments

You can use the following argument to specify which updates to delete.