AWS TRANSCRIBE n8n INTEGRATION: AUTOMATE AWS TRANSCRIBE WITH N8N

The Create transcriptionJob action is your starting point for any transcription workflow—it's how you submit audio or video files to AWS Transcribe for processing. When you need to convert speech to text at scale, this action lets you programmatically initiate transcription jobs without touching the AWS console.

Key parameters to configure:

• Credential to connect with: Select your AWS IAM account from the dropdown. This is required and determines which AWS account processes the transcription.
• Job Name: A unique text identifier for your transcription job. This is required and must be unique within your AWS account. Use descriptive names like "podcast-ep42-2024-01-15" for easy tracking.
• Media File URI: The S3 URI pointing to your audio or video file (e.g., s3://my-bucket/recordings/meeting.mp3). This is required and must be accessible by your IAM user.
• Detect Language: An optional toggle that enables automatic language detection. Useful when processing multilingual content or when you're unsure of the source language.
• Language: If language detection is disabled, specify the language here. Defaults to "American English" but supports dozens of languages and dialects.
• Options: Additional configuration options for advanced use cases like custom vocabularies, content redaction, or speaker identification.

Practical use cases: Trigger a transcription job whenever a new audio file is uploaded to S3 (combine with S3 trigger node); process Zoom recordings by extracting the download URL and submitting for transcription; batch-create multiple transcription jobs from a spreadsheet of audio file URLs.

The Get transcriptionJob action retrieves the status and results of a specific transcription job. This is essential for checking whether your transcription has completed and fetching the actual transcript text once it's ready.

Key parameters to configure:

• Credential to connect with: Your AWS IAM account dropdown selection. Required for authentication.
• Resource: Set to "Transcription Job" to specify you're working with transcription resources. Required.
• Operation: Defaults to "Get" for retrieving a single job. Required.
• Job Name: The exact name of the transcription job you want to retrieve. This must match the name you used when creating the job. Required.
• Return Transcript: A toggle that determines whether the actual transcript text is included in the output. When enabled, you get the full transcription result; when disabled, you only get job metadata and status. Optional but typically enabled.
• Simplify: When enabled, this toggle streamlines the output for easier processing, removing nested AWS metadata you likely don't need. Optional but recommended for cleaner data.

Practical use cases: Poll a transcription job status in a loop until completion, then process the results; retrieve a specific transcript for quality review before publishing; check job status as part of a scheduled workflow that processes completed transcriptions.

The GetAll transcriptionJob action retrieves multiple transcription jobs from your AWS Transcribe account in a single request. This is invaluable for building dashboards, processing batches of completed transcriptions, or auditing your transcription activity.

Key parameters to configure:

• Credential to connect with: Your AWS IAM account selection from the dropdown. Required.
• Resource: Set to "Transcription Job" to work with transcription resources. Required.
• Operation: Set to "Get Many" to retrieve multiple jobs. Required.
• Return All: A toggle that, when enabled, fetches every transcription job in your account without limits. Optional—be cautious with large job histories as this can return significant data.
• Limit: When Return All is disabled, this number field controls how many jobs to retrieve. Defaults to 20, which is sensible for most use cases. Optional.
• Filters: An expandable section where you can add criteria to narrow down results—for example, filtering by job status (COMPLETED, FAILED, IN_PROGRESS) or by creation date range. Optional but highly useful for targeted queries.

Practical use cases: Build a daily report of all completed transcriptions from the last 24 hours; create a cleanup workflow that identifies and deletes failed jobs older than 30 days; populate a dashboard showing transcription job statuses across your team's workflows; process all completed jobs in a batch, extracting transcripts for downstream analysis.

The Delete transcriptionJob action removes a transcription job from your AWS Transcribe account. While AWS doesn't charge for storing job metadata, cleaning up completed or failed jobs keeps your account organized and makes it easier to find relevant transcriptions.

Key parameters to configure:

• Credential to connect with: Select your AWS IAM account from the dropdown. Required for authentication.
• Resource: Set to "Transcription Job" to specify the resource type. Required.
• Operation: Set to "Delete" to remove the specified job. Required.
• Job Name: The exact name of the transcription job to delete. Required—double-check this value since deletion is permanent.

Practical use cases: Automatically delete transcription jobs after successfully extracting and storing the transcript elsewhere; create a maintenance workflow that removes jobs older than 90 days to maintain a clean job list; delete failed jobs after logging the error for troubleshooting.