Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
The node interacts with the Basecamp API to retrieve event data associated with a specific project and recording. The "Get Events" operation under the "Event" resource fetches events related to a given project (referred to as a bucket) and a particular recording within that project.
This node is useful in scenarios where users want to monitor or analyze activity logs, changes, or updates (events) tied to specific recordings in their Basecamp projects. For example, it can be used to track all events for a meeting recording or a project milestone, enabling automation workflows that respond to these events.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) from which to retrieve events. Used in the API path. |
| Recording ID | The numeric ID of the recording within the project for which to get events. Used in the API path. |
| Return All Results | Boolean flag indicating whether to return all available events or limit the number of results. |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the events retrieved from the Basecamp API for the specified project and recording. The structure typically includes an array of event objects, each containing details such as event type, timestamp, associated user, and other metadata relevant to the event.
If "Return Full Response" is enabled, the output will include the entire HTTP response object, including status code and headers, allowing more detailed inspection of the API response.
The node does not output binary data.
Dependencies
- Requires an active connection to the Basecamp API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is constructed using the user's Basecamp account ID.
- Pagination support is included to handle multiple pages of event data if "Return All Results" is enabled.
Troubleshooting
Common Issues:
- Invalid or missing Project ID or Recording ID will result in API errors; ensure these IDs are correct and exist in your Basecamp account.
- Authentication failures due to invalid or expired API tokens.
- Pagination may fail if the API response headers do not include expected pagination links.
Error Messages:
- Unauthorized or 401 errors indicate issues with API credentials; verify and refresh your API key/token.
- 404 Not Found errors suggest the specified project or recording does not exist or is inaccessible.
- Rate limiting errors may occur if too many requests are made in a short period; implement delays or retries as needed.
Links and References
- Basecamp API Documentation
- Basecamp Event Resource (for detailed event object structure and usage)