Genex

Interact with Genex API

Actions18

Overview

The Genex node's "Service" resource with the "Update Service Name" operation allows users to update the name of an existing service in the Genex system. This is useful for organizations that need to keep their service records up-to-date, such as when a service changes its purpose or designation. For example, a telecom provider might use this node to rename a customer's internet service after an upgrade or rebranding.

Practical scenarios:

  • Correcting typos or outdated names in service records.
  • Reflecting product or plan changes for customer services.
  • Automating service name updates as part of larger workflows (e.g., after a CRM update).

Properties

Name Meaning
Customer Number Must be a valid Genex customer number. Identifies the customer whose service will be updated.
Service Number Genex service number associated with the customer. The service must exist and should not be released.
Name The new value to be updated into the service's Name field.

Output

  • The output will contain a json field reflecting the result of the update operation. The structure typically includes:
    • Confirmation of the update (success/failure).
    • Any returned data from the Genex API regarding the updated service.
    • If an error occurs and "Continue On Fail" is enabled, the output will include an error field with error details and a reference to the input item.

Example output:

{
  "json": {
    "status": "Success",
    "serviceNumber": "12345",
    "updatedName": "New Service Name"
  }
}

Or, on error (with continue on fail):

{
  "json": { ...originalInput },
  "error": {
    "message": "Invalid service number",
    ...
  },
  "pairedItem": 0
}

Dependencies

  • External Service: Requires access to the Genex API.
  • Credentials: Needs a configured genexApi credential in n8n.
  • Environment: The node uses SOAP requests and requires network access to the Genex API endpoint.

Troubleshooting

Common issues:

  • Invalid Customer or Service Number: If the provided numbers do not exist or are incorrect, the API will return an error.
  • Service Released: If the service has been released, it cannot be updated.
  • Missing Credentials: If the genexApi credential is not set up, the node will fail to authenticate.
  • Network Issues: Connectivity problems may prevent communication with the Genex API.

Error messages and resolutions:

  • "Invalid service number": Check that the Service Number exists and is active.
  • "Must be a valid Genex customer number": Ensure the Customer Number is correct and present in Genex.
  • "Authentication failed": Verify that the Genex API credentials are correctly configured in n8n.
  • "SOAP client creation failed": Ensure the WSDL files are accessible and the network connection to Genex is available.

Links and References

Discussion