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 "Provision". Specifically, for the Provision - Delete operation, it deletes a provision resource identified by its unique ID. This is useful in scenarios where you need to programmatically remove provisioning entries from your TeleFlow system, such as cleaning up obsolete or incorrect provisions.
Practical examples:
- Automatically deleting a provision after a device or user is decommissioned.
- Removing test provisions created during development or troubleshooting.
- Integrating with workflows that maintain synchronization between TeleFlow and other systems by deleting provisions no longer needed.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the provision resource to delete. Must be provided. |
| 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 provision. Typically, this will confirm whether the deletion was successful or provide details if an error occurred.
No binary data is output by this node.
Example output structure:
{
"json": {
// API response confirming deletion or error details
}
}
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing ID Error: If the "ID" property is not set, the node throws an error stating that the ID is required for the delete operation. Ensure you provide a valid provision ID.
- API Request Failures: Network issues, invalid credentials, or insufficient permissions can cause HTTP request failures. Verify API credentials and network connectivity.
- 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 HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/