The Transcript Generated trigger automatically launches a workflow when a recorded call is successfully transcribed. Once triggered, it passes detailed call data — including the full transcript, call duration, direction, caller location, timestamps, and more — into your automation, enabling immediate downstream actions.
Supported Call Types #
- Voice AI Calls: Transcription is enabled by default.
- LC Phone Calls: Requires transcription to be enabled in Phone Settings.
- IVR Calls: Requires transcription to be enabled in IVR Settings.
Note: Transcription must be enabled for the trigger to function. If transcription is not enabled, the workflow will prompt you to go to the appropriate settings and activate it.
Key Benefits #
- AI-Powered Personalization: Use transcript data with AI Decision Maker or GPT Actions to customize responses based on sentiment, intent, or keywords.
- Actionable Insight Capture: Automatically log buying intent, objections, or important phrases directly into the contact record.
- Comprehensive Data Access: Leverage rich metadata — including call direction, timestamps, duration, and user details — to build precise workflow conditions.
How to Set Up the Transcript Generated Trigger #
Create or Edit a Workflow #
Navigate to Automation > Workflows. Click + Create Workflow, then select Start from Scratch or open an existing one.
Add the Transcript Generated Trigger #
Click Add New Trigger, then select Transcript Generated from the trigger list.
Workflow Trigger Name #
Once it is added, update the trigger’s name if necessary.
Apply Filters #
- Call Type: Choose Voice AI, IVR, or Normal Calls.
- Call Direction (Optional): Filter by inbound or outbound calls.
- Call Duration (Optional): Exclude short or incomplete calls (for example, greater than 30 seconds).
Save and Publish #
Click Save Trigger to add the trigger to your workflow, then configure your workflow actions to replace manual post-call processes. Start using the Transcript Generated trigger to unlock smarter, faster, and more efficient communication workflows across every call channel.
Frequently Asked Questions #
What happens if transcription fails or only partial audio is available? #
If a call fails to transcribe completely, the trigger will not activate. For partial transcripts, the workflow fires normally, but missing segments will appear as blank in the {{full transcript}} custom value. Calls that are never successfully transcribed will not activate this trigger.
Can multiple workflows respond to the same transcript event? #
Yes. Multiple workflows can be triggered by the same transcript event, as long as each workflow uses unique conditions. Use filters strategically to prevent duplicate or redundant actions.
How is transcript data stored and secured? #
Transcripts are securely stored within the system’s infrastructure and tied to the associated contact record. Access is governed by user permissions, and administrators can view, delete, or export transcripts.
Is there a limit to the transcript size for workflow processing? #
Yes. Transcripts up to 16 KB can be referenced in custom fields. For longer calls, store the transcript in a note field or link to it via webhook or file URL. The workflow can still process based on the complete transcript even if it exceeds field limits.
What call types are supported? #
Voice AI calls (transcription on by default), LC Phone calls, and IVR calls (both require transcription enabled in their respective settings).
What filters can I apply to this trigger? #
Call Type, Call Direction, and Call Duration help you target the specific calls you want the workflow to act on.
