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 "Unarchive Recording" under the "Recordings" resource is designed to restore a previously archived recording back to an active state. It is useful in scenarios where recordings have been archived for storage or organizational purposes but need to be accessed or used again later. For example, if a user has archived meeting recordings or voice memos and wants to bring one back for review or sharing, this operation facilitates that.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | ID of the project bucket containing the recording. This identifies the specific project space or container where the recording resides. |
| Recording Id | ID of the recording to unarchive. This specifies which archived recording should be restored. |
Output
The output JSON will typically contain information about the unarchived recording, such as its updated status and metadata confirming it is no longer archived. The exact structure depends on the API response but generally includes identifiers and state details of the recording.
No binary data output is indicated for this operation.
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: If these IDs are incorrect or do not exist, the API may return errors indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key or token is correctly configured.
- Network Issues: Connectivity problems can lead to timeouts or failed requests. Check network settings and API availability.
- Permission Denied: If the authenticated user does not have rights to unarchive recordings in the specified bucket, the operation will fail. Confirm user permissions.
Links and References
- Refer to the official API documentation of the service managing recordings for detailed information on the unarchive endpoint.
- n8n documentation on creating and using custom nodes for API integrations.