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 carriers. Specifically, the Delete operation on the Carrier resource allows users to remove a carrier entry from their TeleFlow system by specifying its unique ID. This is useful in scenarios where obsolete or incorrect carrier data needs to be cleaned up to maintain accurate telephony configurations.
Practical examples:
- Removing a carrier that is no longer used in your telephony infrastructure.
- Automating cleanup of carriers as part of a larger workflow managing telephony resources.
- Integrating with external systems to synchronize carrier data by deleting carriers that have been removed elsewhere.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the carrier 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). |
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the specified carrier. Typically, this will confirm whether the deletion was successful or provide details if it failed.
Example output structure:
{
"success": true,
"message": "Carrier deleted successfully"
}
or an error message if deletion failed.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token configured in the node credentials.
- The base URL for the TeleFlow API must be set in the credentials configuration.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided, the node throws an error stating that the ID is required. Ensure you supply a valid carrier ID.
- API Request Failures: Network issues, invalid credentials, or insufficient permissions can cause the HTTP DELETE request to fail. Verify API credentials and network connectivity.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one deletion fails, returning error details in the output JSON.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes