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, including Flow Templates. Specifically, the Delete operation for the Flow Template resource allows users to remove a flow template by its unique identifier. This is useful in scenarios where outdated or unused flow templates need to be cleaned up to maintain an organized system.
Practical examples:
- Automatically deleting deprecated flow templates as part of a workflow cleanup.
- Removing test or temporary flow templates after validation.
- Managing lifecycle of flow templates programmatically without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Flow Template to delete. This is required to specify which flow template to remove. |
| Fields | Optional field-value pairs to include in the request for more specific queries (not typically used in delete but available). |
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the specified flow template. Typically, this will confirm whether the deletion was successful or provide details if it failed.
Example output structure:
{
"success": true,
"message": "Flow Template 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 via an API key credential configured in n8n.
- The base URL for the TeleFlow API must be set in the node credentials.
- The node uses HTTP methods (DELETE) to communicate with the API endpoint corresponding to flow templates.
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 the correct unique identifier of the flow template to delete.
- API Request Failures: Network issues, invalid credentials, or insufficient permissions can cause the API request to fail. Verify your API key and network connectivity.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one deletion fails, returning the error message in the output JSON.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/