Two ready-made n8n workflows for VimeoClip
One workflow sends a link and gets clips back on a webhook. The other follows a YouTube channel, sends clips to Telegram for approval, then schedules them. The JSON files ship with the source in examples/n8n.
The two templates
openshorts-clip-and-notify.json
A form takes a video link, one request starts the job, and one webhook takes the result. There is no wait loop.
- Video URL form takes the link.
- Start OpenShorts job calls POST /api/process with webhook_url and webhook_secret.
- Clips ready (webhook) takes the result, and Job completed? splits success from failure.
- One item per clip makes each clip an item you can pass to Slack, email or Google Sheets.
openshorts-content-machine.json
A 35-node workflow that follows a YouTube channel, in four parts.
- Watch: once a day it reads the channel RSS and picks one video, new uploads first, then unprocessed older videos.
- Approve: each clip reaches Telegram with Publish and Skip buttons.
- Schedule: an approved clip takes the next free day, one post a day, based on the real queue from GET /api/social/scheduled.
- Report: on Sunday it reads numbers from GET /api/social/analytics/impressions and /posts and sends a digest.
What you need
- Access to the source, to get the JSON files in examples/n8n.
- An n8n with a public URL. VimeoClip refuses a webhook_url pointing at localhost or a private IP.
- Enough credits, because every video a workflow sends is a job. Content Machine sends one video a day.
- For Content Machine: an admin account, an Upload-Post key on the server, a Telegram bot, and n8n on https so Telegram can register the buttons.
Shared setup
These steps apply to both workflows.
Import the workflow
In n8n choose Workflows, Import from file, then pick the JSON file.
Change the server address
The JSON points at a different host. Change the URL in each HTTP Request node to your host: 1 node in clip-and-notify, 5 nodes in content-machine.
Create the credential
Create a Header Auth named OpenShorts API key, with Name set to Authorization and Value set to Bearer plus a session token. The notes in the workflow mention osk_ keys, which this build does not have.
Paste the webhook URL
Open the Clips ready (webhook) node, copy the production URL and paste it as webhook_url in the Start OpenShorts job node.
Change webhook_secret
Replace change-me with your own string.
Get a session token for the credential
The token lives 30 days. When it expires the workflow gets 401 and you need to update the credential.
curl -s -X POST "$BASE/api/auth/login" \
-H "Content-Type: application/json" \
-d '{"email":"you@example.com","password":"YOUR_PASSWORD"}' | jq -r .access_tokenExtra edits for Content Machine
The original workflow assumes the server knows the posting profile. It does not, so you pass the Upload-Post profile name.
| Node | What to change |
|---|---|
| Settings | Fill in youtube_channel_id and telegram_chat_id. |
| Settings (clips), Settings (weekly) | Fill in telegram_chat_id. |
| Schedule social post | Add user_id to the JSON body. |
| Read publishing queue, Weekly impressions, Per-post metrics | Add a user query parameter with the Upload-Post profile name. |
Without a profile name these routes return 400 "Missing Upload-Post user profile". The Upload-Post key comes from UPLOAD_POST_API_KEY on the server.
Body of the Schedule social post node
Keep the n8n expressions and add only the user_id line.
{
"job_id": "{{ $json.job_id }}",
"clip_index": {{ $json.clip_index }},
"user_id": "YOUR_UPLOAD_POST_PROFILE",
"platforms": ["tiktok", "instagram", "youtube"],
"scheduled_date": "{{ $json.scheduled_date }}",
"timezone": "UTC"
}What to know when it runs
A few behaviors of the two templates differ from what the notes in the files suggest.
- Neither template checks the webhook signature. To check it, compute the HMAC over the raw body. Recomputing from JSON.stringify of the parsed body will not match, because VimeoClip signs a string with spaces after commas and colons.
- Clip links in the webhook need a token, so Telegram cannot fetch them directly. Send clip for approval will fail and hand over to Send clip link instead, so you get a message with a link in place of the video.
- Content Machine remembers processed videos in n8n static data. That data only persists on production runs, not on test runs in the editor.
- If VimeoClip refuses a job, the video stays unmarked and is retried the next day. The workflow tells you on Telegram through the Notify: out of minutes node.
Frequently asked questions
In the examples/n8n folder of the source. The repo for this build is private, so you need to be granted access.
No. Content Machine only schedules a clip when you press Publish in Telegram.
Yes, but webhook_url must still be a public address. VimeoClip checks the DNS of the URL and refuses every private address.
Know what the workflow receives
The webhook page covers each field, the retries and how to verify the signature.
Illustration (stock video), not VimeoClip output · Storyblocks




