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
The node interacts with the TeleFlow API to perform various operations on different resources. Specifically, for the Transcription resource and the Create operation, it sends a POST request to create a new transcription entry in the TeleFlow system.
This node is beneficial when you want to automate the creation of transcriptions within your TeleFlow account directly from n8n workflows. For example, you might use it to programmatically add transcription data generated from calls or voice messages into TeleFlow for further processing or record-keeping.
Properties
| Name | Meaning |
|---|---|
| Fields | A collection of field-value pairs to include in the request. You can add multiple fields, each specifying a field name and its corresponding value to customize the transcription creation request. |
The "Fields" property allows flexible input of any additional parameters required by the TeleFlow API for creating a transcription, beyond fixed predefined properties.
Output
The node outputs an array of JSON objects representing the response from the TeleFlow API after creating the transcription. Each output item contains a json property with the full API response data for the created transcription.
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 uses HTTP requests to communicate with the TeleFlow REST API endpoints.
Troubleshooting
- Missing Required Fields: If required fields for creating a transcription are not provided, the API may return errors. Ensure all mandatory fields expected by TeleFlow are included in the "Fields" property.
- Authentication Errors: Incorrect or missing API credentials will cause authentication failures. Verify that the API key and base URL are correctly set in the node credentials.
- API Endpoint Issues: The node constructs the endpoint URL based on the resource name pluralized (e.g.,
/transcriptions). If the API changes or the resource name is incorrect, requests may fail. - Error Handling: If an error occurs during execution, the node logs the error message. If "Continue On Fail" is enabled, the workflow continues with error details in the output; otherwise, execution stops.
Links and References
- TeleFlow API Documentation (example placeholder link)
- n8n HTTP Request Node Documentation