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.
Every file that arrives is text within minutes, with no one involved.
The flow
- TriggerDrive push notification, or a folder-watch module.
- SubmitConnect Drive with OAuth so we fetch the file directly — a share link is a preview page, not media.
- 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"}
What it costs
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.
Build it on
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