Multi-Brand Social Posting Runners

Hybrid API and Playwright social runners

Social Poster on Streamlit port 8501 manages per-brand queues, posting windows, X and Facebook API bridge, GBP API posts, and Playwright runners for Nextdoor and LinkedIn.

Silent failures previously left brand accounts quiet for days. Failure counters and Logs cross-reference give operators same-day visibility when runners break.

Embedded in Knight Command Social Poster and Social Ops tabs — complements local-visibility-systems GBP strategy with scheduled post cadence.

If your “automation” still dies quietly overnight, this is the production answer: isolated brand queues, hybrid API + browser runners, and failures you can see before the week is gone.

Queued social posting keeps project proof visible between jobs — especially for trades where galleries drive quote quality.

We built this after watching brand accounts go quiet for a week at a time with no alert anywhere. A generic scheduler would have covered X and Facebook, but Nextdoor and LinkedIn still needed browser automation, and none of the off-the-shelf tools surfaced a failure the same day it happened.

Isolating credentials per brand also matters more than it sounds. A wrong-account post on a client's page is the kind of mistake that erodes trust fast, so queue separation is enforced at the runner level, not just by habit.