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 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 or confirmation fields.
No binary data output is involved in this operation.
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 endpoints.
Troubleshooting
- Missing ID: If the "ID" property is not provided, the node throws an error stating that the ID is required for the delete operation. Ensure the ID is correctly set.
- API Errors: Errors returned from the TeleFlow API (e.g., invalid ID, permission issues) will be logged and can cause the node to fail unless "Continue On Fail" is enabled.
- Network Issues: Connectivity problems or incorrect base URL configuration may prevent successful API calls.
- To resolve errors, verify the correctness of the transcription ID, API credentials, and network connectivity.
Links and References
- TeleFlow API Documentation (refer to official TeleFlow API docs for detailed endpoint behavior)
- n8n HTTP Request Node documentation (for understanding how HTTP requests are made within n8n)