Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
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 by specified fields. This is useful for workflows that need to aggregate or analyze communication and content stored in Basecamp projects.
Practical examples include:
- Automatically gathering all active comments from specific projects for reporting.
- Fetching archived documents for audit purposes.
- Retrieving trashed messages to review deleted content before permanent removal.
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 for the results. 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, creation date, status, and associated project information.
If the recordings include any binary data (e.g., file uploads), the node would provide this in a binary property, but based on the provided code and properties, the output focuses on JSON metadata about recordings.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically using the user's Basecamp account ID.
- No additional external dependencies are indicated beyond the Basecamp API and standard HTTP request handling.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect project bucket IDs may result in empty responses.
- Requesting unsupported recording types or statuses might return no data.
- Error messages:
- Authentication errors typically indicate invalid or expired API tokens; re-authenticate or update credentials.
- API rate limits may cause temporary failures; retry after some time.
- Malformed query parameters can lead to 400-series errors; verify property values conform to allowed options.
Links and References
- Basecamp API Documentation
- n8n documentation on creating custom nodes