Actions145
- 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
- File Actions
- Flow Actions
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Reseller Actions
- SIP Trunk Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
- Transcription Actions
- User Actions
- Voice Actions
- Voice Mail Message Actions
Overview
This node interacts with the TeleFlow API to manage various resources, including Resellers. Specifically, the Delete operation on the Reseller resource allows users to remove a reseller entity from the TeleFlow system by specifying its unique identifier.
Common scenarios for this node include:
- Automating cleanup of reseller accounts that are no longer active or needed.
- Integrating TeleFlow reseller management into broader workflows where resellers must be programmatically deleted based on external triggers or conditions.
- Maintaining data hygiene by removing obsolete reseller records without manual intervention.
Example use case:
- A workflow that monitors reseller activity and deletes reseller entries automatically if they have been inactive for a certain period.
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 in the request for more specific queries (not typically used in delete but available as part of the generic interface). |
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 is output by this node.
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 requests to communicate with the TeleFlow REST API.
Troubleshooting
- Missing ID error: If the "ID" property is not provided, the node throws an error stating that the ID is required for the delete operation. 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 authenticate. Verify your credentials configuration.
- Resource not found: If the specified reseller ID does not exist, the API may return a 404 error. Confirm the ID is correct.
- Network issues: Connectivity problems can cause request failures. Check network access to the TeleFlow API endpoint.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/