Package Exports
- n8n-nodes-transcriptmagic
- n8n-nodes-transcriptmagic/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (n8n-nodes-transcriptmagic) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
n8n-nodes-transcriptmagic
n8n community node for TranscriptMagic — fetch transcripts from YouTube, TikTok, Instagram, and Facebook videos directly inside your n8n workflows.
Install
npm install n8n-nodes-transcriptmagicRestart n8n. The node appears under TranscriptMagic in the picker.
Setup
- Create an API key in the TranscriptMagic dashboard. Keys begin with
sk_live_. - In n8n, add a new TranscriptMagic API credential and paste your key. The credential test validates the key without consuming a credit.
Operations
Transcript
POST a video URL, get back the transcript.
| Operation | Endpoint |
|---|---|
| YouTube | POST /api/youtube/transcript |
| TikTok | POST /api/tiktok/transcript |
POST /api/instagram/transcript |
|
POST /api/facebook/transcript |
Account
| Operation | Endpoint |
|---|---|
| Get Credit Balance | GET /api/balance |
Output formats
The node exposes two output modes via Options → Output Format:
- Normalized (default) —
{ text, platform, credits, url }. Hides per-platform shape differences so the same downstream nodes work across YouTube, TikTok, Instagram, and Facebook. - Raw — the upstream API response passed through verbatim. Use this when you need YouTube's per-line timed segments or platform-specific metadata (
videoUrls,language, etc).
Error handling
- Continue on fail is supported. A bad URL in a batch surfaces as a per-item error, and the rest of the batch keeps running.
- Rate limits: when the API returns
429, the node honorsRetry-Afterand retries once. The per-key limit is 120 requests/minute.
Example workflows
A ready-to-import quickstart workflow lives in examples/quickstart.json. Below are common patterns to copy.
1. Single-URL transcription
The minimal flow: trigger → transcribe → done.
- Manual Trigger
- TranscriptMagic
- Resource:
Transcript - Operation:
YouTube(or TikTok / Instagram / Facebook) - URL: paste any public video URL
- Resource:
- Run. The output item contains
text,platform,credits, andurl.
2. Batch transcription with graceful failures
Process many URLs at once. Bad URLs surface as per-item errors without aborting the batch, and the node honors Retry-After on 429 automatically.
- Google Sheets / Airtable / Set node returning multiple items, each with a
urlfield. - TranscriptMagic node:
- URL:
={{ $json.url }} - Settings → On Error: Continue
- URL:
- Downstream Google Sheets (or any destination) to write transcripts back, keyed off the original
urlfrom the paired item.
3. Transcript → AI summary → notification
The classic insight-extraction pattern.
- Schedule Trigger (or Webhook, RSS Feed, Telegram, etc.)
- TranscriptMagic → fetch transcript
- OpenAI / Anthropic node — prompt with
={{ $json.text }} - Slack / Email / Notion → deliver the summary
4. Pre-flight balance check
Before kicking off a big batch, verify you have credits left:
- TranscriptMagic — Resource:
Account, Operation:Get Credit Balance - IF —
={{ $json.credits >= 1000 }}→ continue, else send an alert
This call does not consume a credit.