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 "Voice". Specifically, the Delete operation for the Voice resource allows users to remove a voice-related entity by its unique identifier. This is useful in scenarios where you need to programmatically clean up or manage voice records, such as deleting outdated voice configurations or removing voice entries that are no longer needed.
Practical examples:
- Automatically deleting a voice record after a certain event or condition is met.
- Cleaning up test voice data created during development or testing phases.
- Integrating with other workflows to maintain an up-to-date voice resource list by removing obsolete entries.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the voice resource to delete. Required for the delete operation. |
| Fields | Optional field-value pairs to include in the request for more specific queries (not typically used in delete). |
Output
The output is a JSON object representing the response from the TeleFlow API after attempting to delete the specified voice resource. Typically, this will confirm whether the deletion was successful or provide details if it failed.
No binary data output is produced by this operation.
Example output structure:
{
"success": true,
"message": "Voice resource deleted successfully"
}
or in case of error:
{
"error": "Resource not found"
}
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 endpoints.
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 ID.
- API Request Failures: Network issues, invalid credentials, or incorrect base URL configuration can cause HTTP request failures. Verify your API key and endpoint settings.
- Resource Not Found: Attempting to delete a non-existent voice resource may return an error from the API. Confirm the ID is correct and the resource exists.
- 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 for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/