Actions57
- Agents Actions
- Public Answer Actions
- Answer Management Actions
- Communications Actions
- Customers Actions
- Conversations Actions
- Get Conversations
- Get Conversation
- Patch Conversation
- Create Item
- Get Item
- Delete Item
- Get Media
- Get Voice Transcript
- Create Customer Item
- Delete Customer Item
- Get Conversation Items
- Add Topic To Conversation
- Delete Topic From Conversation
- Add Note To Conversation
- Get Note From Conversation
- Reply To Message
- Redact Content
- Export Actions
- Freeform Topics Actions
- Message Automation Actions
- Proactive Conversations Actions
- Tasks Actions
- User Identity Actions
- Topics Actions
- Webhooks Actions
- Payloads Actions
Overview
This node interacts with the Gladly API to retrieve the voice transcript of a specific conversation item. It is useful in scenarios where you need to access and analyze the textual content of voice interactions within customer support or communication platforms. For example, customer service teams can use this node to fetch transcripts for quality assurance, training, or automated sentiment analysis.
Properties
| Name | Meaning |
|---|---|
| Item Id | The unique identifier of the conversation item whose voice transcript you want to retrieve. |
Output
The node outputs JSON data containing the voice transcript associated with the specified conversation item. This typically includes the textual representation of the audio content from the conversation. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node makes HTTP requests to the Gladly API endpoint (base URL:
https://petstore3.swagger.io/api/v3as per the bundled code, which may be a placeholder). - Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
- Invalid or missing Item Id: Ensure the "Item Id" property is correctly set and corresponds to an existing conversation item in Gladly.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- API endpoint issues: The base URL in the bundled code points to a placeholder (
petstore3.swagger.io). Confirm that the actual Gladly API base URL is configured correctly in the node or environment. - Network connectivity: Check network access to the Gladly API servers.
Links and References
- Gladly API Documentation (please refer to the official Gladly developer portal for up-to-date API details)
- n8n documentation on creating and using API credentials