Actions76
- 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
Overview
The "Toggle Client Visibility" operation in the Client Visibility resource allows users to change whether a specific recording within a project is visible to clients. This node is useful in scenarios where you want to control client access to certain recordings, for example, hiding sensitive or internal recordings from clients or making them available when appropriate.
Practical examples include:
- A project manager toggling visibility of meeting recordings so that clients can only see finalized discussions.
- Temporarily hiding recordings during internal reviews before sharing with clients.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the recording resides; used in API path. |
| Recording ID | The numeric ID of the recording whose visibility is being toggled; used in API path. |
| Visible to Clients | Boolean flag indicating if the recording should be visible (true) or hidden (false) to clients. |
| Return Full Response | Boolean flag to determine if the node returns the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the response from the API after toggling the visibility of the recording. By default, this output contains only the response body, which typically includes confirmation or details about the updated visibility status.
If the "Return Full Response" property is set to true, the output will include the entire HTTP response object, including status code, headers, and body, allowing for more detailed handling or debugging.
This node does not output binary data.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- Needs the account ID configured in credentials to construct the API base URL.
- No additional external dependencies beyond the Basecamp API and proper authentication.
Troubleshooting
- Invalid Project or Recording ID: If the provided IDs do not exist or are incorrect, the API may return errors such as "Not Found". Verify the IDs are correct and accessible by the authenticated user.
- Insufficient Permissions: If the API credentials lack permissions to modify recording visibility, the request will fail. Ensure the OAuth2 token has adequate scopes.
- Network or Authentication Errors: Common issues include expired tokens or connectivity problems. Refresh credentials or check network settings.
- Unexpected Response Format: If "Return Full Response" is enabled but downstream nodes expect only the body, adjust accordingly to avoid processing errors.
Links and References
- Basecamp API Documentation
- n8n OAuth2 Credential Setup
- Basecamp Recordings and Client Visibility Concepts (hypothetical link for context)