Short answer: Drop the "Monday.com → Get Monday.com Item" 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 |
|---|---|---|---|
Item ID item_id | string | Required | Item ID. Example: 9876543210 |
{"item_id": "e.g. 9876543210"}
{"data": {"items": [{"id": "9876543210","name": "Feature request","board": {"id": "1234567890","name": "Sprint Board"},"group": {"id": "new_group","title": "This Sprint"},"created_at": "2025-01-10T08:00:00Z","updated_at": "2025-01-15T12:00:00Z","column_values": [{"id": "status","text": "Working on it","type": "color","value": "{\"index\":1}"},{"id": "date4","text": "2025-06-30","type": "date","value": "{\"date\":\"2025-06-30\"}"}]}]}}
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.