SocialBee

What This Integration Enables

SocialBee's model is the useful kind of opinionated: workspaces per brand, categories that control the posting rhythm, posts filed into category queues. That structure is what makes it automatable, because an agent does not need to decide when to post, only what goes in which queue. The scheduling judgment was made once, by a person, when the category was configured; from then on, keeping the queues fed is pipeline work, and pipeline work is what agents are for. This connector gives FlowRunner agents that filing capability, plus the reads to audit everything already scheduled, across every workspace the account manages. - Create and queue posts from any upstream event: a CMS publish, a form submission, a product update - Cross-post to multiple connected profiles, Facebook, Instagram, LinkedIn, X, Pinterest, TikTok, in a single step - Report on scheduled and queued content across a workspace, filtered by category - Resolve workspace, profile, and category IDs so multi-brand agencies can drive many clients from one set of flows - Keep queue health visible so the evergreen rotation never silently runs dry The category model is the part worth designing around. Because each category carries its own posting plan, an agent never schedules a time; it chooses a queue, and the queue's rhythm does the rest. That separation is what lets non-marketing systems, a CMS, a form tool, a product changelog, feed social without anyone teaching them about optimal posting windows. Everything filed here eventually publishes under a brand's name in public, which is exactly the kind of write FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates exist to supervise.