Actions18
- Customer Actions
- Service Actions
- Connection Actions
Overview
This n8n node interacts with the Genex API, specifically targeting the "Service" resource and the "Get Customer Services" operation. It allows users to retrieve all services associated with a specific customer by providing their Genex customer number. This is useful in scenarios where you need to fetch, list, or process all services linked to a particular customer account—such as for reporting, auditing, or integration with other business processes.
Practical Example:
A telecom company using Genex for billing might use this node to automatically pull all active services for a customer when they call support, enabling agents to quickly view and manage the customer's subscriptions.
Properties
| Name | Meaning |
|---|---|
| Customer Number | Must be a valid Genex customer number. This identifies the customer whose services will be retrieved. (Required) |
Output
- The output will be a JSON object (or array of objects) representing the services associated with the provided customer number.
- Each item in the output corresponds to a service record for the specified customer.
- The exact structure of each service object depends on the Genex API response, but typically includes fields such as service ID, type, status, and related metadata.
Dependencies
- External Service: Requires access to the Genex API.
- Credentials: You must configure n8n with valid Genex API credentials (
genexApi). - Network Access: The node communicates with
https://genexapi.billing.com.au/. - SOAP Client: Uses the
soapnpm package internally (handled by the node).
Troubleshooting
- Invalid Customer Number: If an invalid or non-existent customer number is provided, the node may return an error or an empty result set. Ensure the customer number is correct.
- Authentication Errors: Missing or incorrect Genex API credentials will cause authentication failures. Double-check your credential setup in n8n.
- API Connectivity Issues: Network problems or incorrect endpoint configuration can lead to connection errors.
- Error Handling: If an error occurs and "Continue On Fail" is enabled, the error will be attached to the output; otherwise, the workflow will stop with an error message.
Common Error Messages:
NodeOperationError: Indicates a problem during execution, such as invalid parameters or API errors.- SOAP client errors: May indicate issues with the WSDL file or network connectivity.