Skip to main content

Let an AI session post it

Instead of writing code for each platform's API, your own script gives each hand-over to an AI assistant that can work a web browser, and lets it post the video the way a person would, on its own, on a machine that is always on. It is the unattended version of Let your AI assistant post it, where a person watches.

Reelwire offers no code for this, and no guarantee. Browser automation is young, platforms change their pages often and may treat automated posting as a breach of their terms, and an assistant working unattended can post the wrong thing to the wrong account with nobody watching. Read the last section before you build it.

Receiving, checking the signature, answering and reporting back are the same for every receiver and are on Handed over by webhook. This page is what comes after the answer.

The shape of it​

  1. A small receiver checks the signature, answers straight away, and queues the hand-over.
  2. A browser that is already signed in. The assistant works in a browser profile of its own, signed in once, by you, to each account it posts to. Never give it passwords in its instructions.
  3. One session per channel. For each of channels, your script starts an assistant session with the tools to drive that browser, and an instruction built from the hand-over:
    • where: the platform (platform and surface) and which account, from your own map of channelId to account;
    • the video: download media[].url (kind video) to a file the browser can pick, and check it against sha256;
    • the text, exactly as written: text.caption, the brand's line, the link and the hashtags, and the title where the platform has one;
    • what to do at the end: report the link to the post.
  4. The report. When the session ends, your script reports the channel with the call on Handed over by webhook: published with the link the assistant found, or failed with what went wrong. Where the assistant connects to Reelwire itself through its MCP server, the tools reelwire_mark_post_published and reelwire_report_post do the same; give that connection a key that holds Posts write and nothing else.

The post kit's A prompt for your AI assistant is a tried starting point for the instruction: open any post kit to see how it is worded.

Changes and take-downs​

A post.update or post.delete can start a session the same way: find the post by the permalink it carries, change or take it down, and report deleted once it is gone. Where the assistant cannot be sure it has found the right post, report nothing and leave it for a person.

Before you rely on it​

  • Start with approval switched on for the channel, so a person clears each post before it is handed over, and only loosen it once the sessions have behaved for a while.
  • Log every session: what it was asked, what it did, and screenshots of the result.
  • Report failed whenever the assistant is not sure, so the post shows on Posts and a person picks it up, rather than guessing.
  • Keep Email on as well while you try it: the same people get each post and can post it by hand.