Business APIsAutomations › Transcribe every new file in a Drive fol

Transcribe every new file in a Drive folder

Any team whose recordings already land somewhere shared. Files accumulate in a folder nobody opens, and the knowledge in them is invisible to search.

What you end up with

Every file that arrives is text within minutes, with no one involved.

The flow

  1. TriggerDrive push notification, or a folder-watch module.
  2. SubmitConnect Drive with OAuth so we fetch the file directly — a share link is a preview page, not media.
  3. PollStore the job_id and poll GET /api/v1/jobs/{id} from a scheduled run. Self-serve keys are Pro tier and collect by polling; signed callbacks are Enterprise.
# submit — returns immediately, does not block
curl -X POST https://whipscribe.com/api/v1/transcribe/url \
  -H "X-API-Key: $KEY" \
  -H "Idempotency-Key: transcribe-every-file-in-a-drive-folder-$SOURCE_ID" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com/recording.mp4",
       "diarize":true,
       "word_timestamps":true}'

→ 202 {"job_id":"a1b2…","status":"queued"}

# then poll — a self-serve (Pro) key collects by polling
curl "https://whipscribe.com/api/v1/jobs/$JOB" -H "X-API-Key: $KEY"
→ {"status":"processing"} … {"status":"done"}
Watch for this. Watch channels expire and have to be renewed. The OAuth connector avoids owning that lifecycle yourself.

What it costs

Rate$0.008 / min
Per audio hour$0.48
a 3-hour recording$1.44
CreditsNever expire

At $0.48 an audio hour, a year of weekly hour-long recordings costs about $25 to have in full text. $8 per 1,000 minutes — about $0.48 an audio hour — and credits never expire.

Why this needs an API rather than a person

It is the simplest automation here and usually the first one worth building, because it turns a dead folder into a searchable archive.

No subscription to size wrongCompeting transcription tools sell $25–$65 monthly plans with a minute cap that resets whether you used it or not. Credits here are bought once and do not expire, so a quiet month costs nothing and a backlog run does not need an upgrade.
Your audio is not sent to a third-party modelTranscription runs on our own GPUs in our own private cloud. Nothing is forwarded to OpenAI or any other vendor's API, which is usually the blocking question when the recordings are customer calls or unreleased material.
One job, every formattxt, json, srt, vtt and docx all come from the same job id. Re-submitting a file per format is the most common way teams pay several times for one transcription.
Built to be retriedIdempotency-Key means an automation platform's automatic retry returns the original job instead of billing a second one. Every no-code platform retries; most transcription APIs charge you for it.

Build it on

Google Driveshare links are not media URLs — use the OAuth connectorstorageMake.com40s module timeout — submit, store job_id, poll from a second scenariono-code automationZapier30s action timeout — split into a submit Zap and a scheduled poll Zapno-code automationn8nWait node works but pins a worker — split submit and poll at volumeself-hosted automation
Try the quality free, then wire it up

Your first transcript in the web app is free, any length, no card — that is how to check accuracy on your own audio before writing any code. The API itself has no free tier: a key is self-serve once your account has credit ($50 minimum, spendable on transcription, and it does not expire). $8 per 1,000 minutes — about $0.48 an audio hour — and credits never expire.

Transcribe a file free →Create an API keyAPI reference