Approval queue
Every queued post is previewed exactly as it will appear. Edit the copy, approve it, or deny it. Approval is the default gate, not an optional extra.
One queue, one human approval, twelve destinations — from TikTok to the TV above your own bar.
Scheduling tools either post automatically and eventually publish something embarrassing, or need someone to log into a web dashboard, which means it does not get done.
Posts land in a queue. You review them in a Telegram mini app — preview, edit, approve or deny. Approved posts publish on schedule to the social platforms, your own website's blog, your venue's TV screens and your Telegram channels, then confirm back to you. Nothing reaches an audience without a person saying yes.
Every item below is a feature of the running system, not a roadmap.
Every queued post is previewed exactly as it will appear. Edit the copy, approve it, or deny it. Approval is the default gate, not an optional extra.
Approved posts fan out to TikTok, Instagram, LinkedIn, X, Threads, Facebook and Reddit — and to the places scheduling tools forget: your website's blog, the TV screens in your venue and your Telegram channels. Each destination is called separately and reports back individually.
A post with no photo gets one: AI-generated art composited with your logo and the event details, uploaded and attached automatically. A weekly indexer labels your own photo folders — bands, food, events — so generated flyers draw on real reference images rather than generic art.
The queue is swept every five minutes and anything approved and due goes out, then is marked posted so nothing double-posts.
A Telegram message after each run, with per-destination results. You find out a token expired from the bot, not from a client asking why you stopped posting.
Send a long video and get vertical clips: transcribed with Whisper, the strongest 3–6 moments selected, cropped and published to TikTok, Instagram and YouTube Shorts.
Built and tested; not currently enabled in production.
Nothing exotic. A mini app talking to an action-routed API, with state in Postgres and authorisation checked server-side on every call.
| Front end | Telegram Mini App (WebApp) |
|---|---|
| Queue | n8n Data Table |
| Cadence | Swept every 5 minutes |
| Destinations | TikTok, Instagram, LinkedIn, X, Threads, Facebook, Reddit, website blog, venue TV, Telegram channels |
| Artwork | AI generation + logo/text compositing, reference library indexed weekly |
| Video | Whisper transcription, LLM moment selection, vertical crop |
| Reporting | Per-destination result summary to Telegram |
A conversation costs nothing and often ends with us saying automation is not worth it for a given job. That is a useful answer too.