--- title: "AWS Transcribe Integration" description: "Convert speech in audio and video into text with Amazon Transcribe. Start and manage asynchronous S3-based transcription jobs and custom vocabularies from inside a flow." url: https://flowrunner.ai/integrations/aws-transcribe date_modified: 2026-08-07T17:20:23-07:00 --- # AWS Transcribe [AI](https://flowrunner.ai/integrations/category/ai-llms) Convert speech in audio and video into text with Amazon Transcribe. Start and manage asynchronous S3-based transcription jobs and custom vocabularies from inside a flow. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 8 actions · API key · available [AWS Transcribe website](https://aws.amazon.com/) · [Platform Documentation](https://docs.aws.amazon.com/transcribe/) · Capability data verified 2026-07-14 1. New sales call recording lands in S3 2. Agent starts a transcription job with the product custom vocabulary 3. Agent reads the completed transcript when the job finishes 4. Agent scans the transcript for commitments and follow-up items 5. Agent files the transcript and action items against the deal record 6. Rep gets the summary and the follow-ups in Slack 7. A transcript mentioning a contract change or complaint routes to a manager ## What This Integration Enables Transcribe makes spoken conversations usable. It runs a transcription job against audio or video in S3, applies a custom vocabulary so your specific terms come back right, and returns text you can search, summarize, and route. Managing jobs and vocabularies from inside a flow means transcription happens the moment a recording lands, not when someone gets around to it. A transcript on its own is just more text to read. The point is what the flow does next: extract the follow-ups, file them against the right record, and surface the moments that need attention. An orchestration layer turns a transcript into action items and escalations, and FlowRunner is built for that layer. ### Without FlowRunner **Calls not searchable**: Recorded calls sit as audio nobody can find later **Notes taken by hand**: Someone listens back and types out what was said **Terms transcribed wrong**: Product and domain names come back garbled ### With FlowRunner **Audio made text**: Every recording becomes a searchable transcript **Action items extracted**: Follow-ups pulled from the transcript automatically **Vocabulary honored**: Custom terms and product names transcribe correctly ## Use Case Scenarios ### Sales Call Follow-Up A sales call recording lands in S3. The agent starts a transcription job with the product custom vocabulary so model names come back correct, reads the transcript when the job finishes, and extracts the commitments and follow-up items. It files everything against the deal record and sends the rep a summary. The rep gets accurate follow-ups without listening back to the call. ### Meeting Record Keeping Recorded meetings need a durable, searchable record. The agent transcribes each recording, produces a summary with decisions and owners, and stores it where the team can find it. Meetings that used to vanish into a recording nobody replays become a searchable archive, and decisions are captured without a dedicated note-taker. ### Voicemail Triage Customer voicemails accumulate in a shared line. The agent transcribes each one and reads the intent. Routine messages are logged and routed by topic. A voicemail that mentions a cancellation, a complaint, or an urgent request is flagged and sent to a person immediately, so the messages that matter do not wait in a queue. ## Human-in-Loop Highlight A transcript can surface something that needs a real response: a complaint, a contract change, a commitment someone made on a call. When the agent detects that in the text, FlowRunner routes it through a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step rather than filing it silently. The agent pauses, assembles the relevant passage and the surrounding context, and sends it to the right manager via Slack. A person reads what was actually said and decides. Transcription handles the volume; a human handles what the words mean. Agent processes routinely Detects that in the text Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 8 actions ### Transcription Jobs 4 - **Start Transcription Job** Starts an asynchronous transcription job for an audio or video file already stored in Amazon S3. - **Get Transcription Job** Retrieves the current status and details of a transcription job. When the job status is COMPLETED, the result includes the TranscriptFileUri where the transcript JSON is stored. - **List Transcription Jobs** Lists transcription jobs in your account, most recent first. Optionally filter by status or by a substring of the job name, and page through results using the returned cursor. - **Delete Transcription Job** Permanently deletes a transcription job and its metadata. This does not delete any transcript file already written to your own S3 output bucket. ### Custom Vocabularies 4 - **Create Vocabulary** Creates a custom vocabulary to improve transcription accuracy for domain-specific terms, names, and acronyms. - **Get Vocabulary** Retrieves information about a custom vocabulary, including its processing state (PENDING, READY, or FAILED) and a temporary download URI for the vocabulary contents when available. - **List Vocabularies** Lists the custom vocabularies in your account. Optionally filter by processing state or by a substring of the vocabulary name, and page through results using the returned cursor. - **Delete Vocabulary** Permanently deletes a custom vocabulary. Any in-progress transcription jobs already using it are unaffected, but it can no longer be applied to new jobs. ## Frequently Asked Questions ### What can FlowRunner do with AWS Transcribe? FlowRunner agents can run Start Transcription Job, Get Transcription Job, and List Transcription Jobs in AWS Transcribe, plus 5 more actions. ### Does connecting AWS Transcribe to FlowRunner require OAuth? No. AWS Transcribe connects to FlowRunner with an API key, no OAuth flow required. ### Can AWS Transcribe trigger a FlowRunner workflow automatically? AWS Transcribe doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at AWS Transcribe?** This integration exposes AWS Transcribe to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/aws-transcribe. Site index: https://flowrunner.ai/llms.txt