monday.com boards support a variety of column types, each designed to store specific kinds of data. The API lets you read, filter, create, update, and clear most column types, though some are read-only or unsupported.

Each column type has a dedicated reference page (linked below) with examples for querying, filtering, and mutating values. The tables on this page show every column type, its implementation type, and the ColumnType enum value used in the API.

Reading column values

Column values are returned through the column_values field on items. Each column type maps to a specific GraphQL implementation type (e.g., StatusValue, TextValue, DropdownValue). Use inline fragments to access type-specific fields:

query {
  items(ids: [1234567890]) {
    column_values {
      ... on StatusValue {
        label
        index
      }
      ... on TextValue {
        text
        value
      }
    }
  }
}

All implementations share a common set of fields from the ColumnValue interface: id, text, type, and value. Type-specific fields (like label on StatusValue or url on LinkValue) are only available through inline fragments.

Supported columns

These column types support read operations through column_values, and most support write operations through change_simple_column_value or change_multiple_column_values. See each column's reference page for details on supported operations.

Read-only columns

These columns return values through the API but cannot be written to. Their data is auto-generated or derived from other columns.

Calculated columns

These columns are computed at render time and are not accessible through the column_values API.

Deprecated columns

These column types have been deprecated. They remain accessible via the API for backwards compatibility, but you should use the recommended replacement.

Other column types

The following column types exist in the API schema but have limited or no direct API support for reading and writing values.

Creating columns

You can create new columns on a board using the generic create_column mutation, which works for any column type. Pass the column type as the column_type argument.

For status and dropdown columns, the API also provides typed mutations with strongly typed settings:

• create_status_column — create a status column with label and color configuration
• create_dropdown_column — create a dropdown column with predefined options

Updating column values

You can update column values using one of two mutations:

• change_simple_column_value — accepts a string value for the column
• change_multiple_column_values — accepts a JSON object to update one or more columns at once

The expected format varies by column type. See each column's reference page for the specific value format and examples.

Filtering by column values

You can filter items by column values using items_page with query_params. Each column type supports a specific set of filter operators (e.g., any_of, contains_text, greater_than). See each column's reference page for supported operators and compare value formats.

query {
  boards(ids: [1234567890]) {
    items_page(
      query_params: {
        rules: [
          {
            column_id: "status"
            compare_value: [1]
            operator: any_of
          }
        ]
      }
    ) {
      items {
        id
        name
      }
    }
  }
}

Column type schema

You can retrieve the JSON schema for any column type's settings using the get_column_type_schema query. This returns the structure, validation rules, and available properties for a column's configuration.

query {
  get_column_type_schema(
    type: status
  )
}

The schema is useful for validating column settings programmatically, building dynamic UIs, or understanding the available configuration options for each column type.