Monday.com
Description
Section titled “Description”Integration with the Monday.com API, which is GraphQL, not REST. Every operation is a POST to the single endpoint https://api.monday.com/v2 carrying a { query, variables } body. The nodes build that query for you; the GraphQL Query node lets you write your own when you need something the other five do not cover.
Five nodes wrap the everyday item operations — create, read, update, delete and post an update — and the sixth is a raw GraphQL escape hatch.
Authentication is handled through the credentials module (service type monday). The requests also send the API-Version header with value 2024-10.
Operations
Section titled “Operations”Configuration
Section titled “Configuration”Each node exposes only the fields it needs. This is the combined list across the six nodes:
| Parameter | Type | Required | Description |
|---|---|---|---|
| credentials_id | credentials | Yes | Monday credential (provider monday) |
| board_id | text | Conditional | Numeric board id — Create Item and Update Item |
| group_id | text | No | Group id inside the board — Create Item |
| item_name | text | Conditional | Item name — Create Item |
| item_id | text | Conditional | Numeric item id — Get, Update, Delete and Add Update |
| column_values | json | Conditional | Column values as JSON, sent to Monday as a stringified JSON |
| body | textarea | Conditional | Update text — Add Update |
| query | textarea | Conditional | GraphQL query or mutation — GraphQL Query |
| variables | json | No | Operation variables — GraphQL Query |
Credentials
Section titled “Credentials”Service type: monday. Stored in the servicecredentials table.
- token: personal API token, generated in Monday under Avatar → Developers → My access tokens (or Admin → API). Required.
- timeout: request timeout in milliseconds (default: 20000). Optional.
The token travels in the Authorization header as it is, with no Bearer prefix — this is a Monday particularity. The Test button runs the query { me { name } } and returns the account name.
Column values
Section titled “Column values”column_values is the trickiest part of the Monday API: it must arrive as a stringified JSON, not as an object. You write it as normal JSON in the node and Floogos stringifies it before sending.
The keys are column ids, not the titles you see in the board, and the value shape depends on the column type:
{ "status": { "label": "Working on it" }, "date4": { "date": "2026-03-05" }, "person": { "personsAndTeams": [ { "id": 12345678, "kind": "person" } ] }, "numbers": "4200", "text": "Free text"}Output
Section titled “Output”{ "nextModule": null, "data": { "id": "987654321", "name": "Acme Ltd" }, "_meta": { "moduleVersion": "1.0.0", "success": true, "id": "987654321", "totalMs": 310 }}API Used
Section titled “API Used”- Monday.com GraphQL API — https://developer.monday.com/api-reference
- Endpoint:
POST https://api.monday.com/v2, API version2024-10 - Operations:
create_item,items,change_multiple_column_values,delete_item,create_update
- Board and item ids are numeric, and the GraphQL schema types them as
ID!. The nodes cast them to string before sending, so it is fine to feed them from a previous node. - Every text and id field accepts dynamic variables such as
{{data.item_id}}, including inside the JSON fields. - Transient failures (timeout, rate limit, 5xx and network errors) are retried automatically up to 3 times with exponential backoff, honouring
Retry-Afterand Monday’sretry_in_seconds. - Monday’s rate limiting is based on complexity, not on request count. Errors whose GraphQL code mentions complexity, minute or daily limits are treated as rate limits and retried.
- Authentication errors and validation errors — an invalid board, a column that does not exist, a bad argument — are not retried.
- Default request timeout is 20 seconds.
Related Nodes
Section titled “Related Nodes”- HubSpot and Salesforce — other CRM integrations.
- Jira, Asana, Trello and ClickUp — work-management integrations.
- Retry queue (DLQ) — how failed executions are retried.