Worktables icon

Worktables

Interact with Monday.com boards and items

Actions29

Overview

The node enables interaction with Monday.com boards, specifically allowing users to duplicate an existing board. This operation is useful when you want to create a new board based on the structure or content of an existing one without manually recreating it. Common scenarios include project management where similar workflows or templates are reused, or when creating backups or variants of boards for different teams or purposes.

For example, you can duplicate a board with all its pulses (items), or with pulses and their updates, or just duplicate the board's structure without any items. You can also choose whether to keep the subscribers from the original board in the duplicated version.

Properties

Name Meaning
Board Name The name to assign to the duplicated board.
Workspace Name or ID The workspace under which the board exists or will be duplicated into.
Board Name or ID The identifier of the board to duplicate.
Folder Name or ID The folder where the duplicated board should be placed.
Keep Subscribers Boolean flag indicating whether to retain the subscribers from the original board in the duplicated board.
Duplicate Type Specifies the duplication mode:
- Duplicate Board with Pulses
- Duplicate Board with Pulses and Updates
- Duplicate Board with Structure

Output

The output JSON contains details of the duplicated board, including at least its id and name. This allows subsequent workflow steps to reference the newly created board.

Example output structure:

{
  "board": {
    "id": "123456",
    "name": "Duplicated Board Name"
  }
}

Dependencies

  • Requires an API key credential for Monday.com (referred generically as an API authentication token).
  • The node makes HTTP POST requests to the Monday.com GraphQL API endpoint (https://api.monday.com/v2).
  • Proper permissions on the API token are necessary to perform board duplication and related operations.
  • The node expects valid workspace, board, and folder identifiers or names as inputs.

Troubleshooting

  • Missing Board ID: If the board ID to duplicate is not provided, the node throws an error "Board ID is required." Ensure this property is set correctly.
  • Missing API Key: If the API key credential is missing or invalid, the node throws "API Key not found." Verify that the API key is configured properly in n8n credentials.
  • Invalid Folder ID: If the folder ID is invalid or not accessible, the duplication may fail or place the board in an unintended location. Confirm folder selection.
  • Permission Issues: Insufficient permissions on the API token can cause failures. Make sure the token has rights to read and duplicate boards.
  • Duplicate Type Errors: Providing an unsupported duplication type value will cause errors. Use one of the predefined options.
  • Subscribers Handling: If keeping subscribers is enabled but some subscriber IDs are invalid or inaccessible, the operation might partially fail or skip subscribers.

Links and References

Discussion