Publish videos from n8n

What it can do

• Publish or schedule videos, photos and text from any n8n workflow – for example when a new file lands in a cloud folder or a spreadsheet row is marked "ready".
• Get results back with the Webhook trigger: one event per platform with the post URL or the error.
• Reuse Upload-Post workflows: if your workflow already calls Upload-Post, only the URL and the key change.
• Works with n8n cloud and self-hosted n8n.

Honest note: there is no "Video Automation" node in n8n's node list. The generic HTTP Request node does everything our API offers.

Limits

• The limits of your plan apply (requests per minute, uploads per month).
• Large videos: n8n keeps binary data in memory or on disk depending on its settings. For files over a few hundred MB, send a public video URL instead of the file.
• Synchronous uploads can take up to about a minute; set the node timeout to at least 120 seconds or use async_upload=true with a webhook.

Setup

1. In our app create an API key under API & webhooks.
2. In n8n add an HTTP Request node:
   • Method POST, URL https://my-video-automation.com/api/upload
   • Authentication: Generic → Header Auth, name Authorization, value Apikey YOUR_KEY
   • Body content type: Form-Data (multipart)
   • Fields: user = your profile name, platform[] = youtube (add one platform[] field per platform), title = your title, video = the public video URL – or, as an n8n binary field, the file itself
   • Optional: scheduled_date (e.g. 2026-12-01T12:00:00) and timezone (Europe/Berlin), async_upload = true
3. Run the node once; the answer contains request_id or job_id.
4. For results, create a second workflow with a Webhook trigger (POST). Copy its production URL and add it in our app under API & webhooks → New webhook.
5. Optional: check the signature in a Code node (see webhooks).

More: API and keys.

FAQ

My existing Upload-Post node workflow – what do I change?

Only the URL (api.upload-post.com → my-video-automation.com) and the key in the header.

How do I send to several platforms?

Add the field platform[] several times, once per platform.

Can I use the REST API v1 instead?

Yes. Send JSON to /v1/posts with Authorization: Bearer YOUR_KEY; media go in media_urls.