Cliphi + Make

A Make scenario
that ships clips

In Make, Cliphi is two HTTP modules: new video detected, clips delivered, no code.

1HTTP module: submit

POST the video URL with your Cliphi key when your trigger fires.

2Sleep, then check

Repeat a GET on the job until it completes; the moments and previews arrive in the response.

3Fan the clips out

Add a router after: review queue, storage, notifications, wherever the scenario goes next.

Create your API key All the ways to use Cliphi

Made with Cliphi

Real clips, real reach, published to YouTube Shorts, Instagram Reels, and Facebook Reels.

Make questions

No. Cliphi is plain HTTP, so Make's built-in HTTP modules handle everything. You configure a request the way you would for any other service and map the response fields into the rest of your scenario visually.

Sleep, then repeat the status check until the job is done. Long videos take a few minutes, so a scenario that submits and immediately reads the result will find nothing. The job id from the first call is all the second one needs.

Wherever the scenario already goes. A router after the Cliphi step can drop previews into a review queue, archive finished clips to cloud storage, notify a channel, or hand the links to a scheduling tool.

Yes. Each video gets its own job id, and Make's iterator handles a list of them cleanly. Cliphi processes them on its own infrastructure, so the scenario is only tracking progress rather than doing the heavy work.

Get Started

Also works from

ChatGPT Claude Claude Code Codex Cursor OpenClaw Gemini CLI n8n Zapier Grok Gemini Perplexity Hermes GitHub Copilot Replit Poe Qwen Le Chat Devin