Trigger: Recording Transcribed

The Recording transcribed trigger fires once a call recording's automatic transcription is ready, with the full text available. It's the step after "Recording ready": first the audio gets generated, then AI transcribes it to text.

Requirements

• Call recording must be enabled, and your plan must include automatic call transcription.

When to use it

• Search the transcription for keywords (e.g. "cancel", "complaint") and alert a supervisor.
• Save the full text as a note on the contact so any agent can read it without listening to the audio.
• Feed an AI call summary from the transcribed text.

Trigger settings

• Specific channel and Direction — the standard call filters.

Available variables

Standard call and contact variables, plus:

• $recording.id, $recording.duration, $recording.url.
• $recording.transcription — the full transcribed text.
• $recording.transcription_lang — the detected language (BCP-47 code, e.g. "en-US").

Steps

1. Confirm recording and transcription are enabled on your plan and channel.
2. Create or open an automation.
3. Drag "Recording transcribed" from Call triggers.
4. Connect an action, e.g. "Log activity" with the transcribed text, or a condition node checking for keywords.
5. Activate and save.

Example

You want to automatically detect if a customer mentioned "cancel" during the call. Connect a condition node checking whether {{$recording.transcription}} contains "cancel", and if so, fire "Notify the team": "Possible cancellation detected on the call with {{$contact.display_name}}. Transcript: {{$recording.transcription}}."

Tips

• The detected language in $recording.transcription_lang lets you route the transcription to a language-specific analysis flow if your business serves multiple countries.
• If the transcription comes back empty, check that the call transcription add-on/feature is active for your organization.