BasecampInstall

Overview

This node operation "Trash Recording" under the "Recordings" resource allows users to move a specific recording into the trash (soft delete) within a project bucket. It is useful in scenarios where recordings need to be removed from active use but retained temporarily for possible recovery or auditing purposes. For example, a user managing audio or video recordings in a project can use this operation to clean up unwanted recordings without permanently deleting them immediately.

Properties

Output

The output JSON typically contains confirmation details about the trashed recording, such as its ID and status indicating it has been moved to trash. The exact structure depends on the API response but generally confirms successful trashing of the specified recording.

No binary data output is expected from this operation.

Dependencies

• Requires an API key credential for authentication with the external service managing recordings.
• The node uses a base URL constructed dynamically based on credentials.
• The node depends on an OpenAPI specification for request building and execution.

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.
• Network Issues: Connectivity problems may result in timeouts or failed requests. Check network access to the API endpoint.
• Permission Denied: Insufficient permissions to trash recordings in the specified bucket may cause errors. Confirm user rights on the project bucket.

Links and References

• Refer to the external API documentation for recordings management for detailed information on the trash operation.
• Consult n8n documentation on setting up API credentials and using HTTP request nodes for similar integrations.