Worktables

Interact with Monday.com boards and items

Actions26

Overview

This node operation updates the column values of a specific item on a Monday.com board. It allows users to modify multiple columns of an existing item or subitem by specifying new values for each column. This is useful in scenarios where you want to automate updates to project tasks, status changes, or any other data tracked in Monday.com boards without manual intervention.

For example, you can use this node to:

Automatically update the status and priority columns of a task item when certain conditions are met.
Change due dates or assignees of items based on external triggers.
Modify subitems' details dynamically as part of a workflow.

Properties

Name	Meaning
Workspace Name or ID	Select the workspace containing the board.
Board Name or ID	Select the Monday.com board where the item exists.
Item Name or ID	Select the item whose column values you want to update.
Is Subitem	Boolean flag indicating whether the target is a subitem (true) or a regular item (false).
Subitem Name Or ID	If updating a subitem, select the specific subitem to update.
Column Values	A collection of column-value pairs specifying which columns to update and their new values.

The Column Values property supports multiple entries, each requiring:

Column Name or ID: The identifier of the column to update.
New Value: The new value to set for that column, provided as a string.

Output

The output JSON contains the response from the Monday.com API after attempting to update the item’s column values. Typically, it includes the updated item's ID confirming the mutation was successful.

Example output structure:

{
  "data": {
    "change_multiple_column_values": {
      "id": "123456789"
    }
  }
}

No binary data is produced by this operation.

Dependencies

Requires an API key credential for Monday.com with appropriate permissions to read and write board items.
The node makes HTTP POST requests to the Monday.com GraphQL API endpoint at https://api.monday.com/v2.
Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

API Key Not Found: The node will throw an error if the API key credential is missing or invalid. Ensure the credential is configured correctly.
Missing Required Parameters: Errors occur if required fields like workspace, board, or item IDs are not provided.
Invalid Column Values Format: The column values must be formatted as a JSON object string mapping column IDs to new values. Incorrect formatting may cause API errors.
Subitem Handling: When updating a subitem, ensure the subitem ID is correct and that the "Is Subitem" flag is enabled; otherwise, the update will fail.
Permission Issues: The API key must have sufficient permissions to update items on the specified board.