TeleFlow icon

TeleFlow

Interact with TeleFlow API

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 a transcription record by its unique ID. This is useful when you need to fetch detailed information about a specific transcription, such as in call center analytics, voice-to-text processing workflows, or quality assurance processes.

For example, you might use this node to:

  • Retrieve the text and metadata of a particular call transcription.
  • Fetch transcription details to trigger further automated processing or reporting.
  • Integrate transcription data into other systems for analysis or storage.

Properties

Name Meaning
ID The unique identifier of the transcription resource to retrieve. This is required.
Fields Optional key-value pairs specifying additional fields to include in the request query. You can add multiple field name and value pairs to filter or customize the returned data.

Output

The output is a JSON object representing the transcription resource retrieved from the TeleFlow API. It contains all the properties of the transcription as provided by the API, which typically includes the transcription text, timestamps, associated call or recording IDs, and any metadata.

No binary data output is indicated for this operation.

Example output structure (simplified):

{
  "id": "string",
  "text": "string",
  "createdAt": "string",
  "callId": "string",
  "metadata": {
    "key": "value"
  }
}

Dependencies

  • Requires an API authentication token credential configured in n8n to access the TeleFlow API.
  • The base URL for the TeleFlow API must be set in the node credentials.
  • The node uses HTTP requests to communicate with the TeleFlow REST API.

Troubleshooting

  • Missing ID error: If the "ID" property is not provided for the get operation, the node will throw an error stating that the ID is required. Ensure you provide a valid transcription ID.
  • API connection issues: Errors related to network connectivity or invalid credentials may occur. Verify your API key/token and base URL configuration.
  • Invalid field names: Providing incorrect field names in the "Fields" property may result in unexpected responses or errors from the API. Double-check the API documentation for valid query parameters.
  • Handling failures: If the node is set to continue on fail, errors will be returned in the output JSON under an error property instead of stopping execution.

Links and References

Discussion