Actions145
- User Actions
- Voice Actions
- File Actions
- Flow Actions
- Reseller Actions
- SIP Trunk Actions
- Transcription Actions
- Voice Mail Message Actions
- 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
- Flow Template Actions
- LCR Actions
- Mobile SIM Actions
- Number Port Actions
- Phone Number Actions
- Provision Actions
- Report Actions
- Tariff Actions
- Tariff Code Actions
- Tariff Profile Actions
- Tenant Actions
- Tenant Audit Actions
Overview
This node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Account Audit resource with the Delete operation, it deletes an account audit record identified by a unique ID.
Common scenarios where this node is beneficial include:
- Automating cleanup of audit records in TeleFlow.
- Integrating TeleFlow account audit management into workflows that require removing outdated or irrelevant audit entries.
- Managing audit data lifecycle programmatically without manual intervention.
Example use case: Automatically delete specific account audit entries after processing them in a workflow to maintain a clean audit trail.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Account Audit record to delete. This is required. |
| Fields | Optional field-value pairs to include in the request for more specific queries (not used in Delete operation). |
Output
The output JSON contains the response from the TeleFlow API after attempting to delete the specified Account Audit record. Typically, this will be a confirmation of deletion or an empty object indicating success.
No binary data is output by this node.
Example output JSON structure:
{
"success": true,
"message": "Account Audit record deleted successfully"
}
(Note: Actual response fields depend on the TeleFlow API's delete endpoint.)
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 DELETE requests to interact with the TeleFlow API.
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 ID.
- API authentication errors: If the API key or base URL is incorrect or missing, the node will fail to authenticate. Verify your credentials and configuration.
- Resource not found: If the specified ID does not exist, the API may return a 404 error. Confirm the ID is correct.
- Network issues: Connectivity problems can cause request failures. Check network access to the TeleFlow API endpoint.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/