Actions18
- Customer Actions
- Service Actions
- Connection Actions
Overview
The "Search Services" operation of the Genex node allows users to search for services within the Genex system using a specified search string. This is particularly useful in scenarios where you need to locate specific services based on partial or full identifiers, names, or other searchable attributes. For example, a telecom company might use this node to find all active or released services matching a customer query, or an administrator could automate service lookups as part of a larger workflow.
Properties
| Name | Meaning |
|---|---|
| Search String | Value to search. Enter the text or identifier you want to search for among services. |
| Include Released | Whether to include released services in the search. Set to true to include them, false otherwise. |
Output
- The output will be a JSON object (or array of objects) representing the results of the service search.
- Each result typically contains details about the matched services, such as their identifiers and relevant metadata.
- The exact structure depends on the Genex API response, but you can expect fields like service ID, name, status, and possibly more.
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the Genex API.
- Credentials: You must configure the
genexApicredentials in n8n for authentication. - WSDL Files: The node expects WSDL files for SOAP client creation (e.g.,
WSDL/CustomerService.wsdl). - Environment: Ensure network access to
https://genexapi.billing.com.au/.
Troubleshooting
- Missing Credentials: If credentials are not set up or incorrect, the node will throw an authentication error. Make sure the
genexApicredential is configured in n8n. - WSDL Not Found: If the required WSDL file is missing or misnamed, the node will fail to create the SOAP client. Ensure all necessary WSDL files are present in the expected directory.
- API Errors: If the Genex API returns an error (e.g., invalid parameters, server issues), the node will report it. Check the error message for details and verify your input values.
- Continue On Fail: If enabled, failed items will be returned with an
errorfield in the output; otherwise, execution stops at the first error.