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 Call Detail Records (CDRs). Specifically, for the Call Detail Record - Delete operation, it deletes a CDR identified by its unique ID. This is useful in scenarios where you need to remove obsolete or incorrect call records from your TeleFlow system.
Practical examples include:
- Automatically cleaning up call logs after a certain period.
- Removing test or erroneous call records during data maintenance.
- Integrating with workflows that require conditional deletion of call details based on external triggers.
Properties
Name | Meaning |
---|---|
ID | The unique identifier of the Call Detail Record to delete. This is required. |
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 specified Call Detail Record. Typically, this will be an object indicating success or failure of the deletion operation. No binary data is output by this node.
Example output structure:
{
"success": true,
"message": "Call Detail Record deleted successfully"
}
or in case of error:
{
"error": "Error message describing what went wrong"
}
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 credentials.
- The node uses HTTP DELETE requests to the endpoint
/callDetailRecords/{id}
to perform deletions.
Troubleshooting
- Missing ID Error: If the ID property is not provided, the node throws an error stating "ID is required for delete operation". Ensure the ID of the record to delete is correctly supplied.
- API Connection Issues: Errors related to network connectivity or authentication failures may occur if the API key or base URL is misconfigured.
- Permission Denied: If the API user lacks permission to delete records, the API will return an error. Verify API user permissions.
- Record Not Found: Attempting to delete a non-existent record ID will result in an error from the API. Confirm the ID exists before deletion.
To resolve errors, verify input parameters, check API credentials and permissions, and consult TeleFlow API documentation for error codes.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/