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 perform various operations on multiple resource types, including Device Templates. Specifically, for the Device Template resource, it supports deleting a device template by its unique identifier.
A common use case for this node is automating the management of telephony infrastructure components within workflows. For example, you might want to programmatically remove obsolete or unused device templates from your TeleFlow system as part of a cleanup process or when decommissioning hardware configurations.
Practical example:
- Automatically delete a device template after a related device has been retired, ensuring that your TeleFlow environment stays tidy and up-to-date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the device template to delete. This is required to specify which device template to remove. |
| Fields | Optional field-value pairs to include in the request for more specific queries (not typically used for delete operation). |
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the specified device template. 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 includes status information or confirmation messages.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the TeleFlow API must be set in the node 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 device template ID.
- API errors: If the API returns an error (e.g., resource not found, permission denied), the node will either stop execution or continue based on the "Continue On Fail" setting. Check the error message for details.
- Network issues: Connectivity problems to the TeleFlow API endpoint can cause request failures. Verify network access and correct base URL configuration.
- Insufficient permissions: Make sure the API key or token used has the necessary rights to delete device templates.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/