Actions18
- Customer Actions
- Service Actions
- Connection Actions
Overview
The Disconnect Carrier Connection operation for the Connection resource in this custom n8n node is designed to disconnect a carrier service from a Genex customer account. This action is typically used when a customer no longer requires a specific carrier service, or when migrating services between carriers. The node interacts with the Genex API to process the disconnection, optionally sending a provisioning file to notify the carrier.
Common scenarios:
- Deactivating a phone number or internet service for a customer.
- Automating offboarding workflows when customers cancel their subscriptions.
- Managing carrier transitions or service cleanups in bulk.
Practical example:
A telecom company uses n8n to automate customer management. When a customer requests to disconnect their mobile service, this node can be triggered to remove the carrier connection and update all relevant systems automatically.
Properties
| Name | Meaning |
|---|---|
| Customer Number | Must be a valid Genex customer number. Identifies the customer whose carrier connection will be disconnected. |
| Service Number | Genex service number associated with the customer. This is found in the Service Details section of the Services screen. The service must exist and not be released. |
| Carrier Name or ID | Select from a list of carriers or specify an ID using an expression. |
| Disconnection Date | The date from which the service should be disconnected. Can be set to a past or future date. |
| Send Disconnection Request | Boolean (true/false). Indicates whether Genex should send a disconnection request in the provisioning file. |
| Disconnection Reason Name or ID | Select from a list of disconnection reasons or specify an ID using an expression. |
Output
- The output will be a
jsonobject containing the response from the Genex API regarding the disconnection request. - The structure typically includes:
- Confirmation of the disconnection action.
- Status or result message.
- Any error details if the operation failed.
Note: The exact fields depend on the Genex API's response for the disconnection operation.
Dependencies
- External Service: Requires access to the Genex API.
- Credentials: You must configure the
genexApicredentials in n8n for authentication. - Environment: Ensure network access to
https://genexapi.billing.com.au/.
Troubleshooting
Common issues:
- Invalid Customer or Service Number: If the provided numbers do not exist or are already released, the API may return an error.
- Missing Required Fields: All properties marked as required must be filled; otherwise, the node will throw validation errors.
- Authentication Errors: Incorrect or missing Genex API credentials will prevent successful execution.
- Date Format Issues: Ensure the Disconnection Date is in a valid format accepted by Genex.
Error messages and resolutions:
"Customer/service not found": Double-check the Customer Number and Service Number."Unauthorized": Verify that the Genex API credentials are correctly configured in n8n."Disconnection reason invalid": Make sure the Disconnection Reason is selected from the available options or specified correctly.