The BlockEvent type now includes fields to support automation loops (iterators). These fields let you identify whether a block event is part of a loop and track its progress.

You can now query the monday.com developer documentation using AI via the ask_developer_docs query. It returns an AI-generated answer based on the apps documentation, along with a conversation_id you can use for follow-up queries.

query {
  ask_developer_docs(query: "How do I authenticate with the monday API?") {
    id
    question
    answer
    conversation_id
  }
}

You can now create, publish, delete, and query knowledge base articles via the API.

Queries

• articles — retrieve published articles by object ID, with optional workspace filtering and pagination
• article_blocks — paginate through an article's content blocks

query {
  articles(object_ids: ["12345"], limit: 10, page: 1) {
    id
    name
    privacy_kind
    blocks {
      id
      type
      content
    }
  }
}

Mutations

• create_article — create a new article in a workspace
• publish_article — publish a draft article with privacy and subscriber controls
• delete_article — delete an article

mutation {
  create_article(
    name: "Getting started guide"
    workspace_id: "123456"
  ) {
    object_id
    name
  }
}

mutation {
  publish_article(
    object_id: "789"
    privacy_kind: PUBLIC
  ) {
    object_id
    name
    state
  }
}

New fields have been added to support app features within the platform:

Folder

The same app_feature_slug field has also been added to GraphqlHierarchyObjectFolderItem (favorites folder items).

AppFeatureType

The API now supports AI agent attribution in two areas:

Reaction attribution

The Reaction type on updates includes two new fields to identify when a reaction was created by an AI agent on behalf of a user:

Agent as assignee kind

The Kind enum now includes agent as a value, allowing AI agents to appear as assignees alongside person and team.

New query_params filter on workspaces query

The workspaces query now accepts a query_params argument to filter workspaces by account product kind.

Supported product kinds: core, crm, forms, marketing, project_management, service, software, whiteboard.

query {
  workspaces(query_params: { account_product_kind: project_management }) {
    id
    name
  }
}

The Board type now includes two new fields:

query {
  boards(ids: [1234567890]) {
    id
    name
    created_from_board_id
    folder {
      id
      name
    }
  }
}

The AggregateGroupByResult type no longer exposes separate typed fields for group-by values. The following fields have been removed:

• value_string (String)
• value_int (Int)
• value_float (Float)
• value_boolean (Boolean)

These are replaced by a single unified field:

"""The value of the group by result. Can be an integer, float, string, or boolean."""
value: JSON

If your integration references value_string, value_int, value_float, or value_boolean, you must migrate to the value field and handle type coercion on the client side.

You can now update a board’s item terminology (item nickname) via the update_board mutation.

By setting the board_attribute to item_nickname, you can programmatically control the singular and plural labels used for items on a board.

mutation {
  update_board(
    board_id: 1234567890
    board_attribute: item_nickname
    new_value: "{\"preset_type\":\"other\",\"singular\":\"Task\",\"plural\":\"Tasks\"}"
  )
}

Enterprise customers can now manage departments via the API. This release introduces new queries and mutations for creating, updating, assigning, and deleting departments.

Queries

• departments
• department field added to users

Mutations

• create_department
• assign_department_members
• assign_department_owner
• update_department
• clear_users_department
• unassign_department_owners
• delete_department