Buffer queue push is the integration that hands off locked masters from Brandflux to the Buffer-connected channel queue. It is available from Professional and above, and it is an explicit Lead action on the delivery page, not an auto-publish.
What “explicit Lead-clicks-Publish” means
A locked master does not auto-flow to a connected social channel. The Lead opens the delivery page, picks the asset, picks a Buffer profile (per-asset; the same campaign can hand off to multiple channels), and picks a date and time. The push only fires when the Lead clicks Publish. Brandflux’s role ends at the handoff; Buffer owns the queueing, scheduling, and posting from there.
Why the explicit action
Auto-publish on approval sounds convenient and is operationally dangerous. Approval and publish are two different decisions: the team can approve a Variation for shipping while still wanting to coordinate the publish timing with a launch window, an embargo, or a parallel announcement. Separating the two stages keeps the publish moment in the Lead’s hands.
What flows back
The Buffer post ID is stored per asset, and the Brandflux delivery page reflects the Buffer-side status (Pending, Published, Failed). When the launch retro asks “what shipped, when, where”, the answers are in the campaign view, not split between two tools.
Scope
- In scope today. Buffer queue push for stills and reels handed to the configured Buffer profiles.
- Not in scope today. Direct Meta Business publish (a separate integration in the workflow spec, also Professional-gated when it ships). Paid-ads management. Any social channel Buffer doesn’t connect.
- Calendaring. Buffer owns the calendar. Brandflux does not duplicate that surface.
Related on this site
- /glossary/final-approval produces the locked masters Buffer queue push hands off.
- /glossary/dam is where those masters are pulled from at push time.
- /glossary/campaign is the unit Buffer status reports back into.