Worktables icon

Worktables

Interact with Monday.com boards and items
Join our community

Actions126

Overview

This node interacts with Monday.com boards to list activity logs for a specified board. It allows users to retrieve detailed activity logs filtered by date range, item IDs, column IDs, group IDs, and user IDs. The node supports pagination and limits the number of results returned, making it useful for auditing changes, tracking user actions, and monitoring board activity over time.

Use Case Examples

  1. Retrieve all activity logs for a project management board within the last month to audit changes.
  2. Filter activity logs by specific item IDs to monitor updates on key tasks.
  3. Get activity logs filtered by user IDs to track contributions of team members.

Properties

Name Meaning
Board The Monday.com board from which to retrieve activity logs. This is a required field and can be selected from a list or specified by ID.
From The start date from which to retrieve activity logs. Optional filter to limit logs to those created after this date.
To The end date up to which to retrieve activity logs. Optional filter to limit logs to those created before this date.
Item IDs Comma-separated list of item IDs to filter the activity logs. Only logs related to these items will be returned.
Column IDs Comma-separated list of column IDs to filter the activity logs. Only logs related to these columns will be returned.
Group IDs Comma-separated list of group IDs to filter the activity logs. Only logs related to these groups will be returned.
User IDs List of user IDs to filter the activity logs. Only logs generated by these users will be returned.
Limit Maximum number of activity log results to return. If set to 0, all logs will be returned, which may take longer for large boards.

Output

JSON

  • data
    • boards
      * 0
      * activity_logs - Array of activity log entries for the specified board, each containing details such as id, user_id, entity, event, data, and created_at.

Dependencies

  • Monday.com API key credential for authentication

Troubleshooting

  • Ensure the API key credential is correctly configured and has sufficient permissions to access the board and activity logs.
  • Verify that the board ID is valid and accessible by the API key user.
  • If filtering by item, column, group, or user IDs, ensure the IDs are correctly formatted and exist on the board.
  • Large boards with many activity logs may cause timeouts or long response times; consider using date range filters and limits to reduce data volume.
  • Common error messages include 'API Key not found' if credentials are missing, and 'Board ID is required' if the board parameter is not provided.

Links

Discussion