Connector library

Implemented source AI & Language

Amazon Transcribe connector.

Start S3 audio transcription jobs, retrieve job status and transcript locations, and list jobs using native AWS APIs.

Connector download

Download Amazon Transcribe

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
0.1.0.0
Release
2026-10-04
Package
Implemented source
Schema credentials
AWS
Package size
11 KB
SHA-256
ab726d40dc8882224f8da80c6c7b4104d34fce85dfba9051540f578bb5be87be
Notes
Read release notes

Included in this version

Included actions

Implemented in v0.1.0.0. Use a separate flow trigger; no webhook trigger is included.

StartTranscriptionJob

Submit one confirmed S3 batch job; acceptance is not transcript completion.

GetTranscriptionJob

Get job state and stable transcript location without fetching audio or transcripts.

ListTranscriptionJobs

Read one bounded page of job summaries and a continuation token.

Vendor API

API and access

Implementation considerations
  • Native AWS JSON actions use managed AWS credentials and SigV4. Temporary credentials require their session token; hosted mapping must be verified.
  • Input audio must be in S3 in the request region. Required output bucket and exact .json key need AWS write permission; use a unique key because existing output can be overwritten.
  • Acceptance does not prove transcription completion. Failed jobs remain failed even when their status lookup succeeds.
  • Uncertain submissions must be verified using the same job name before retrying. No automatic retries or unbounded polling.
  • Transcript audio and JSON are not downloaded. Presigned query-bearing transcript URLs are omitted; retrieve stable output using an authorized S3 action.
  • No streaming, medical transcription, Call Analytics, custom models or job deletion. Normal TLS, canceled 1–8 second budgets and bounded responses apply.
  • New identity coexists with the preserved legacy adapter. Hosted import, saved mappings and live AWS calls remain untested.
  • New native AWS API connector with an independent identity; the preserved legacy adapter is not an upgrade target. Local validation passed; hosted import, credential mapping and live AWS calls remain untested.

Support

Need help with Amazon Transcribe?

Tell us what you need to connect or change.