TeleFlowInstall

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 older than a certain date.
• Removing test or dummy call records after validation.
• Deleting specific call records based on external triggers or workflows.

Properties

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. The exact structure depends on the API's response but generally confirms whether the record was deleted.

No binary data output is produced by this operation.

Example output JSON might look like:

{
  "success": true,
  "message": "Call Detail Record deleted successfully"
}

or in case of error:

{
  "error": "Record not found"
}

Dependencies

• Requires an active connection to the TeleFlow API via an API key credential configured in n8n.
• The node uses HTTP requests to communicate with the TeleFlow API endpoint defined by the base URL in credentials.
• No additional external dependencies are needed beyond the configured API access.

Troubleshooting

• Missing ID Error: If the "ID" property is not provided, the node throws an error stating that the ID is required. Ensure you provide a valid Call Detail Record ID.
• API Authentication Errors: If the API key or base URL is incorrect or missing, the node will fail to authenticate. Verify your TeleFlow API credentials in n8n.
• Record Not Found: Attempting to delete a non-existent record may return an error from the API. Confirm the ID exists before deletion.
• Network Issues: Connectivity problems can cause request failures. Check network access and API availability.
• Continue On Fail: If enabled, the node will continue processing subsequent items even if one deletion fails, returning error details in the output JSON.

Links and References

• TeleFlow API Documentation (Replace with actual URL)
• n8n Documentation on Creating Custom Nodes
• General REST API best practices for resource deletion operations