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 integrates with the TeleFlow API to manage various telephony-related resources. Specifically, for the Phone Number - Delete operation, it allows users to delete a phone number resource by specifying its unique identifier. This is useful in scenarios where phone numbers need to be removed from the system, such as decommissioning unused numbers or cleaning up test data.
Practical examples:
- Automatically removing phone numbers that are no longer assigned to users.
- Cleaning up phone number records during account closure workflows.
- Managing phone number lifecycle in bulk automation processes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the phone number resource to delete. This is required. |
| Fields | Optional field-value pairs to include additional query parameters in the request (not used in delete but available for other operations). |
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the specified phone number. Typically, this will include confirmation of deletion or relevant status information returned by the API.
No binary data output is produced by this operation.
Example output structure:
{
"success": true,
"message": "Phone number deleted successfully",
"id": "12345"
}
(Note: Actual fields depend on the TeleFlow API response.)
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP DELETE requests to interact 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 phone number ID.
- API errors: If the API returns an error (e.g., invalid ID, permission denied), the node will throw an error unless "Continue On Fail" is enabled, in which case the error message is included in the output JSON.
- Network issues: Connectivity problems or incorrect base URL configuration can cause request failures. Verify network access and credential settings.
- Permission issues: Ensure the API key has sufficient permissions to delete phone number resources.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- General n8n node development guide: https://docs.n8n.io/integrations/creating-nodes/