Webhooks action

YouTube transcripts in Zapier.

Send a YouTube URL from any Zap trigger to Threadmap and continue the automation with structured, timestamped transcript data and clear request metadata.

Setup

Connect in three steps.

Connection method: Webhooks by Zapier ยท Custom Request

  1. 01

    Choose Custom Request

    Add Webhooks by Zapier as the action and select POST.

  2. 02

    Configure authentication

    Add the Authorization and Content-Type headers. Keep your API key inside the Zap action.

  3. 03

    Map and test

    Insert a URL from the trigger, send the test, and map transcript or segments into later actions.

Working example

Custom request

A new database row, form submission, saved link, or webhook can provide the video URL. Zapier receives JSON that can be routed to a document, CRM, knowledge base, or AI action.

URL: https://threadmap.online/api/v1/transcripts
Method: POST
Headers: Authorization = Bearer tm_live_YOUR_KEY
Data: {"url":"VIDEO_URL_FROM_TRIGGER","mode":"auto"}

What comes back

Text for humans, segments for software.

Complete transcript

Use the normalized transcript field when the next step needs clean text for search, notes, analysis, or generation.

Timestamped segments

Use segment start times and duration values for citations, chapter links, clips, interfaces, or traceable AI answers.

Source metadata

Language, video duration, transcript mode, cache state, and request IDs make workflows observable and easier to debug.

Production checklist

Make the Zapier workflow reliable.

Test with a short public video before adding loops or downstream AI calls. Keep the source URL beside every stored transcript and expose request errors clearly instead of silently skipping videos.

01

Protect credentials

Keep the Threadmap credential inside Zapier or a server-side secret store. Never place a live key in a public webpage, shared document, or client-side script.

02

Handle failures

Branch on HTTP status and error code. Private videos, unavailable media, rate limits, and insufficient minutes require different follow-up actions.

03

Monitor balance

Read remaining-minute headers after successful requests or call the usage endpoint before a large batch so the workflow can pause cleanly.

04

Preserve evidence

Store the video ID and timestamped segments with transformed output. That lets reviewers trace summaries, quotations, and extracted facts back to the source.

Integration questions

Operational details

Which transcript mode should I use?

Use captions for the fastest existing subtitles, auto when you want a supported audio fallback, or transcribe when you explicitly need a fresh audio transcript.

How should Zapier retry?

Retry temporary rate-limit and service errors with a delay. Do not repeatedly retry private, unavailable, invalid, or over-limit videos without changing the input.

How is usage measured?

Successful transcript work is billed by video duration rounded up to a whole minute. Purchased credits do not expire, and failed results are not charged.

Can I process many videos?

Yes, but use controlled concurrency, inspect rate-limit headers, and preserve each request ID. For a curated YouTube playlist, the private batch importer may be simpler.

Good workflow design

Keep the source transcript before transforming it.

Save the original transcript and video URL before asking another service to summarize, translate, classify, or rewrite it. That preserves a traceable source, makes retries cheaper, and lets people return to the exact timestamp behind a claim. Respect the video creator's rights when storing, sharing, or republishing transcript content.

Need another connection?

Use the same API from any HTTP-capable tool.

See every supported workflow or open the complete endpoint reference.