ActionAssemblyAIUpdated September 2026
How do I start an AssemblyAI transcription?
Short answer: You can transcribe audio in AssemblyAI by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the AssemblyAI Transcribe Audio action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Audio URL audio_url | string | Required | (defaults to AssemblyAI's sample news.mp4) |
Model speech_models | array | Optional | Model. Options: Best (slower, accurate), Nano (fast) (array of model names) |
Speaker Labels speaker_labels | boolean | Optional | Speaker Labels. Options: No, Yes |
Language Code language_code | string | Optional | Language Code |
Sample request
{"audio_url": "https://example.com/audio.mp3","speech_models": "{{trigger.speech_models}}","speaker_labels": "{{trigger.speaker_labels}}","language_code": "{{trigger.language_code}}"}
Returns
{"id": "trans-abc123","status": "queued","language_code": "en"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Transcribe Audio.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Transcribe Audio.
What does the Transcribe Audio action do in AssemblyAI?
Submits an audio URL for transcription with options for speaker diarization, language detection, sentiment analysis, PII redaction, custom vocabulary. Returns the transcript ID; processing takes ~25% of audio duration on the Best tier.
What inputs does Transcribe Audio require?
Required: Audio URL. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if AssemblyAI returns an error?
The run history shows the failed step with its input and the error message AssemblyAI returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Transcribe Audio support batch operations?
Run Transcribe Audio inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within AssemblyAI's rate limits.
More actions
Other AssemblyAI actions.
Action
Get Transcript
Returns the transcript by ID with the full text, word-level timestamps, speaker labels (if diarization was on), sentiment per utterance (if enabled), and the AI-generated summary. Poll until status=completed or pair with the transcript-ready webhook.
ActionLeMUR Task on Transcript
Runs an LLM task (summarise, Q&A, extract structured data) against one or more completed transcripts. Saves the chain of "fetch transcript → LLM call" by bundling both server-side. Useful for "summarise this call, extract action items as JSON" post-call workflows.