Cliphi + n8n
Every new video,
clipped automatically
Two HTTP Request nodes are the whole integration: one submits the video, one collects the finished clips.
1Node 1: submit the video
POST the video URL with your Cliphi key. Trigger it from RSS, a form, a folder, anything n8n hears.
2Node 2: wait for the clips
Poll the job on a wait loop until it completes. The response lists every strong moment with previews.
3Route the results anywhere
Save previews for human review, notify a channel, or queue approved clips for posting.
Made with Cliphi
Real clips, real reach, published to YouTube Shorts, Instagram Reels, and Facebook Reels.
641Kviews
Instagram Reels
12.9Kviews
Instagram Reels
158Kviews
Instagram Reels
26Kviews
Instagram Reels
176Kviews
Instagram Reels
77Kviews
Facebook Reels
20Kviews
Facebook Reels
127Kviews
Facebook Reels
641Kviews
Instagram Reels
12.9Kviews
Instagram Reels
158Kviews
Instagram Reels
26Kviews
Instagram Reels
176Kviews
Instagram Reels
77Kviews
Facebook Reels
20Kviews
Facebook Reels
127Kviews
Facebook Reels
n8n questions
You do not need one. Two HTTP Request nodes cover the whole integration: one submits the video, one collects the results. That means no waiting for a node to be installed or approved on your instance, and it works the same on self-hosted and cloud.
Use a Wait node and loop back to the status check until the job reports completed. Cliphi is built for this: the submit call returns immediately with a job id, so nothing hangs while a two hour recording is processed.
Anything n8n can hear. An RSS feed of your podcast, a new file in a watched folder, a form submission, a webhook from your CMS, or a schedule. Cliphi only needs the video link, so whatever produces one can start the workflow.
Every moment Cliphi found, each with a preview link and its timing. That is usually the point where a workflow branches: post the previews into a channel for someone to approve, and only render the ones that get a thumbs up.
Also works from
Put clipping on autopilot
Two HTTP nodes between your trigger and your finished clips.
Building your own agent or workflow? Developer docs