Actions29
- Board Actions
- Item Actions
- Update Actions
- Team Actions
- User Actions
- Query Actions
Overview
The node "Worktables" integrates with Monday.com to perform various operations on boards, items, groups, updates, teams, and users. 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 that have occurred on a Monday.com board over time. For example, a project manager might use this to audit who made changes to tasks or when certain activities happened on a board.
Practical Example
- Retrieve all activity logs from a specific Monday.com board between January 1, 2024, and February 1, 2024, to review team member interactions.
- Use the logs to trigger notifications or automate follow-up actions based on specific events recorded in the activity logs.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | Select the workspace containing the board. Can be chosen from a list or specified via expression. |
| Board Name or ID | Select the Monday.com board to retrieve activity logs from. Can be chosen from a list or expression. |
| From | (Optional) Start date/time to filter activity logs from. |
| To | (Optional) End date/time to filter activity logs up to. |
Output
The output JSON contains the raw response from Monday.com's API for the activity logs query. The structure includes:
id: Unique identifier of the activity log entry.user_id: ID 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 a JSON object with details.created_at: Timestamp when the activity occurred.
Example snippet of output JSON:
{
"boards": [
{
"activity_logs": [
{
"id": "123456",
"user_id": "78910",
"entity": "item",
"event": "update_column_value",
"data": { /* event-specific details */ },
"created_at": "2024-01-15T12:34:56Z"
}
]
}
]
}
No binary data output is involved in this operation.
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 configuration of the API key credential in n8n is necessary for authentication.
Troubleshooting
- API Key Not Found: If the API key credential is missing or invalid, the node will throw an error indicating the absence of the API key. Ensure the API key is correctly configured in n8n credentials.
- Board ID Required: The operation requires a valid board ID. If not provided, the node throws an error. Make sure to select or specify a valid board.
- Date Format Issues: The "From" and "To" properties expect ISO 8601 date-time strings. Incorrect formats may cause the API request to fail or return no results.
- Empty Results: If no activity logs are returned, verify the board ID and date range. Also, check if there has been any activity during the specified period.
- API Rate Limits: Excessive requests may hit Monday.com's rate limits. Implement retries or reduce request frequency if encountering rate limit errors.
Links and References
- Monday.com API Documentation - Activity Logs
- n8n Expressions Documentation
- Monday.com GraphQL API Reference
If you need further details about other operations or resources, feel free to ask!