Short answer: Drop the "Monday.com → Update Monday.com Item Column" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Board ID board_id | string | Required | The Board ID assigned by Monday. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Item ID item_id | string | Required | The Item ID assigned by Monday. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Column ID column_id | string | Required | Column ID. Example: status |
Value (JSON) value | string | Required | Value (JSON). e.g. "{"label":"Done"}" |
{"board_id": "{{trigger.board_id}}","item_id": "{{trigger.item_id}}","column_id": "e.g. status","value": "{\"label\":\"Done\"}"}
{"data": {"change_column_value": {"id": "9876543210"}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.