Your first multi-platform post
Set up a profile and API key, test one upload, then send the same clip to several platforms in one call.
Set up the account side first
Upload-Post works with profiles. You create a profile (for example your brand name), connect your TikTok, Instagram, YouTube and other accounts to that profile, and generate an API key in the dashboard. Every upload later names that profile in the user field, so write the exact spelling down. If the name does not match, or an account is not connected to that profile, nothing is posted there.
Test one upload before you automate
Before building anything in n8n or Make, send a single test request with a short clip. The upload endpoint takes a multipart form: the video (as a file or a public URL), the profile name, a title, and one platform[] field per destination. Repeat platform[] to post to TikTok and Instagram in the same call. Once that works, copy the same fields into an HTTP Request node, or use the verified Upload-Post community node in n8n. Store the key as a credential instead of pasting it into the node.
Write captions per platform
The title field is the default caption. You can override it per network with fields such as tiktok_title or youtube_title, which is the easiest way to give Shorts a searchable title while TikTok gets a casual hook. Note that description is only used by a few platforms (for example YouTube and LinkedIn); TikTok and Instagram read the title.
Schedule or queue
Add scheduled_date (ISO-8601) plus a timezone to publish later, or use add_to_queue to drop the post into your next free slot. You cannot use both in one request. Large files are better sent with async_upload, after which you check progress on the status endpoint instead of waiting on one long call.
Keep a posting log
If your source is a spreadsheet, mark each row as posted right after a successful upload. That one step prevents the most common automation mistake: the same video going out twice.