Actions119
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Recording → Unarchive a Recording
AI-generatedOverview
This node operation unarchives a specific recording within a project in Basecamp. It is useful when you want to restore access to a recording that was previously archived, making it active and accessible again. For example, if a recording was archived for storage or organizational purposes but needs to be reviewed or edited later, this operation will unarchive it.
Use Case Examples
- Unarchive a recording by specifying the project ID and recording ID to make the recording active again.
- Restore access to an archived recording in a project to continue collaboration or review.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the recording is located. Used in the API endpoint path to identify the project. |
| Recording ID | The ID of the recording to unarchive. Used in the API endpoint path to identify the specific recording. |
| Return Full Response | Whether to return the full HTTP response including status code, headers, and body, instead of only the response body. |
| Request Options | Additional options for the HTTP request such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
body- The main response body from the unarchive recording API call, containing details of the unarchived recording.statusCode- The HTTP status code of the response, available if 'Return Full Response' is enabled.headers- The HTTP response headers, available if 'Return Full Response' is enabled.
Dependencies
- Basecamp API with OAuth2 authentication
Troubleshooting
- Ensure the Project ID and Recording ID are correct and correspond to existing resources in Basecamp.
- If the API returns an authentication error, verify that the OAuth2 credentials are valid and have the necessary permissions.
- If SSL issues occur, consider enabling the 'Ignore SSL Issues' option if appropriate for your environment.
- Timeout errors may occur if the server is slow to respond; adjust the timeout setting accordingly.
Links
- Basecamp API Documentation - Official documentation for Basecamp API endpoints and usage.