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 perform various operations on different resources, including Transcriptions. Specifically, the "Get" operation for the "Transcription" resource retrieves detailed information about a single transcription by its unique ID. This is useful when you need to fetch specific transcription data, such as the text or metadata of a recorded call or voice message.
Practical examples include:
- Retrieving a transcription record to analyze call content.
- Fetching transcription details for quality assurance or compliance checks.
- Integrating transcription data into workflows for further processing or reporting.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the transcription resource to retrieve. This is required. |
| Fields | Optional field-value pairs to specify additional query parameters for filtering or detail. |
The "Fields" property allows adding multiple custom fields as key-value pairs to refine the request or specify which fields to include in the response.
Output
The output is a JSON object representing the transcription resource retrieved from the TeleFlow API. It contains all available data fields related to the transcription identified by the provided ID, such as transcription text, timestamps, associated call or user info, and any other metadata returned by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to access the TeleFlow API.
- The base URL for the API must be set in the node credentials.
- The node uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing ID Error: If the "ID" property is not provided, the node will throw an error stating that the ID is required for the get operation. Ensure the ID is correctly set.
- API Request Failures: Network issues, invalid credentials, or incorrect base URL configuration can cause HTTP request failures. Verify API credentials and endpoint settings.
- Field Parameter Issues: Incorrectly formatted or unsupported field names in the "Fields" property may result in unexpected API responses or errors. Use valid field names as per TeleFlow API documentation.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- TeleFlow API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation
- n8n Custom Node Development Guide