Transcribe Audio
Use this action when you have an audio file in your company storage and want a transcript produced from it.
Best for
- Transcribing a file a workflow just created, such as the output of Upload to storage or Download to storage
- Turning voice notes or call recordings into text for later steps
- Producing subtitle files (
srt,vtt) alongside the plain transcript
To transcribe an audio message that is already in a conversation, use Execute function on document with the message's own transcription function instead — it is built for that case.
Main fields
| Field | What it does |
|---|---|
| File | The audio file to transcribe, usually step(0).file from an earlier step |
| Bucket and Full path | An alternative to File when you want to point at the object directly |
| Transcription profile | Which transcription settings to use. Leave it empty to use your company default |
| Language | Overrides the profile's language, for example pt-BR |
| Formats | Which outputs to produce: txt, srt, vtt, json. All four by default |
| Purpose | Optional label for what this step is for, shown in the logs |
What later steps can use
| Value | What it is |
|---|---|
step(N).jobId | The transcription job's ID |
step(N).jobStatus | The job's status when it was queued — normally pending |
step(N).enginePath | How the audio will be processed |
step(N).providerType | Which transcription provider will run it |
step(N).diarized | Whether the transcript will label who is speaking |
This action queues the job — it does not wait for it
The step hands back a job ID and finishes immediately. Real transcription takes minutes, so it runs in the background.
That means the transcript is not available to the next step in the same run. To get the result:
- Open the transcriptions panel in the app, or
- Look the job up by its ID from another workflow run later
You also receive a notification when the job finishes.
Tips
- You can queue up to 10 transcription jobs at a time. Beyond that the step fails until earlier jobs finish.
- Transcription counts toward your plan's usage. Profiles that use your own provider keys are tracked but not billed.
- Read the job's outcome with
step(N).jobStatus, notstep(N).status—statusis reserved for HTTP status codes and will not hold the job's state.