Actions119
- 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
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Event → Get Events
AI-generatedOverview
This node operation retrieves events from a specified project (bucket) and recording in Basecamp. It is useful for workflows that need to fetch event data related to specific projects and recordings, such as monitoring project activities or integrating event data into other systems.
Use Case Examples
- Fetch all events for a given project and recording to analyze project activity.
- Retrieve a limited number of events to display recent updates in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) used in the API endpoint path to specify which project's events to retrieve. |
| Recording ID | The ID of the recording used in the API endpoint path to specify which recording's events to retrieve. |
| Return All Results | Whether to return all event results or only up to a given limit. Useful for controlling pagination and data volume. |
| Return Full Response | Whether to return the full HTTP response including status code, headers, and body instead of only the response body. |
Output
JSON
id- The unique identifier of the event.content- The content or description of the event.created_at- The timestamp when the event was created.updated_at- The timestamp when the event was last updated.project_id- The ID of the project (bucket) the event belongs to.recording_id- The ID of the recording the event is associated with.
Dependencies
- Basecamp API access with OAuth2 credentials
Troubleshooting
- Ensure the Project ID and Recording ID are correct and exist in Basecamp to avoid 404 errors.
- Check API rate limits and pagination settings if not all events are returned when 'Return All Results' is enabled.
- Verify OAuth2 credentials are valid and have necessary permissions to access event data.
Links
- Basecamp Node Documentation - Official documentation for the Basecamp node in n8n, including usage and configuration details.