BasecampInstall

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 declutter their active recordings list.
• Automatically archiving recordings after a certain date or event to maintain an organized repository.

Properties

Output

The node outputs JSON data representing the result of the archive operation on the specified recording. This typically includes confirmation details such as the recording's updated status or metadata indicating successful archival.

No binary data output is involved.

Dependencies

• Requires an API key credential for authentication with the external service managing recordings.
• The node uses a base URL constructed dynamically based on credentials (e.g., a project or account identifier).
• Network access to the external API endpoint that handles recording archival.

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: Verify that the API key or authentication token is valid and has sufficient permissions to archive recordings.
• Network Issues: Check connectivity to the external API service.
• API Rate Limits: If many archive requests are made rapidly, the API might throttle requests; handle retries accordingly.

Links and References

• Refer to the external service’s official API documentation for "recordings" and "archive" operations.
• n8n documentation on creating custom nodes and handling API credentials.