How does the n8n sync template work?

The sync workflow starts with a Manual Trigger, defines the V2 request fields in a Set node, posts to `/api/v2/transcribe`, and normalizes the transcript result for later n8n nodes.

What does the n8n async template expect?

The async template exposes a POST webhook endpoint in n8n. Use that endpoint as `webhook_url` in long-running transcript jobs so the V2 worker posts the completion payload back into n8n.

Can I keep the API key in an environment variable?

Yes. The starter workflow uses `YT_TRANSCRIPT_API_KEY` in the Authorization header expression, and you can replace it inline if you prefer a direct credential for the first import.

n8n Templates

Choose one flow, copy the JSON, import it into n8n, replace placeholders, and test with one request.

/api-docs get-api-key

Choose Flow

Sync RequestAPI v2

Sync Request

Manual-trigger n8n workflow that builds the V2 request body, calls `/api/v2/transcribe`, and normalizes the transcript fields for follow-up nodes.

Paste into n8n workflow import.

Quick steps

Paste this JSON into n8n workflow import.

Replace the API key and request defaults.

Run one small sync request and confirm the response shape.

Sample V2 Request Body

{
  "video": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
  "language": "en",
  "source": "auto",
  "format": {
    "timestamp": true,
    "paragraphs": false,
    "words": false
  }
}