Integration

There is no clipsdk app on Zapier, and Webhooks by Zapier covers it: a Custom Request starts the job and a Catch Hook Zap receives the clips. An 8-minute speech costs about $0.24 at $0.03 a source minute.

Zapier for video clips: one Custom Request in, 3 ranked clips back in under 90 seconds

It takes two Zaps: the first sends a file link to clipsdk, the second wakes up when the finished job arrives.

Updated

Or one API call

$0.03per source minute

  • Every clip included, up to 1080p60 and 20 Mb/s
  • $1 free to start, 33 minutes of video
  • Prepaid credit, no subscription
See pricing

Custom Request settings

Custom Request settings
FieldValue
App and eventWebhooks by Zapier, Custom Request
MethodPOST
URLhttps://api.clipsdk.com/v1/clips?wait=0
DataRaw JSON: video_url from your trigger, clips, captions and webhook_url set to the Catch Hook URL
HeadersAuthorization: Bearer csdk_live_..., Content-Type: application/json
ReplyThe job, with its id and status, at once

Source: Zapier: Send webhooks in Zap workflows, checked 7 November 2026

Build it in Zapier

Webhooks by Zapier is a premium app, so both Zaps need a paid Zapier plan or the trial (Zapier help). Build the catching Zap first: the sending Zap needs its URL.

  1. Create the catching Zap

    Trigger: Webhooks by Zapier, event Catch Hook. Copy the webhook URL Zapier shows. Catch Hook parses the JSON body, so the job's fields can be mapped later. Pick Catch Raw Hook instead if you need the headers to check Clipsdk-Signature: it keeps the body unparsed, max 2 MB (Zapier help).

  2. Add a Custom Request to the sending Zap

    After your trigger (a new file, row or form entry with a direct https link to the video file), add Webhooks by Zapier, event Custom Request. Method POST, URL https://api.clipsdk.com/v1/clips?wait=0. Custom Request sends the Data exactly as you type it, so keep it valid JSON (Zapier help).

    Data
    {
      "video_url": "<file link from your trigger>",
      "clips": 3,
      "captions": "minimal",
      "webhook_url": "https://hooks.zapier.com/hooks/catch/..."
    }
  3. Add the headers

    In Headers, add Authorization with Bearer plus your key, and Content-Type with application/json. Leave Basic Auth empty (Zapier help).

  4. Use the clips in the catching Zap

    Add a Filter by Zapier step that only continues when event is job.succeeded: a failed job arrives with job.error and no clips. Then add the action that posts or stores the clips. Each clip in job carries its video link, title, score and post_caption, ready to map into Slack, Drive, Sheets or a scheduler (Zapier: Webhooks by Zapier).

The request the Custom Request sends

Same Data as the Zap, with the speech we ran it on. Your Catch Hook URL goes in webhook_url; our run used a test catcher. Try it opens New clips with the same video and settings.

POST/v1/clipsTry it
curl https://api.clipsdk.com/v1/clips \
  -H "Authorization: Bearer $CLIPSDK_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "video_url": "https://api.clipsdk.com/f/lib/demo/artemis-moon-speech.mp4",
    "clips": 3,
    "captions": "minimal",
    "webhook_url": "https://hooks.zapier.com/hooks/catch/..."
  }'
Clip 1: The Generation That Will Reach Mars, 22 seconds.

Why two Zaps and ?wait=0

A clips job takes minutes: clipsdk transcribes the video, ranks the moments, follows the speaker and renders each clip. ?wait=0 makes clipsdk answer at once with the job id, so the Custom Request step finishes right away instead of waiting on the render.

When the job is done, clipsdk POSTs it to your Catch Hook URL and the second Zap runs. No polling, no Delay steps, no task spent asking whether it is ready.

What the catching Zap receives

One POST with event set to job.succeeded or job.failed and the full job, the same object GET /v1/jobs/{id} returns. Each clip has a title, a score from 0 to 100, start and end times, a post caption, an MP4 link, a poster and SRT and VTT files. The links work for 7 days without a key.

Checking an HMAC signature in a Zap takes a code step. The simpler guard: add a Custom Request that calls GET https://api.clipsdk.com/v1/jobs/{id} with your key and trust that answer. The webhooks docs explain Clipsdk-Signature for code that can check it.

What our run returned

We sent this exact request with an 8-minute NASA speech about Artemis and a test catcher in place of the Zapier URL. The webhook arrived in under 90 seconds, on the first attempt, with 3 clips in minimal captions:

  • The Generation That Will Reach Mars: score 92, 22 seconds
  • Why Mars is Calling Humanity: score 88, 24 seconds
  • Why We Do the Hard Things: score 82, 33 seconds

What it costs

clipsdk bills $0.03 per source minute, and $0.02 past 2,000 minutes a month. That speech runs just under 8 minutes, so about $0.24 at list price. Zapier counts its own tasks on top. New accounts get $1 of free credit, enough for 33 minutes, and clips carry no watermark. See pricing.

Each account runs 3 jobs at once and 200 a day. A Zap that fires on a bulk import gets a 429 with Retry-After past that, so space the files out.

Questions, answered

Is there a clipsdk app on Zapier?

No. Webhooks by Zapier does both halves: Custom Request starts the job and Catch Hook receives it. Nothing to install and no app connection to approve.

Do I need a paid Zapier plan?

Yes. Zapier lists Webhooks by Zapier as a premium app, and premium apps need a paid plan or the trial. clipsdk itself starts with $1 of free credit.

Can the Zap send a YouTube or Twitch link?

No. clipsdk needs the file itself: a direct https link to an MP4, MOV, WebM or MKV, up to 3 hours or 5 GB. Page links are refused, so map a file link from Dropbox, Drive, S3 or your own storage.

What if the catching Zap is off when the job finishes?

clipsdk tries 5 times: at once, then after 10 seconds, 1 minute, 5 minutes and 30 minutes. After that the job still waits for you: `GET /v1/jobs/{id}` with the key that started it returns it, and the clip files stay up for 7 days.

Start free

Your back catalog is full of shorts

Your first $1 is free: 33 minutes of video, every clip included up to 1080p60 and 20 Mb/s.

Two studio microphones on a desk in a dark room lit by a red glow