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 operation "Trash Recording" under the "Recordings" resource allows users to move a specific recording into the trash within a project bucket. It is useful for managing and organizing recordings by removing unwanted or obsolete audio/video files without permanently deleting them immediately. For example, a user might want to clean up their project workspace by trashing recordings that are no longer needed but may still be recoverable later.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | ID of the project bucket containing the recording. This identifies the container or project area where the recording resides. |
| Recording Id | ID of the specific recording to be trashed. This uniquely identifies the recording within the bucket. |
Output
The node outputs JSON data representing the result of the trash operation on the specified recording. Typically, this would include confirmation details such as the trashed recording's ID, status, or metadata indicating it has been moved to trash. The output does not indicate binary data handling.
Dependencies
- Requires an API key credential for authentication with the external service managing recordings.
- The node depends on the Basecamp API (as inferred from the bundled code) or a similar project management platform API that supports recording management.
- Proper configuration of the API base URL and authentication credentials in n8n is necessary.
Troubleshooting
- Invalid Bucket Id or Recording Id: If either ID is incorrect or does not exist, the API will likely return an error indicating the resource was not found. Verify IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key or OAuth token is correctly configured.
- API Rate Limits: Excessive requests may lead to rate limiting errors. Implement retry logic or reduce request frequency.
- Network Issues: Connectivity problems can cause timeouts or failed requests. Check network stability and API endpoint accessibility.
Links and References
- Basecamp API Documentation
- General n8n documentation on Creating Custom Nodes