Worktables icon

Worktables

Interact with Monday.com boards and items

Actions26

Overview

The "Add Board Subscribers" operation in the Worktables node allows users to add subscribers—both individual users and teams—to a specific board within a workspace on Monday.com. This operation supports assigning subscribers as either owners or regular subscribers, enabling fine-grained control over board access and notifications.

This node is beneficial when automating team collaboration workflows, such as:

  • Automatically adding project members to a new or existing board.
  • Managing subscriber roles programmatically based on team changes.
  • Ensuring relevant stakeholders receive updates by subscribing them to boards.

Example use case: When a new project board is created, automatically add the project manager as an owner subscriber and the rest of the team as regular subscribers to keep everyone informed.

Properties

Name Meaning
Workspace Name or ID Select the workspace containing the target board. Choose from a dropdown list or specify an ID via expression.
Board Name or ID Select the Monday board to which subscribers will be added. Choose from a dropdown list or specify an ID via expression.
User Subscribers A collection of users to add as subscribers. For each user, specify:
- User Name or ID: Select or specify the user.
- Is Owner: Boolean indicating if the user should be added as an owner (true) or subscriber (false).
Team Subscribers A collection of teams to add as subscribers. For each team, specify:
- Team Name or ID: Select or specify the team.
- Is Owner: Boolean indicating if the team should be added as an owner (true) or subscriber (false).

Output

The output JSON contains details about the added subscribers grouped by category:

  • ownerUsers: Result data for users added as owners.
  • subscriberUsers: Result data for users added as regular subscribers.
  • ownerTeams: Result data for teams added as owners.
  • subscriberTeams: Result data for teams added as regular subscribers.
  • boardId: The ID of the board to which subscribers were added.

Each group contains the response from Monday.com's API showing the IDs and names of the entities successfully added.

Dependencies

  • Requires an API key credential for Monday.com with permissions to manage boards and subscribers.
  • The node makes HTTP POST requests to the Monday.com GraphQL API endpoint: https://api.monday.com/v2.
  • Proper workspace and board IDs must be provided or selected.
  • User and team lists are dynamically loaded via helper methods that query Monday.com for available users and teams.

Troubleshooting

  • API Key Not Found: If the API key credential is missing or invalid, the node throws an error. Ensure the API key is correctly configured in n8n credentials.
  • Board ID Required: The operation requires a valid board ID. Omitting this parameter results in an error.
  • Invalid User or Team IDs: Specifying non-existent or unauthorized user/team IDs may cause the API call to fail or silently ignore those entries.
  • Permission Issues: The API key must have sufficient permissions to add subscribers; otherwise, mutations will fail.
  • Empty Subscriber Lists: If no users or teams are specified, no action is taken for that category.
  • GraphQL Errors: Malformed queries or invalid parameters can cause errors. Review the mutation structure if issues arise.

Links and References

Summary of execute() logic for "Add Board Subscribers"

  1. Retrieve required parameters: board ID, user subscribers, and team subscribers.
  2. Validate presence of board ID and API key.
  3. For user subscribers:
    • Separate users into owners and regular subscribers based on the isOwner flag.
    • Send separate GraphQL mutations to add owners and subscribers.
  4. For team subscribers:
    • Similarly separate teams into owners and subscribers.
    • Send separate GraphQL mutations to add owner teams and subscriber teams.
  5. Collect responses from all mutations.
  6. Return a JSON object summarizing the additions under keys: ownerUsers, subscriberUsers, ownerTeams, subscriberTeams, and boardId.

This approach ensures clear role assignment and efficient batch processing of subscribers.

Discussion