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
The node provides functionality to unarchive a specific recording within a project bucket. This is useful in scenarios where recordings have been previously archived for storage or organizational purposes and need to be restored to an active state for further use, review, or processing.
Practical examples include:
- Restoring a meeting or call recording that was archived but now needs to be accessed again.
- Reactivating recordings for compliance audits or quality checks.
- Managing media assets by toggling their archived status without deleting them.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | ID of the project bucket containing the recording. Must be provided as a number. |
| Recording Id | ID of the recording to unarchive. Must be provided as a number. |
Output
The node outputs JSON data representing the result of the unarchive operation on the specified recording. This typically includes details about the recording's updated status and metadata confirming it is no longer archived.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the external service managing recordings.
- The node interacts with the Basecamp API (as inferred from the bundled code), so proper configuration of the Basecamp API credentials and permissions is necessary.
- Network access to the Basecamp API endpoint is required.
Troubleshooting
- Invalid Bucket Id or Recording Id: Ensure that the IDs provided are correct and correspond to existing resources in the project.
- Authentication Errors: Verify that the API key or OAuth2 token used has sufficient permissions to modify recording states.
- Network Issues: Check connectivity to the Basecamp API endpoint.
- API Rate Limits: If requests fail due to rate limiting, consider implementing retry logic or reducing request frequency.
Common error messages might include unauthorized access, resource not found, or invalid parameters. Resolving these involves checking credentials, verifying input IDs, and ensuring the API service is operational.
Links and References
- Basecamp API Documentation (for understanding API endpoints related to recordings)
- n8n documentation on creating custom nodes