Actions82
- 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
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 or removal of obsolete or incorrect feature codes in a telephony system managed via TeleFlow. For example, when a feature code is no longer needed or has been replaced, this node can be used to delete it programmatically as part of an automated workflow.
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 operation). |
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the specified feature code. Typically, this will confirm whether the deletion was successful or provide details if there was an error.
Example output structure:
{
"success": true,
"message": "Feature code deleted successfully"
}
or, in case of failure:
{
"error": "Feature code not found"
}
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 will throw an error stating that the ID is required for the delete operation. Ensure you provide a valid feature code ID.
- API Errors: If the feature code does not exist or cannot be deleted due to permissions, the API may return an error message. Check that the ID is correct and that the API key has sufficient rights.
- Network Issues: Connectivity problems with the TeleFlow API endpoint will cause request failures. Verify network access and API endpoint availability.
- 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 Error Handling Guide