Actions29
- Board Actions
- Item Actions
- Update Actions
- Team Actions
- User Actions
- Query Actions
Overview
This node integrates with Monday.com (referred to as "Worktables" in the code) and allows users to perform various operations on Monday.com resources such as boards, items, groups, updates, teams, and users via the Monday.com GraphQL API.
Specifically for the Item resource and the Get an Item operation, the node retrieves detailed information about a specific item by its ID. This includes the item's ID, name, creation and update timestamps, and all column values associated with the item.
Common scenarios where this node is beneficial:
- Fetching detailed data of a particular task or project item from Monday.com to use in workflows.
- Integrating Monday.com item details into other systems or automations.
- Using item data as input for conditional logic or further processing in n8n workflows.
Practical example:
- You have a Monday.com board tracking customer support tickets. When a new ticket is created or updated, you want to fetch the full details of that ticket (item) including custom fields and statuses to send notifications or update another system.
Properties
| Name | Meaning |
|---|---|
| Item ID | The unique identifier of the item to retrieve. Must be specified as a string or expression. |
Output
The output JSON contains the full details of the requested item, structured as follows:
{
"items": [
{
"id": "string", // The item's unique ID
"name": "string", // The item's name/title
"created_at": "string", // Timestamp when the item was created
"updated_at": "string", // Timestamp when the item was last updated
"column_values": [ // Array of column value objects for the item
{
"id": "string", // Column ID
"text": "string", // Text representation of the value
"value": "string" // Raw value (usually JSON string)
}
]
}
]
}
- The
column_valuesarray provides the values of all columns (custom fields) associated with the item. - The node returns the data wrapped inside an
itemsarray even though only one item is fetched.
Dependencies
- Requires an API key credential for Monday.com (referred to generically as "an API key credential").
- The node makes HTTP POST requests to the Monday.com GraphQL API endpoint:
https://api.monday.com/v2. - The API key must be provided in the Authorization header as a Bearer token.
- No additional external dependencies are required beyond standard n8n credentials and HTTP request capabilities.
Troubleshooting
Common issues
- Missing or invalid API key: The node throws an error if the API key credential is not found or invalid. Ensure the API key is correctly configured in n8n credentials.
- Invalid or missing Item ID: The operation requires a valid item ID. If omitted or incorrect, the API will return an error or empty results.
- API rate limits or network errors: Monday.com API may throttle requests or experience downtime. Handle retries or check API status if errors occur.
- Malformed GraphQL queries: Although generated internally, any manual query changes should follow GraphQL syntax strictly.
Common error messages
"API Key not found": Indicates the API key credential is missing or not loaded."Unsupported operation: getItem": Means the operation name is incorrect or not implemented."Item ID is required.": The required item ID parameter was not provided.- Errors returned from Monday.com API will typically include descriptive messages; review those for guidance.
Links and References
If you need summaries for other resources or operations, feel free to ask!