You can now use the board_updates_only argument when querying the updates field inside a boards query. This argument filters the results to return only updates posted directly on the board, excluding item-level updates.
query {
board (ids: 1234567890) {
updates (limit: 50, board_updates_only: true) {
body
id
created_at
creator {
name
id
}
}
}
}We added a new argument to the create_update mutation:
original_creation_date: The update's original creation date. Useful in scenarios like account recovery where preserving the original creation date is necessary.mutation {
create_update (item_id: 9876543210, body: "This update will mention user 1234567890 on an item", mentions_list: [{id: 1234567890, type: User}], original_creation_date: "01-03-2025") {
id
}
}You can now filter replies queries by board IDs, pages, and creation time ranges using the following arguments:
board_idscreated_at_fromcreated_at_tolimitpagequery {
replies(board_ids: [1234567890], created_at_to: "2025-08-02", created_at_from: "2025-01-01") {
body
created_at
edited_at
creator {
id
name
}
}
}You can now update a folder's position, workspace, or product using the following new arguments on the update_folder mutation:
account_product_idpositionworkspace_idmutation {
update_folder (
folder_id: 1234567890,
name: "Updated folder name",
account_product_id: 54321,
position: {
object_id: "15",
object_type: Board,
is_after: false
}
) {
id
name
}
}You can now update a board's position, workspace, or product using the new update_board_hierarchy mutation.
mutation {
update_board_hierarchy(
board_id: 1234567890,
attributes: {
account_product_id: 54321
workspace_id: 12345
folder_id: 9876543210
position: {
object_id: "15",
object_type: Overview,
is_after: true
}
}
) {
success
}
}You can now set or update a board's default permissions using the new set_board_permissions mutation.
mutation {
set_board_permission (board_id: 1234567890, basic_role_name: viewer) {
edit_permissions
failed_actions
}
}We just completed a major overhaul of our developer community! 🥳
Come join us to ask and answer questions, network with other developers, submit feature requests, track product updates, register for events, sign up for new feature testing groups, and so much more!
Here's the new link 👉 https://developer-community.monday.com
You can now change the account product a workspace is in using the new account_product_id field on the update_workspace mutation.
mutation {
update_workspace (id: 1234567, attributes: { account_product_id: 98765, name:"Marketing team", description: "This workspace is for the marketing team." }) {
id
}
}You can now change an item's position on the same board using the new change_item_position mutation. The following example moves 1234567890 after item 9876543210.
mutation {
change_item_position (
item_id: 1234567890,
relative_to: 9876543210,
position_relative_method: after_at
) {
id
group {
id
}
}
}