Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.transcriptmagic.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

n8n-nodes-transcriptmagic is a community node that wraps the TranscriptMagic API as drag-and-drop operations inside n8n. Drop it into a workflow, point it at a public video URL, and the transcript flows through to the next node like any other JSON. It is published to npm and works in both self-hosted n8n and n8n Cloud (once verified).

npm package

n8n-nodes-transcriptmagic
If you’re writing a service or batch job in code, use the REST API directly. If you’re inside an AI client, use the MCP server. Use n8n when your workflow orchestration already lives in n8n.

​
Install

  1. Open Settings → Community Nodes → Install.
  2. Enter n8n-nodes-transcriptmagic and confirm.
  3. The node appears in the picker under TranscriptMagic.
n8n Cloud requires verified community nodes. If the install button is missing, the package is awaiting verification — self-host in the meantime.

​
Setup

  1. Create an API key in your TranscriptMagic dashboard. Keys begin with sk_live_.
  2. In n8n, add a new TranscriptMagic API credential and paste your key. The credential test calls GET /api/balance — it validates the key without consuming a credit, and works even on zero-credit accounts.

​
Operations

​
Transcript

POST a video URL, receive the transcript.
OperationEndpoint
YouTubePOST /api/youtube/transcript
TikTokPOST /api/tiktok/transcript
InstagramPOST /api/instagram/transcript
FacebookPOST /api/facebook/transcript
Cost 1 credit per successful call. Cache hits and errors are free.

​
Account

OperationEndpoint
Get Credit BalanceGET /api/balance
Free; useful as a pre-flight check before a big batch.

​
Output formats

Set via Options → Output Format:
  • Normalized (default) — { text, platform, credits, url }. Hides per-platform shape differences so a single downstream branch works across all four sources.
  • 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.). See the response schema.

​
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 honors Retry-After and retries once. The per-key limit is 120 requests/minute. See rate limits.

​
Common patterns

The minimal flow: trigger → transcribe → done.
  1. Manual Trigger
  2. TranscriptMagic — Resource Transcript, Operation YouTube (or TikTok / Instagram / Facebook), URL = any public video URL.
  3. Run. The output item contains text, platform, credits, and url.
Process many URLs without aborting the batch on a single bad URL.
  1. Google Sheets / Airtable / Set node returning items with a url field.
  2. TranscriptMagic — URL = ={{ $json.url }}, Settings → On Error = Continue.
  3. Downstream destination keyed off the original url from the paired item.
The node automatically honors Retry-After on 429.
The classic insight-extraction pattern.
  1. Schedule Trigger (or Webhook, RSS Feed, Telegram, etc.)
  2. TranscriptMagic → fetch transcript.
  3. OpenAI / Anthropic node — prompt with ={{ $json.text }}.
  4. Slack / Email / Notion → deliver the summary.
Before kicking off a big batch, verify you have credits.
  1. TranscriptMagic — Resource Account, Operation Get Credit Balance.
  2. IF — ={{ $json.credits >= 1000 }} → continue, else send an alert.
The balance call does not consume a credit.

Source repository

Issues, releases, and example workflows.

REST API

The underlying API the node calls — useful for advanced cases.

Authentication

How API keys work and how to rotate them.

Errors

Status codes and retry strategy.