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 Customer resource and the Search Customers operation, this node enables querying customer data based on multiple filtering criteria like name, UUID, creation date, and status (enabled/disabled). It supports pagination and sorting, making it useful for retrieving manageable subsets of customer records.
Typical use cases include:
- Fetching a list of customers matching specific search criteria for reporting or analysis.
- Integrating customer data into workflows that require customer validation or enrichment.
- Automating customer management tasks by retrieving filtered customer lists.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of results to return (pagination control). |
| Page Size | Number of customer items to return per page. |
| Sort Property | The property name by which to sort the results (e.g., name, creation date). |
| Sort Ascending | Whether to sort the results in ascending order (true) or descending order (false). |
| Name Contains | Filter customers whose names contain this string. |
| Is Enabled | Filter customers based on whether they are enabled (true) or disabled (false). |
| UUID Equals | Filter customers by an exact UUID match. |
| Created After | Filter customers created after this date (ISO 8601 string expected). |
| Created Before | Filter customers created before this date (ISO 8601 string expected). |
Output
The node outputs JSON data representing the list of customers matching the search criteria. Each item in the output array corresponds to a customer object returned by the Zorus API. The structure typically includes customer details such as UUID, name, status, creation date, and other relevant metadata.
If binary data is supported (not indicated explicitly here), it would represent attachments or files related to customers, but this node primarily deals with JSON customer data.
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. - No additional external dependencies beyond the configured API authentication.
Troubleshooting
- Invalid API Key or Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Pagination Issues: If no results appear, verify that the page number and page size are within valid ranges and that filters are not overly restrictive.
- Date Format Errors: The
Created AfterandCreated Beforefields expect ISO 8601 date strings; incorrect formats may cause errors or empty results. - Sorting Problems: Using an invalid property name in
Sort Propertymight result in unsorted or default-sorted results. - Empty Results: Could indicate no customers match the filter criteria; try broadening filters or removing some conditions.
Links and References
- Zorus API Documentation — Official API reference for detailed endpoint and parameter information.
- n8n Documentation on Creating Custom Nodes — For understanding how to configure and use custom nodes like this one.