n8n and Blotato: inspect the distribution route before repeating it

Start with one identifiable video record

The 15 July 2025 tutorial combines n8n, Blotato and Airtable for multi-platform video distribution. It names YouTube, Instagram, Facebook, TikTok and Twitter among the destinations. The title says nine platforms while the description also says seven-plus; use the actual connected account list rather than either headline count to define your own batch.

1. Use the retained product link: https://blotato.com/?ref=luke.
2. Follow the workflow demo at 0:44, node explanation at 3:00 and Airtable sequence at 5:00.
3. Choose one test record and identify its video file, caption and intended destination accounts before starting the upload.

Inspect account IDs, credentials and the media upload

Account connections appear at 7:58 and the Blotato API upload at 10:46. A correctly uploaded file is not yet a published post. The next stage needs the right account identifiers and a payload that describes the intended content; an apparently successful request can still target the wrong destination if the mapping is wrong.

1. Follow the recorded API setup, keeping keys private and account IDs clearly associated with the correct profiles.
2. Compare the JSON payload’s media and destination fields with the selected Airtable record.
3. Inspect the upload response and verify that the next step uses the intended uploaded media rather than an earlier item.
4. Keep failures and pending uploads separate from completed delivery so a retry does not create an unwanted duplicate.

Verify each platform result before recurring distribution

Posting to YouTube, Facebook and LinkedIn starts at 13:39. Platform-specific delivery should be checked independently: a success on one account does not establish success on the others. The description offers a community workflow but gives no direct template download URL; use the original recording for that retrieval route.

1. Confirm each intended account and inspect its actual post, media and caption after the run.
2. Record the publication result per destination and check existing receipts before retrying an uncertain outcome.
3. Only repeat the workflow after one complete batch has been reviewed, preserving explicit release timing and destination choices.
4. Check current platform support and service terms separately; historical “hourly” and zero-cost promotional title variants are not evidence of unattended reliability or present pricing.

The takeaway

The useful system maps one approved video to the correct accounts and produces inspectable delivery evidence for every destination.