Post Videos to TikTok, Reels, and Shorts from One Workflow
You made a short-form video. Now you need it on TikTok, Instagram Reels, YouTube Shorts, LinkedIn, Facebook, and X. Each platform has a different upload API, different authentication, and different required fields. Building separate integrations for each one takes days and breaks often.
This is one of the most requested workflows on the n8n forum and Make.com forum. Users want one workflow that takes a video URL and publishes it everywhere. Here is how to build that.
Why cross-platform video posting is hard without Blotato
Each platform requires a different approach:
TikTok has no native module in Make.com. On n8n, the TikTok API requires developer app approval that many users report getting rejected. The upload flow requires chunked uploads and a multi-step "publish" confirmation.
Instagram Reels requires the Facebook Graph API with a two-step process: create a video container, wait for processing, then publish. Video processing takes 30-120 seconds, so you need polling logic.
YouTube Shorts uses the YouTube Data API v3 with OAuth2. Videos under 60 seconds with a vertical aspect ratio appear as Shorts. You need to handle title, privacyStatus, and subscriber notifications.
X (Twitter) requires OAuth1 for media uploads, which n8n has deprecated. Image and video posting through n8n's native X node is broken for many users.
LinkedIn has a separate video upload flow from images, requiring a pre-registered upload URL, a binary PUT request, then a post creation referencing the uploaded asset.
Facebook needs a pageId, and video uploads go through a different endpoint than image uploads.
Building and maintaining six separate integrations means six points of failure.
The unified approach: one API, all platforms
With the Blotato Publish API, each platform publish is one POST request. The video URL goes in mediaUrls. Blotato handles the platform-specific upload, processing, and publishing.
For Instagram Reels, change platform and targetType to "instagram" and add "mediaType": "reel" in the target. For YouTube Shorts, set "youtube" and include title and privacyStatus. Same video URL. Same API. Same authentication.