New platform capability: Data Validation

monday Apps & Developers Announcements
, ,
1

We’re introducing a new platform capability: Data Validation :tada:

This feature will allow board owners to enforce rules on column inputs to improve data quality and prevent process errors.

The validation is enforced in the server side, so any item creation or item edit attempt that violates a validation rule rule will be rejected and an API error will be returned

What’s Included

Required Fields
Board owners will be able to mark specific columns as required. Users won’t be able to create or update items without filling them in. This will be enforced across all entry points: table, forms, API, automations, mobile, and more.

This feature will be gradually released from July 22 to all Pro and Enterprise accounts.

Conditional Rules
Owners will be able to define conditions like: “Status can only be set to Approved if Client is not empty.” These rules will apply during updates and will be enforced consistently across all flows.

Validation Rules
Owners will be able to set validation rules, for example - minimum value in a budget column
Validation and Conditional Rules will be rolled out in the end of Q3, in September 2025.

This feature will be gradually released, so you’ll see related errors crop up over time (for boards in which validation rules were defined by board owner).

What developers need to know and do:

  • The API will return an error if a column change does not satisfy a required field or rule.
  • We will release methods to query active data validation rules on a given column.

If your app creates or updates items or columns (via API or integrations), you should:

  • Handle validation errors returned by the server
  • Ensure your logic supports these new rules
  • Optionally surface validation issues in your UI to help users correct inputs

The first phase (July 2025) will include monday’s Work Management and Dev. CRM and monday Service will get the mentioned capabilities later on during H2 2025.

The technical part:

In order to be able to set column as required the user must have permissions to edit column settings on the board.

To set column as required go to the column menu → settings → set column as required.

Supported column type: text, longtext, color, numeric, date, dropdown, timeline, link, multiple_person, phone, email, location, country, rating,

(The graphQL for add_required_column is not validating the column type yet)

This feature is still in progress, we are opening it early for test accounts to allow developers enough time to adjust their apps. Please take into account that while the main flows are already supported some of the functionality is still WIP - see list below. In addition the feature is not 100% stable yet and we might need to close it in case of issues.

Supported:

  • Create item enforcement. When creating an item, via graphQL or UI, with missing values for required columns an indicative error will return.
  • Change column value - enforce validations.
  • Undo to action will always work - DON’T enforce validations
  • Restore item/s - DON’T enforce validations
  • Set/get required columns using graphQL.

Query:

Validations

Args: id (the board id), type (not required, the default is board)

Response:

validations: { required_column_ids : string[] }

Mutations:

add_required_column

Args: id (the board id), column_id, type (not required, the default is board)

Response:

required_column_ids: string[]
remove_required_column

Args: id (the board id), column_id, type (not required, the default is board)

Response: required_column_ids: string[]

In progress:

  • Server side enforcement for other flows expected behavior (not fully implemented yet):
  • Duplicate item/s - enforce validations
  • Move to item/s - enforce validations
  • Convert to subitems parent - enforce validations
  • Change group in the same board - DON’T enforce validations
  • UI support on the board is partial (on board, form, widgets)
  • Permissions - for now anyone with board edit columns permissions can set validations. When the feature is released we will add a dedicated permission level for setting required columns.

Important note:

This is a platform-level capability, so enforcement will apply across all interfaces, including marketplace apps.
Questions? Feel free to ask them here, or on our marketplace partners slack channel #data-validations

3

After hearing some feedback, I wanted to provide some additional information regarding this release. This is not currently listed as a part of the 2025-07 release as it was only released to early to some accounts for testing. When this is fully released, we will provide the full release notes and documentation for the feature.

In the meantime, we had some requests for how the errors will return. These are shared below:

{
  “data”: {
    “create_item”: null
  },
  “errors”: [
    {
      “message”: “data_validation_error”,
      “locations”: [
        {
          “line”: 1,
          “column”: 12
        }
      ],
      “path”: [
        “create_item”
      ],
      “extensions”: {
        “code”: “DATA_VALIDATIONS_ERROR”,
        “status_code”: 422,
        “error_data”: [
          {
            “itemId”: null,
            “columnIds”: [
              “XXXXXXXXXXXXXX”
            ],
            “message”: “Status 1 should not be empty”
          },
          {
            “itemId”: null,
            “columnIds”: [
              “XXXXXXXXXXXXX”
            ],
            “message”: “Text should not be empty”
          },
          {
            “itemId”: null,
            “columnIds”: [
              “numbers__1"
            ],
            “message”: “Numbers should not be empty”
          }
        ],
        “service”: “XXXXXXXX”
      }
    }
  ],
  “extensions”: {
    “request_id”: “XXXXXXXXXXXXXXXXXXX”
  }
}