Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- Account Actions
- Account Audit Actions
- Billing Entry Actions
- Call Detail Record Actions
- Carrier Actions
- Device Actions
- Device Template Actions
- Email Template Actions
- Feature Code Actions
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
Overview
This node interacts with the TeleFlow API to manage various resources, including Resellers. Specifically, the Delete operation for the Reseller resource allows users to remove a reseller entity from the TeleFlow system by specifying its unique identifier.
Common scenarios where this node is beneficial include:
- Automating cleanup of reseller accounts that are no longer active or needed.
- Integrating reseller management into broader workflows where resellers must be programmatically deleted based on external triggers or conditions.
- Maintaining data hygiene in TeleFlow by removing obsolete reseller entries.
For example, a user might set up a workflow that deletes a reseller when their contract expires or if they fail compliance checks.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the reseller to delete. This is required to specify which reseller to remove. |
| Fields | Optional field-value pairs to include additional query parameters in the request (not typically used for delete but available). |
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the reseller. Typically, this will confirm whether the deletion was successful or provide details about the deleted resource.
No binary data output is produced by this operation.
Example output structure:
{
"success": true,
"message": "Reseller deleted successfully",
"id": "reseller-id"
}
(Note: Actual response fields depend on the TeleFlow API's delete endpoint.)
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the node credentials.
- The node uses HTTP DELETE requests to the
/resellers/{id}endpoint of the TeleFlow API.
Troubleshooting
- Missing ID error: If the "ID" property is not provided, the node throws an error stating that the ID is required. Ensure you supply a valid reseller ID.
- API authentication errors: If the API key or base URL is incorrect or missing, the node will fail to connect. Verify your credentials and configuration.
- Resource not found: If the specified reseller ID does not exist, the API may return a 404 error. Confirm the ID is correct.
- Permission issues: Deleting a reseller may require specific permissions. If unauthorized, check the API key's access rights.
- Network issues: Connectivity problems can cause request failures. Check network settings and API availability.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/