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 perform various operations on different resources. Specifically, for the Transcription resource with the Get Many operation, it retrieves multiple transcription records from the TeleFlow system. Users can specify filtering fields to narrow down the results.
This node is beneficial when you want to programmatically fetch a list of transcriptions, for example:
- Retrieving all transcriptions within a certain date range.
- Filtering transcriptions by status or associated call ID.
- Automating reports or workflows that require bulk transcription data.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used as filters in the request to refine the query. You can add multiple fields, each specifying a field name and its corresponding value to filter the transcriptions returned. |
The "Fields" property allows users to specify any number of filtering criteria by adding multiple field entries, each with:
- Name: The field name to filter by (e.g., "status", "date").
- Value: The value to match for that field.
Output
The output is an array of JSON objects representing transcription records retrieved from the TeleFlow API. Each item corresponds to one transcription entry matching the specified filters.
The exact structure of each transcription object depends on the TeleFlow API response but typically includes details such as transcription text, timestamps, related call identifiers, and status.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the TeleFlow API via an API key credential configured in n8n.
- The node uses the base URL and authentication headers provided by the credential to make HTTP requests.
- No additional external dependencies are required beyond the TeleFlow API access.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key credential is correctly set up with valid access to the TeleFlow API.
- Empty or no results returned: Verify that the filter fields are correct and correspond to valid transcription properties. Incorrect field names or values may result in no matches.
- Error messages about missing IDs: This does not apply to the "Get Many" operation but may appear if other operations are selected incorrectly.
- Network or connectivity issues: Confirm that the base URL is reachable and the network allows outbound HTTPS requests to the TeleFlow API.
If errors occur, enabling "Continue On Fail" will allow the workflow to proceed while logging error details in the output.
Links and References
- TeleFlow API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/