Worktables icon

Worktables

Interact with Monday.com boards and items

Actions26

Overview

The node interacts with Monday.com boards and related entities via the Monday.com API. Specifically, for the Board resource and the List Boards operation, it retrieves a list of boards within a specified workspace. Users can filter the boards by kind (public, private, shareable, or all), state (active, archived, deleted, or all), and order them by creation date or last used date. The node supports pagination and limiting the number of results returned.

This operation is useful when you want to dynamically fetch and work with boards from a specific workspace in Monday.com, for example:

  • Automating reporting workflows that aggregate data across multiple boards.
  • Synchronizing board lists with other tools or databases.
  • Displaying available boards for user selection in subsequent workflow steps.

Properties

Name Meaning
Workspace Name or ID Select the workspace from which to list boards. You can choose from a dropdown list or specify an ID using an expression. This is required.
Board Kind Filter boards by their kind. Options are: All, Public, Private, Shareable. Default is All.
Order By Defines the order in which boards are retrieved. Options are: None, Name (creation date), Newest (last used date). The ordering is descending. Default is None.
State Filter boards by their state. Options are: All, Active, Archived, Deleted. Default is Active.
Limit Maximum number of boards to return. Minimum value is 1. If set to 0, all boards will be returned. Default is 50.

Output

The output is a JSON array where each element represents a board with the following fields:

  • id: The unique identifier of the board.
  • name: The name of the board.
  • boardKind: The kind of the board (public, private, shareable).
  • state: The current state of the board (active, archived, deleted).
  • description: Description text of the board.
  • itemsCount: Number of items on the board.
  • creator: Object containing the creator's id and name.
  • owners: Array of owner objects with id and name.
  • subscribers: Array of subscriber objects with id and name.
  • tags: Array of tag objects with id and name.
  • workspaceId: The ID of the workspace the board belongs to.
  • updatedAt: Timestamp of the last update.
  • url: URL link to the board.

Example output JSON snippet:

[
  {
    "id": 123456,
    "name": "Project Board",
    "boardKind": "public",
    "state": "active",
    "description": "Board for project management",
    "itemsCount": 42,
    "creator": { "id": 789, "name": "Alice" },
    "owners": [{ "id": 789, "name": "Alice" }],
    "subscribers": [{ "id": 101, "name": "Bob" }],
    "tags": [{ "id": 5, "name": "Urgent" }],
    "workspaceId": 555,
    "updatedAt": "2024-05-01T12:34:56Z",
    "url": "https://monday.com/boards/123456"
  }
]

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for Monday.com API access.
  • The node makes HTTP POST requests to the Monday.com GraphQL API endpoint at https://api.monday.com/v2.
  • The API key must have permissions to read boards in the specified workspace.
  • No additional environment variables or external services are required beyond the Monday.com API access.

Troubleshooting

  • API Key Not Found: The node throws an error if the API key credential is missing or invalid. Ensure the API key is correctly configured in n8n credentials.
  • Workspace ID Required: The workspace parameter is mandatory. Omitting it or providing an invalid ID will cause errors.
  • Rate Limits: Monday.com API has rate limits; requesting too many boards or making frequent calls may result in throttling.
  • Invalid Filters: Providing unsupported values for board kind, state, or order by may cause the API to reject the request.
  • Empty Results: If no boards match the filters, the output will be an empty array.
  • Pagination Handling: Setting limit to 0 returns all boards but may take longer and risk timeouts for large workspaces.

To resolve common errors:

  • Verify API key validity and permissions.
  • Confirm workspace ID exists and is accessible.
  • Use valid options for filtering parameters.
  • Adjust limit to reasonable values to avoid timeouts.

Links and References

Discussion