Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
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 keeping historical data accessible but not cluttering active views.
Practical examples:
- A user wants to archive old meeting recordings in a project bucket to keep the workspace tidy.
- Automatically archiving recordings after a certain date or event to maintain compliance or storage limits.
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 project or account identifier).
- Network access to the external API endpoint responsible for managing recordings is necessary.
Troubleshooting
- Invalid Bucket Id or Recording Id: Ensure both IDs are correct and correspond to existing resources; otherwise, the API may return errors like "Not Found" or "Invalid ID".
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key or token is correctly configured.
- Network Issues: Connectivity problems can prevent the node from reaching the API. Check network settings and firewall rules.
- API Rate Limits: If too many requests are made in a short time, the API might throttle or block requests temporarily.
Links and References
- Refer to the external service's official API documentation for details on the archive recording endpoint.
- n8n documentation on how to configure API credentials and use custom nodes.