← All guides

Automation integrations

Transcripts are most useful inside a pipeline — summarize new uploads to Slack, archive a channel to Notion, or feed a vector database.

n8n

1. Download the VidWords n8n workflow template.
2. In n8n: Workflows → Import from file.
3. Open the HTTP Request node and set the Authorization: Basic <your-api-token> header (token on your profile page).
4. Trigger it on a schedule, a webhook, or an RSS feed of a channel's uploads.

Make.com

1. Download the Make blueprint.
2. In Make: Create a new scenario → ⋯ → Import blueprint.
3. Fill in your API token in the HTTP module, then map the results[].text field to any downstream app — Google Docs, Notion, Slack, Airtable.

Plain REST (everything else)

Anything that can issue an HTTP POST can use the API directly — Zapier webhooks, GitHub Actions, cron jobs:

curl -X POST https://vidwords.com/api/transcripts \
  -H "Authorization: Basic YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"ids": ["jNQXAC9IVRw", "dQw4w9WgXcQ"], "lang": "en"}'

Up to 50 video ids per call, 5 requests / 10 seconds. Full reference with Node and Python examples in the API docs, machine-readable spec at /openapi.json.

Recipe ideas

• New-upload digest: RSS trigger → transcript → AI summary → Slack/email.
• Research archive: weekly channel sweep → transcripts → Notion database.
• Content repurposing: transcript → blog-post draft → CMS.

Read the API docs →