Actions13
- Customer Actions
- Deployment Token Actions
- Endpoint Actions
- Group Actions
- Policy Actions
- Unblock Request Actions
Overview
The node named "Zorus" provides integration with the Zorus API, allowing users to manage various resources such as customers, deployment tokens, endpoints, groups, policies, and unblock requests. Specifically, for the Release Endpoint operation under the Endpoint resource, this node enables releasing a previously isolated or locked endpoint by its UUID.
This operation is useful in scenarios where an endpoint device was isolated due to security concerns or maintenance and now needs to be released back into normal operation. For example, after resolving a security incident on a workstation, an administrator can use this node to release the endpoint so it can resume normal network activity.
Properties
| Name | Meaning |
|---|---|
| Endpoint UUID | The unique identifier (UUID) of the endpoint to release. This is required to specify which endpoint should be released. |
Output
The node outputs JSON data representing the response from the Zorus API after attempting to release the specified endpoint. This typically includes status information about the release operation, such as success confirmation or error details if the release failed.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Zorus API.
- The base URL for API requests is
https://developer.zorustech.com/api. - The node expects the API version header
"Zorus-Api-Version": "1.0"to be set. - Proper configuration of the API credential within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Endpoint UUID will likely result in an error response from the API.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues may prevent reaching the Zorus API endpoint.
Error messages:
- Authentication errors indicating invalid API keys require verifying and updating the stored credentials.
- Not found or invalid UUID errors suggest checking the correctness of the provided Endpoint UUID.
- Rate limiting or server errors from the API should be handled by retrying after some delay or contacting Zorus support.
Links and References
- Zorus API Documentation (for detailed API usage and endpoint specifications)