Worktables icon

Worktables

Interact with Monday.com boards and items

Actions26

Overview

The node interacts with Monday.com boards and their related entities via the Monday.com API. Specifically, for the Board resource and the List Board Activity Logs operation, it retrieves activity logs of a specified board within an optional date range.

This operation is useful for tracking changes, user actions, or events on a Monday.com board over time. For example, you might use it to audit who made updates, what kind of changes occurred, or monitor board usage patterns.

Practical scenarios include:

  • Monitoring team activity on a project board.
  • Auditing changes for compliance or review.
  • Triggering workflows based on specific board events logged in the activity logs.

Properties

Name Meaning
Workspace Name or ID Select the workspace containing the board. You can choose from a list or specify an ID via expression. This is required.
Board Name or ID Select the specific Monday.com board to retrieve activity logs from. Choose from the list or specify an ID via expression. This is required.
From (Optional) The start date/time from which to retrieve activity logs. Format: ISO 8601 datetime.
To (Optional) The end date/time up to which to retrieve activity logs. Format: ISO 8601 datetime.

Output

The output JSON contains the activity logs of the specified board within the given date range. Each activity log entry includes:

  • id: Unique identifier of the activity log entry.
  • user_id: Identifier of the user who performed the action.
  • entity: The entity affected by the activity (e.g., item, group).
  • event: The type of event or action performed.
  • data: Additional data related to the event, typically in JSON format.
  • created_at: Timestamp when the activity occurred.

The output is structured as an array of these activity log objects under the board's activity_logs field.

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.
  • Proper configuration of the API key credential in n8n is necessary.
  • The workspace and board IDs must be valid and accessible by the provided API key.

Troubleshooting

  • API Key Not Found: If the API key credential is missing or invalid, the node will throw an error. Ensure the API key is correctly configured in n8n credentials.
  • Board ID Required: Omitting the board ID will cause an error. Always specify a valid board ID.
  • Invalid Date Format: The "From" and "To" properties expect ISO 8601 datetime strings. Incorrect formats may lead to no results or errors.
  • Permission Issues: The API key must have sufficient permissions to read board activity logs; otherwise, the request may fail.
  • Empty Results: If no activity logs exist in the specified date range, the output will be empty. Adjust the date range accordingly.

Links and References

Discussion