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. Specifically, for the Transcription resource and the Get Many operation, it retrieves multiple transcription records from the TeleFlow system. Users can specify filtering fields to narrow down the results returned by the API.
This node is beneficial in scenarios where you need to programmatically fetch a list of transcriptions, for example:
- Retrieving all transcriptions within a certain date range or matching specific criteria.
- Integrating transcription data into workflows for further processing or reporting.
- Automating the extraction of transcription metadata for analysis or archival.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs used as filters to include specific fields in the request. You can add multiple fields to refine the query. Each field consists of: - Name: The name of the field to filter by (string). - Value: The value to match for that field (string). |
Output
The output is an array of JSON objects representing the transcription records retrieved from the TeleFlow API. Each item corresponds to one transcription entry with its associated data fields as returned by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the TeleFlow API.
- The base URL for the TeleFlow API must be configured in the node credentials.
- The node sends HTTP requests with JSON content type and expects JSON responses.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node credentials.
- Empty or no results returned: Verify that the filter fields are correctly specified and match existing transcription records.
- ID required errors: This does not apply to the "Get Many" operation but may occur if other operations like "Get" or "Update" are mistakenly selected without providing an ID.
- API request failures: Check network connectivity and API availability. Review error messages logged by the node for details.
- Continue on Fail behavior: If enabled, errors will be captured in the output JSON under an
errorproperty instead of stopping execution.
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/