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 recordings of a specified type. It is designed to fetch recording data filtered by project(s), status, and sorted by a chosen field and direction. This node is useful for users who want to programmatically access various types of recordings (such as comments or other recorded items) from their Basecamp projects, enabling automation of reporting, auditing, or integration workflows.
Practical examples include:
- Fetching all active comment recordings from specific projects to analyze team communication.
- Retrieving recordings sorted by creation date to monitor recent activity.
- Automating the extraction of recordings for archival or further processing in other systems.
Properties
| Name | Meaning |
|---|---|
| Recording Type | The type of recording to retrieve. Example: "Comment". |
| Projects Filter | Single or comma-separated list of project IDs to filter recordings. Defaults to all visible projects. |
| Status | The status of recordings to retrieve. Example values: "active". |
| Sort Field | The field by which to sort the results. Default is "created_at". |
| Sort Direction | The direction of sorting: "asc" (ascending) or "desc" (descending). |
| Return All Results | Boolean flag indicating whether to return all available results or limit to a default count. |
| 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 retrieved recordings matching the specified filters and sorting. The structure typically includes an array of recording objects with properties depending on the recording type requested (e.g., comments will have text, author, timestamps).
If the "Return Full Response" option is enabled, the output includes the entire HTTP response object containing status code, headers, and body.
This node does not output binary data.
Dependencies
- Requires an authenticated connection to the Basecamp API using OAuth2 credentials.
- The node depends on the Basecamp account ID configured in the credentials to construct the API base URL.
- No additional external dependencies are indicated.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect project IDs in the "Projects Filter" may result in empty responses.
- Requesting a recording type that does not exist or is unsupported will yield no results.
- Pagination issues if "Return All Results" is false and more data exists than the default page size.
Error Messages:
- Authentication errors typically indicate invalid or expired tokens; re-authenticate the credential.
- HTTP 404 errors may indicate incorrect resource paths or non-existent projects.
- Rate limiting errors from Basecamp API require waiting before retrying or adjusting request frequency.
Links and References
- Basecamp API Documentation
- n8n OAuth2 Credential Setup
- Basecamp API Recordings Endpoint (for detailed API parameters and response schema)