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 telephony-related resources, including SIP Trunks. Specifically, the Delete operation for the SIP Trunk resource allows users to remove a SIP Trunk from their TeleFlow account by specifying its unique identifier.
Common scenarios where this node is beneficial include:
- Automating cleanup of unused or obsolete SIP Trunks in bulk.
- Integrating TeleFlow SIP Trunk management into larger workflows, such as provisioning or decommissioning telephony infrastructure.
- Ensuring synchronization between TeleFlow and other systems by programmatically deleting SIP Trunks when they are no longer needed.
Practical example:
- A telecom administrator uses this node within an n8n workflow to delete a SIP Trunk immediately after it is replaced by a new trunk, ensuring no orphaned trunks remain active.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the SIP Trunk to delete. This is required to specify which trunk to remove. |
| Fields | Optional field-value pairs to include in the request for more specific queries (not typically used in delete operations). |
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the specified SIP Trunk. Typically, this will be a confirmation object indicating success or details about the deletion result.
No binary data is output by this node.
Example output structure:
{
"success": true,
"message": "SIP Trunk deleted successfully"
}
or an error message if deletion failed.
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 sends HTTP DELETE requests to the TeleFlow API endpoint corresponding to the SIP Trunk resource.
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 SIP Trunk ID.
- API Authentication Errors: If the API key or base URL is incorrect or missing, the node will fail to authenticate. Verify your TeleFlow API credentials and configuration.
- Resource Not Found: If the specified SIP Trunk ID does not exist, the API may return a 404 error. Confirm the ID is correct and the trunk exists.
- Network Issues: Connectivity problems can cause request failures. Check network access to the TeleFlow API endpoint.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation
- n8n Workflow Automation Platform