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 manage various resources, including transcriptions. Specifically, the "Delete" operation for the "Transcription" resource allows users to remove a transcription record by its unique identifier. This is useful in scenarios where outdated or incorrect transcription data needs to be cleaned up or removed from the system.
Practical examples:
- Automatically deleting transcription records after a certain retention period.
- Removing transcriptions that were created in error or are no longer relevant.
- Managing transcription lifecycle as part of a larger workflow involving call recordings and voice data.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the transcription resource 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 transcription. Typically, this will confirm whether the deletion was successful or provide details if it failed. The structure depends on the API's response but generally includes status information.
No binary data output is involved in this operation.
Example output JSON might look like:
{
"success": true,
"message": "Transcription deleted successfully"
}
or in case of failure:
{
"error": "Transcription not found"
}
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API.
Troubleshooting
- Missing ID: If the "ID" property is not provided, the node will throw an error stating that the ID is required for the delete operation.
- Invalid ID: Providing an incorrect or non-existent transcription ID may result in an error response from the API indicating the resource was not found.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to delete transcriptions.
- Network issues: Connectivity problems can cause request failures; verify network access to the TeleFlow API endpoint.
- API errors: Check the API response message for details if deletion fails; it may indicate permission issues or other constraints.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node documentation for understanding how HTTP calls are made within nodes: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/