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 such as accounts, devices, feature codes, and more. Specifically, for the Feature Code resource with the Delete operation, it deletes a feature code identified by its unique ID.
Common scenarios where this node is beneficial include automating the cleanup of obsolete or unused feature codes in a telephony system, managing telephony configurations programmatically, or integrating TeleFlow management into broader workflows.
For example, you might use this node to delete a feature code after it has been deprecated or replaced, ensuring your telephony system remains clean and up-to-date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the feature code to delete. This is required to specify which feature code 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 feature code. Typically, this will be an object indicating success or failure of the deletion operation. The exact structure depends on the API's response but generally confirms whether the feature code was deleted.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The node expects the base URL of the TeleFlow API to be configured in the credentials.
- Network access to the TeleFlow API endpoint is necessary.
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 feature code ID.
- API Request Failures: Errors returned from the TeleFlow API (e.g., invalid ID, permission issues) will be surfaced. Check that the ID exists and that the API key has sufficient permissions.
- Network Issues: Connectivity problems to the TeleFlow API endpoint can cause failures. Verify network access and correct base URL configuration.
- 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 Documentation on HTTP Request Node (for understanding underlying HTTP calls)
- General n8n Node Development Guide