Automation•
2 min read
•
2026-10-03 · Updated 2026-10-20

Plan a reviewed video publishing workflow in Reeling

TL;DR — Direct Answer

Move from a video draft to connected channels, a scheduled request and verified delivery across supported destinations.

By Reeling product team. Examples describe the documented implementation; no live publishing test is implied.

Prepare a reviewable draft

Start with a script, media and caption that you have permission to publish. If you use generated media, inspect the output and apply the disclosures required by the destination. Keep the original media and a record of the approved caption.

Confirm account availability

Connect destinations in the correct Reeling project. Reeling’s current Instagram flow requires an eligible professional account with tester access. TikTok inbox mode hands the video back to TikTok for completion; public Direct Post is subject to the app audit. Review the documentation before promising unattended publication.

Schedule with an explicit timezone

In the API, supply project_id, video_url, caption and platforms; use scheduled_for for a future timestamp. In the UI, verify the displayed date and timezone in the calendar. Make the publishing request only after the intended destinations and content have been reviewed.

Record results instead of assuming success

Store the returned post ID. Check processing and each platform result, and verify public destination links where available. Investigate partial failures rather than blindly repeating the whole request. Monitor accepted requests separately from confirmed publication.

Run a fixture before authorizing an agent

Clone the Reeling examples and run the account and polling scripts without flags. They return labeled synthetic output and make no account requests even if credentials exist in the environment. Inspect the tests before adding a live key.

Once the connection is understood, use --live-read to inspect the exact project and channels. Keep draft preparation separate from --publish and check the full payload before authorizing the write.

git clone https://github.com/yomariano/reeling-examples.git
cd reeling-examples
npm test
node examples/read-account.mjs
node examples/poll-status.mjs

Keep a durable record between agent steps

Save a draft identifier, the approved caption, target channel, intended timezone and returned post ID. If the assistant loses context or a tool times out, resume from that record rather than starting the upload again.

Report the actual state of each destination. A paid generation result, upload receipt and public post are different artifacts. A useful automation should explain the remaining human action when inbox delivery or account review is required.

Frequently Asked Questions

How do I build a reviewed automation pipeline for TikTok, Instagram Reels, and YouTube Shorts?

Structure your automation in two distinct tiers: (1) an agent or script generates content drafts, subtitles, and metadata, saving them to Reeling drafts; (2) a human editor or review gate approves the video, verifies platform-specific safe zones, and triggers the scheduled publication via Reeling UI, REST API, or MCP.

Why must scheduled publishing API calls include explicit timezone offsets?

Passing ambiguous timestamps (like 2026-11-05T09:00:00 without +00:00 or Z) causes server schedulers to interpret timestamps in UTC or server-local time, leading to posts publishing hours earlier or later than intended. Always pass complete ISO 8601 strings with explicit UTC or offset values (e.g. 2026-11-05T09:00:00-05:00).

What is the difference between direct TikTok publishing and TikTok Inbox delivery?

Direct publishing publishes the video immediately or at the scheduled timestamp to your public TikTok profile. TikTok Inbox delivery dispatches the video and caption as a private draft notification inside the TikTok app, requiring the creator to tap Post to complete publication, which preserves access to in-app trending audio and effects.

How should autonomous workflows maintain state across multi-step video publishing?

Store the initial draft identifier, target channel IDs, approved caption, and the returned Reeling postId in a persistent database or state log. If an API call times out or an agent loses context, query GET /api/v1/posts/:id to check execution state before retrying, preventing duplicate video uploads.

Sources and related documentation

Prepare your next publishing workflow

Review the supported destinations, account requirements and current plans.

View Plans
Account requirements apply
Tags:#TikTok Automation#Instagram Reels#AI Video Ads#Social Media Scheduler