Publish one announcement to every Postiz channel from chat

The agent calls the Public API of your Postiz instance — cloud or self-hosted — and sees there the connected social accounts, the post feed for a period, the free schedule slots and analytics for channels and individual publications over 7, 30 or 90 days. Out of that a picture forms: what is already lined up for the days ahead, where the announcement has not gone yet and which posts drew more reactions than the rest.

Postiz is a layer over the platforms, and a scheduled post is not yet a published one: the decision is made by X, LinkedIn, Telegram or Mastodon on their side. So the agent treats the notification feed, not the schedule, as the source of truth — it shows which publications went through and which ones the platform rejected, with the error. Nor does it push one and the same text to every channel: the wording is tuned to each platform.

On the writing side the agent does plenty: it creates drafts and scheduled posts, moves a post between draft and schedule, uploads media and, when needed, deletes posts and disconnects channels. Fan-out publishing is packed into a single request with an array of posts, so the announcement goes to every channel at once. It publishes only where a social account is already linked inside Postiz: connecting new channels is not the agent's job.

The Public API limit is hard — 30 requests per hour across all endpoints at once — and the agent spends them sparingly: a fan-out goes as one request with an array of posts, analytics is taken for a whole period instead of day by day, and the feed is re-read no more often than the answer actually changes. Media is uploaded first and attached to the post afterwards, so a broken image fails before publishing rather than taking the whole fan-out down with it. If there are no channels or no data, it says so directly instead of showing an empty table.