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 stored or inactive, which can help in organizing and managing recordings by removing them from active lists without deleting them permanently. This is useful in scenarios where you want to keep historical data but avoid cluttering the active workspace.
Practical examples include:
- Archiving old meeting recordings after they have been reviewed.
- Moving completed webinar recordings into an archive for long-term storage.
- Managing audio/video files in projects by archiving those no longer needed for immediate access.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | ID of the project bucket containing the recording. |
| Recording Id | ID of the recording to be archived. |
Output
The node outputs JSON data representing the result of the archive operation on the specified recording. This typically includes confirmation of success and may contain metadata about the archived recording such as its ID, status, or timestamps.
If the node supports binary data output (not evident from the provided code), it would represent the actual recording file or related binary content, but this is not indicated here.
Dependencies
- Requires an API key credential or authentication token to interact with the external service managing recordings.
- The node depends on the Basecamp API or a similar service endpoint configured via environment variables or credentials within n8n.
- Proper configuration of the base URL and authentication headers is necessary for successful API 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 token is incorrect or expired.
- Network connectivity problems preventing access to the external API.
- Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and refresh tokens if applicable.
- "Recording not found": Verify that the provided Recording Id exists within the specified Bucket Id.
- "Invalid input": Ensure that Bucket Id and Recording Id are numbers and correctly set.
Links and References
- Refer to the official API documentation of the service managing recordings for detailed information on archiving endpoints.
- n8n documentation on creating and configuring custom nodes and handling API credentials.