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 allows users to archive a specific recording within a project bucket. Archiving a recording typically means marking it as inactive or moving it out of the active list without deleting it permanently. This can be useful for managing storage, organizing recordings, or preserving historical data while keeping the active workspace clean.
Practical examples:
- A user wants to archive old meeting recordings in a project bucket to reduce clutter.
- Automatically archiving recordings after a certain date or event to maintain an organized repository.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | ID of the project bucket where the recording is stored. Must be a number. |
| Recording Id | ID of the recording to archive. Must be a number. |
Output
The node outputs JSON data representing the result of the archive operation on the specified recording. This typically includes confirmation of success and possibly metadata about the archived recording (such as its ID, status, or timestamps). The exact structure depends on the API response but generally confirms that the recording was archived.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the external service managing recordings.
- The node uses a base URL constructed dynamically from credentials (e.g., a Basecamp-like API endpoint).
- Proper configuration of authentication credentials in n8n is necessary for successful requests.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Recording Id will cause the operation to fail.
- Authentication errors if the API key or OAuth token is not configured correctly.
- Network or API endpoint errors if the base URL or credentials are misconfigured.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Recording not found": Verify the Recording Id and Bucket Id are correct and exist.
- "Bad Request": Ensure all required parameters are provided and valid numbers.
Resolving these usually involves verifying input parameters and ensuring proper credential setup.
Links and References
- Refer to the external API documentation for managing recordings and archiving operations.
- n8n documentation on setting up API credentials and using HTTP request nodes may help configure this node properly.