Do I need a developer to set this up?

No. Every step uses the built-in Webhooks by Zapier action or trigger. You paste your FaithTranscripts API key once, copy a URL, and Zapier handles the rest.

Where do I store my API key?

Create a Zapier connection with a custom header Authorization: Bearer ft_live_YOUR_KEY. Zapier encrypts the value and reuses it across every Zap in your workspace. Rotate keys from FaithTranscripts Settings → API Keys any time.

How do I receive the cleaned transcript back?

Add a second Zap whose trigger is Webhooks by Zapier → Catch Hook. Paste that URL into FaithTranscripts Settings → Webhooks. Every time a transcript or AI pass finishes, we POST signed JSON to Zapier and your Zap runs automatically.

Is the webhook payload signed?

Yes. Every delivery includes an X-FT-Signature header that is an HMAC-SHA256 of the raw body using your endpoint's signing secret. Zapier's Catch Hook forwards the headers, so you can verify them in a Code by Zapier step if you want defense in depth.

Can I also run the AI validation pass from a Zap?

Yes. Add options.ai_pass.enabled = true to the POST body in step 2, or call POST /api/v1/transcripts/{id}/ai-pass from a separate action. Wait for the ai_pass.completed webhook event before routing downstream.

What happens if a step fails?

Zapier retries automatically and surfaces failures in your task history. FaithTranscripts webhooks retry up to 5 times with exponential backoff (10s, 1m, 10m, 1h, 6h), and you can replay any delivery from Settings → Webhooks.

FaithTranscripts + Zapier

Automate sermon transcript cleanup with Zapier.

Clean captions land in YouTube. Polished transcripts land in Google Docs. Zero copy-paste — powered by a single Zap connecting the tools you already use.

See the 3-step setup Read the API docs

Diagram: a YouTube upload flows into FaithTranscripts, which hands the cleaned transcript to Zapier, which delivers it to Google Docs.

How it works

Three steps, start to finish

Create an API key

In Settings → API Keys, click Create API key and copy the value. In Zapier, set up a reusable connection with a custom header Authorization.

Authorization: Bearer ft_live_YOUR_KEY

Authentication reference

Send transcripts to FaithTranscripts

Pick any Zapier trigger — New Video in YouTube, New File in Dropbox, New Item in RSS — then add a Webhooks by Zapier → Custom Request action that POSTs the source to the FaithTranscripts API.

POST https://www.faithtranscripts.com/api/v1/transcripts
Content-Type: application/json
Authorization: Bearer ft_live_YOUR_KEY

{
  "source_type": "youtube",
  "url": "{{trigger.videoUrl}}",
  "title": "{{trigger.title}}",
  "options": { "ai_pass": { "enabled": true } }
}

Full request spec

Deliver the cleaned transcript

Create a second Zap triggered by Webhooks by Zapier → Catch Hook. Paste the URL into Settings → Webhooks. Route the JSON payload to Google Docs, Notion, your CMS, or anywhere else.

POST /hooks/ft HTTP/1.1
X-FT-Event: transcript.completed
X-FT-Signature: 3ac15e2dfa...

{
  "id": "tr_01HW...",
  "status": "completed",
  "content": "…cleaned transcript…",
  "changes_summary": { "total": 42, "by_category": { "bible": 15 } }
}

Webhook headers & signing

Build your pipeline

Connect any source to any destination

Trigger on new audio or text from

New YouTube upload
New Dropbox file
New Google Drive file
New Podbean episode
New Buzzsprout episode
New RSS item
New row in Airtable
New event in Calendly

Deliver the cleaned transcript to

Google Docs
Notion
WordPress
Substack
Airtable
Mailchimp
Slack alert
Team email digest

Developer docs

For engineers on your team

Quickstart

Send your first transcript and see a corrected response in under five minutes.

/docs/api/quickstart

Authentication

API key format, header usage, and how to rotate or revoke keys from the dashboard.

/docs/api/authentication

Webhooks

Event types, HMAC signature verification, retries, and replay from Settings.

/docs/api/webhooks

Sync, poll, or webhooks

Choose the right interaction pattern for every workflow in your pipeline.

/docs/api/async

FAQ

Frequently asked questions

No. Every step uses the built-in Webhooks by Zapier action or trigger. You paste your FaithTranscripts API key once, copy a URL, and Zapier handles the rest.