Actions80
- 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
- Todos 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 cleaning up recordings by marking them as trashed without permanently deleting them immediately. For example, if you have recorded meetings or calls stored in buckets and want to remove outdated or irrelevant recordings, this operation helps you do so efficiently.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | ID of the project bucket containing the recording. |
| Recording Id | ID of the recording to be moved to trash. |
Output
The output JSON typically contains confirmation details about the trashed recording, such as its ID and status indicating it has been trashed. 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 authenticating with the external service managing recordings.
- The node uses a base URL constructed dynamically based on credentials (e.g., a Basecamp-like API endpoint).
- Proper configuration of authentication credentials in n8n is necessary to perform the operation.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Recording Id will cause the operation to fail.
- Authentication errors if the API key or token is incorrect or expired.
- Network connectivity problems can prevent reaching the API endpoint.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set and valid.
- "Recording not found" or similar: Verify that the provided Bucket Id and Recording Id are correct and exist.
- "Bad Request": Ensure all required parameters are provided and properly formatted.
Resolving these usually involves verifying input parameters and refreshing or reconfiguring credentials.
Links and References
- Refer to the external API documentation for managing recordings and trash operations.
- n8n documentation on setting up API credentials and using HTTP request nodes may provide additional context.