Does this work with self-hosted n8n?

Yes — the integration only uses the built-in HTTP Request and Webhook nodes, which ship with every n8n install (self-hosted, Docker, and n8n Cloud). No community node required.

How do I store the API key securely in n8n?

Create an HTTP Header Auth credential in n8n with Name = Authorization and Value = Bearer ft_live_YOUR_KEY. n8n encrypts the credential at rest and the value never appears in workflow exports. Rotate from Settings → API Keys at any time.

How do I verify the webhook signature?

Compute HMAC-SHA256(secret, raw_body) and compare against the X-FT-Signature header using a timing-safe comparison. n8n exposes the raw body on $binary or via a Code node. The verify helper is published in the webhooks docs.

Can I retry on failures?

Yes. Configure the n8n HTTP Request node to retry on failure, and send an Idempotency-Key header so FaithTranscripts returns the original response for duplicate POSTs. FaithTranscripts webhooks also retry 5 times with exponential backoff on non-2xx responses.

Can I trigger the AI validation pass from n8n?

Yes — either set options.ai_pass.enabled = true in the initial POST or call POST /api/v1/transcripts/{id}/ai-pass from a follow-up HTTP Request node. Wait for the ai_pass.completed webhook event before routing downstream.

What about rate limits?

The default is generous (600 reads/min per org). Our 429 responses include a Retry-After header, which n8n respects automatically if you enable retry on failure.

FaithTranscripts + n8n

Self-host your transcript pipeline with n8n.

Two built-in nodes, signed webhooks, full ownership of the workflow. Wire FaithTranscripts into the automation stack your engineering team already runs on your own servers.

See the 3-node setup Read the webhooks guide

Diagram: n8n HTTP Request and Webhook nodes wired to FaithTranscripts with a signed callback delivering the cleaned transcript.

How it works

Three steps, start to finish

Store the API key as a credential

In n8n, create a new HTTP Header Auth credential. Name it FaithTranscripts. Set the header name to Authorization and the value to your Bearer token.

Name:  Authorization
Value: Bearer ft_live_YOUR_KEY

Authentication reference

POST with the HTTP Request node

Add an HTTP Request node set to POST. Select the credential from step 1, enable retry on failure, and send the source payload as JSON. An Idempotency-Key header makes retries safe.

Method: POST
URL:    https://www.faithtranscripts.com/api/v1/transcripts
Headers:
  Content-Type: application/json
  Idempotency-Key: {{$json.uniqueId}}
Body:
{
  "source_type": "youtube",
  "url": "{{$json.videoUrl}}",
  "options": { "ai_pass": { "enabled": true } }
}

Full request spec

Verify the webhook with a Code node

Add a Webhook trigger node and paste its URL into Settings → Webhooks. In a follow-up Code node, verify the HMAC signature before routing the JSON onward.

import crypto from "node:crypto";

const secret = $env.FT_WEBHOOK_SECRET;
const sig    = $input.first().headers["x-ft-signature"];
const raw    = $input.first().body;

const expected = crypto
  .createHmac("sha256", secret)
  .update(raw)
  .digest("hex");

if (!crypto.timingSafeEqual(
  Buffer.from(expected, "hex"),
  Buffer.from(sig, "hex"),
)) throw new Error("invalid signature");

return $input.all();

Webhook signing & retries

Build your pipeline

Connect any source to any destination

Trigger on new audio or text from

Cron schedule
New Google Drive file
New FTP upload
New S3 object
New RSS item
New database row
Internal CMS webhook
Manual form submission

Deliver the cleaned transcript to

Self-hosted Ghost
WordPress REST API
Notion database
Internal Postgres
Slack channel
Team Mattermost
Email via SMTP
Your own API

Developer docs

For engineers on your team

Quickstart

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

/docs/api/quickstart

Webhooks

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

/docs/api/webhooks

Processing options

Toggle the AI validation pass, set categories, pass metadata, and more.

/docs/api/options

Sync, poll, or webhooks

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

/docs/api/async

FAQ

Frequently asked questions

Yes — the integration only uses the built-in HTTP Request and Webhook nodes, which ship with every n8n install (self-hosted, Docker, and n8n Cloud). No community node required.