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 Endpoint resource, it supports operations including isolating an endpoint.
The Isolate Endpoint operation enables users to isolate a specific endpoint identified by its UUID. This is useful in scenarios where an endpoint device needs to be quarantined or restricted from network access due to security concerns, suspicious activity, or compliance requirements.
Practical examples:
- Automatically isolate an endpoint when a threat is detected by a security monitoring system.
- Manually isolate endpoints during incident response workflows.
- Integrate endpoint isolation into automated remediation pipelines.
Properties
| Name | Meaning |
|---|---|
| Endpoint UUID | The unique identifier (UUID) of the endpoint to isolate. This is required to specify which endpoint should be isolated. |
Output
The node outputs JSON data representing the result of the isolate endpoint operation. This typically includes confirmation of the action taken on the specified endpoint, such as status updates or error messages returned by the Zorus API.
If the node supports binary data output, it would generally relate to any files or logs returned by the API, but based on the provided code and context, the primary output is JSON structured data reflecting the API response.
Dependencies
- Requires an active connection to the Zorus API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for API requests is
https://developer.zorustech.com/api. - The node sets headers to accept and send JSON content and specifies the API version as "1.0".
Troubleshooting
- Invalid or missing Endpoint UUID: Ensure that the UUID provided is correct and corresponds to an existing endpoint in the Zorus system.
- Authentication errors: Verify that the API key or token credential is correctly set up and has sufficient permissions.
- API connectivity issues: Check network connectivity and that the Zorus API service is reachable.
- Unexpected API responses: Review the JSON output for error messages returned by the API; these often indicate issues like rate limiting, invalid parameters, or internal server errors.
Links and References
- Zorus API Documentation (official API reference)
- n8n documentation on creating custom nodes