Overview
This node interacts with the Monday.com API to retrieve all items from a specified board. It is designed to fetch multiple items up to a user-defined limit, making it useful for workflows that need to process or analyze bulk data from a Monday.com board.
Common scenarios include:
- Exporting all tasks or items from a project board for reporting.
- Synchronizing Monday.com board items with other systems.
- Performing batch operations or analytics on all items within a board.
For example, a user might configure this node to get all items from their "Marketing Campaign" board, limiting the results to 100 items, and then pass this data to another node for further processing or visualization.
Properties
| Name | Meaning |
|---|---|
| Board | The specific Monday.com board from which to retrieve items. Options are dynamically loaded from available boards. |
| Limit | The maximum number of items to return from the selected board. Defaults to 50. |
Output
The output is an array of JSON objects, each representing an item retrieved from the specified Monday.com board. Each item object contains detailed information including item ID, name, and associated column values.
Example structure of one output item (simplified):
{
"id": "12345",
"name": "Item Name",
"column_values": [
{
"id": "status",
"text": "Done",
"value": "{\"index\":1}"
},
...
]
}
If binary data were involved, it would be summarized here, but this node outputs only JSON data representing Monday.com items.
Dependencies
- Requires an active Monday.com API key credential configured in n8n.
- Uses Monday.com API version "2023-10" by default.
- Relies on internal utility classes/methods to communicate with the Monday.com API.
Troubleshooting
Common issues:
- Invalid or expired API token: The node will fail to authenticate with Monday.com.
- Specifying a board that the API key does not have access to will result in errors.
- Requesting a very high limit may cause performance issues or API rate limiting.
Error messages:
- Authentication errors typically indicate invalid credentials; verify and update the API key.
- Permission errors suggest insufficient access rights to the chosen board.
- JSON parsing errors are unlikely here since the node handles response parsing internally, but malformed input parameters could cause failures.
To resolve these, ensure the API key is valid and has appropriate permissions, select accessible boards, and keep the limit reasonable.