Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node interacts with the Basecamp API to retrieve recordings of various types such as comments, documents, messages, and more. Specifically, the "Get Recordings" operation fetches a list of recordings filtered by type, project buckets, status, and sorted according to specified criteria.
Common scenarios for this node include:
- Extracting all active comments or messages from specific projects for reporting or analysis.
- Retrieving archived or trashed recordings for audit or cleanup purposes.
- Sorting recordings by creation or update date to process the most recent items first.
For example, a user might use this node to get all active "Comment" recordings from certain projects, sorted by creation date descending, to display recent feedback in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Type | Type of recording to retrieve. Options: Comment, Document, Message, Question Answer, Schedule Entry, Todo, Todolist, Upload, Vault. |
| Bucket | Single or comma-separated list of project IDs to filter recordings by specific projects. |
| Status | Status of the recordings to fetch. Options: Active, Archived, Trashed. |
| Sort | Field to sort the results by. Options: Created At, Updated At. |
| Direction | Sort direction. Options: Asc (ascending), Desc (descending). |
Output
The node outputs JSON data containing an array of recordings matching the query parameters. Each recording object includes details relevant to its type, such as content, timestamps, status, and associated project information.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API base URL constructed dynamically using the authenticated user's Basecamp account ID.
- No additional external dependencies are required beyond the Basecamp API access.
Troubleshooting
- Authentication errors: Ensure that the API key or OAuth2 credentials are correctly configured and have sufficient permissions to access recordings.
- Empty results: Verify that the selected type, bucket IDs, and status filters match existing recordings in the Basecamp account.
- Invalid bucket IDs: Confirm that project IDs provided in the Bucket property are correct and accessible.
- API rate limits: If many requests are made in a short time, the Basecamp API may throttle requests; implement retry logic or reduce request frequency.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Node (for understanding API calls)