n8n transcription integration

For engineers who self-host their automation layer and want the audio to stay on infrastructure they control. The job: run the whole pipeline on your own box: watch a folder, submit, poll for the result, post the transcript onward.

Wiring it up

1 · Trigger

Any of these start the run:

• Local File Trigger
• S3 Trigger
• Webhook node

2 · Submit from HTTP Request node

# submit — returns immediately, does not block
curl -X POST https://whipscribe.com/api/v1/transcribe/url \
  -H "X-API-Key: $KEY" \
  -H "Idempotency-Key: n8n-$FILE_ID" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com/recording.mp4",
       "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"}

3 · Collect

Poll from a Wait node, or move polling to a scheduled run once volume grows.

# one job, every format — never re-submit per format
curl "https://whipscribe.com/api/v1/jobs/$JOB/result?format=txt" -H "X-API-Key: $KEY"
curl "https://whipscribe.com/api/v1/jobs/$JOB/result?format=srt" -H "X-API-Key: $KEY"
curl "https://whipscribe.com/api/v1/jobs/$JOB/result?format=vtt" -H "X-API-Key: $KEY"

What your key can actually do

What it costs to run

$24 per 5,000 minutes — about $0.29 an audio hour — and credits never expire.

Why run it here

Recipes that use n8n

Use cases with n8n