Actions82
- 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
Overview
This node interacts with the TeleFlow API to manage various resources such as accounts, devices, phone numbers, users, and more. Specifically, for the Account - Delete operation, it deletes an account resource identified by a unique ID. This is useful in scenarios where you need to programmatically remove obsolete or unwanted account records from your TeleFlow system.
Practical examples include:
- Automating cleanup of test or temporary accounts.
- Integrating account lifecycle management into broader workflows.
- Removing accounts that no longer meet certain criteria or have been deactivated elsewhere.
Properties
Name | Meaning |
---|---|
ID | The unique identifier of the account resource to delete. This is required. |
Fields | Optional field-value pairs to include in the request for more specific queries (not used in delete but available for other operations). |
Additional Details | Informational notice related to the Account resource (displayed in the UI, no direct effect on delete operation). |
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the specified account. Typically, this will be a confirmation of deletion or an empty object indicating success. If the deletion fails, the output may contain error details.
No binary data is output by this node.
Example output JSON after successful deletion might look like:
{}
or
{
"message": "Account deleted successfully"
}
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 methods (DELETE) 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 provide a valid account ID.
- API Authentication Errors: If the API key or base URL is incorrect or missing, requests will fail. Verify your credentials configuration.
- Resource Not Found: If the specified account ID does not exist, the API may return a 404 error. Confirm the ID is correct.
- Permission Issues: Insufficient permissions for the API key can cause authorization errors. Check API user roles and permissions.
- Network Issues: Connectivity problems can cause request failures. Ensure network access to the TeleFlow API endpoint.
Links and References
- TeleFlow API Documentation (Replace with actual URL if available)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/