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.mjsKeep 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.