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 provides integration with the Basecamp API, specifically allowing users to manage recordings within their Basecamp projects. The "Archive a Recording" operation enables users to archive a specific recording by specifying the project and recording IDs. This is useful for organizing and managing recordings by moving them out of active lists without deleting them.
Common scenarios include:
- Archiving completed meeting recordings to keep the project workspace clean.
- Managing storage by archiving old or irrelevant recordings.
- Automating workflow steps where recordings are archived after certain triggers or conditions.
Example: Automatically archive a recording after it has been reviewed or processed in another system.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the recording exists; used in the API endpoint path. |
| Recording ID | The ID of the recording to be archived; used in the API endpoint path. |
| Return Full Response | Whether to return the full HTTP response (status code, headers, body) instead of only the response body. |
Output
The output contains a JSON object representing the response from the Basecamp API after attempting to archive the specified recording. If "Return Full Response" is enabled, the output includes the full HTTP response details such as status code, headers, and body. Otherwise, only the response body is returned.
No binary data is involved in this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests to the Basecamp API.
- The node uses the Basecamp API base URL constructed with the user's account ID.
- No additional external dependencies beyond the Basecamp API and proper credentials.
Troubleshooting
- Invalid Project or Recording ID: If the provided IDs do not exist or are incorrect, the API will likely return a 404 error. Verify that the IDs correspond to existing resources in your Basecamp account.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth2 token is correctly set up in n8n.
- Permission Issues: Lack of sufficient permissions on the Basecamp account may result in authorization errors. Confirm that the authenticated user has rights to archive recordings.
- Network or API Downtime: Network issues or Basecamp service outages can cause request failures. Retry later or check Basecamp status.
Links and References
- Basecamp API Documentation
- Basecamp Recordings API Reference (for detailed API endpoint info)