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
Recording → Trash a Recording
AI-generatedOverview
This node operation allows users to trash (delete) a specific recording within a project in Basecamp. It is useful for managing and cleaning up recordings that are no longer needed or relevant. For example, if a user wants to remove a recording from a project to keep the project organized, they can use this operation by specifying the project ID and the recording ID.
Use Case Examples
- Trash a recording by providing the project ID and recording ID to remove unwanted recordings from a Basecamp project.
- Use the operation to manage storage by deleting obsolete or incorrect recordings.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the recording is located. Used in the API endpoint path to specify the project. |
| Recording ID | The ID of the recording to be trashed. Used in the API endpoint path to specify the recording. |
| Return Full Response | Whether to return the full HTTP response including status code, headers, and body instead of only the response body. |
| Request Options | Additional options for the HTTP request such as batching, SSL certificate validation, proxy settings, and timeout. |
Output
JSON
statusCode- HTTP status code of the response when full response is requested.headers- HTTP headers of the response when full response is requested.body- The main content of the response, typically the result of the trash operation.
Dependencies
- An OAuth2 API credential for Basecamp authentication
Troubleshooting
- Ensure the Project ID and Recording ID are correct and exist in Basecamp to avoid 'not found' errors.
- Check network connectivity and proxy settings if requests fail to reach the Basecamp API.
- If SSL certificate validation fails, consider enabling the option to ignore SSL issues, but be aware of security risks.
- Timeout errors can occur if the server is slow to respond; increase the timeout setting if needed.
Links
- Basecamp API Documentation - Official documentation for Basecamp API endpoints and usage.