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 interact with various resources such as customers, deployment tokens, groups, policies, unblock requests, and endpoints. Specifically, for the Create Customer operation, this node enables creating a new customer record in the Zorus system by specifying details like the customer's name and an associated base policy UUID.
This node is beneficial in automation workflows where managing customer data programmatically is required, such as onboarding new clients, syncing customer information from other systems, or automating policy assignments during customer creation.
Practical Example
- Automatically create a new customer in Zorus when a new user signs up on your platform.
- Assign a default base policy to each newly created customer to enforce consistent access controls.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the customer to be created. |
| Base Policy UUID | The unique identifier (UUID) of the base policy that will be assigned to the customer. |
Output
The node outputs JSON data representing the newly created customer object as returned by the Zorus API. This typically includes fields such as the customer's ID, name, associated policies, creation timestamps, and any other metadata provided by the API response.
If the node supports binary data output, it would generally relate to file attachments or similar content, but based on the provided code and properties, the output is purely JSON structured data about the customer.
Dependencies
- Requires an active connection to the Zorus API endpoint at
https://developer.zorustech.com/api. - Needs an API authentication token credential configured within n8n to authorize requests.
- The node uses HTTP headers including
Accept: application/json,Content-Type: application/json, and a custom headerZorus-Api-Version: 1.0.
Troubleshooting
- Authentication errors: Ensure the API key or token credential is correctly set up and has sufficient permissions.
- Invalid UUID for Base Policy: If the provided base policy UUID does not exist or is malformed, the API may return an error. Verify the UUID format and existence in Zorus.
- Missing required fields: The "Name" property must be provided; otherwise, the API might reject the request.
- Network issues: Confirm network connectivity to the Zorus API endpoint and that no firewall or proxy blocks the requests.
Links and References
- Zorus API Documentation (for detailed API usage and schema)
- n8n Documentation on Creating Custom Nodes