Channels and Buffer

Why Buffer

Zeea does not post to Instagram, LinkedIn, Facebook, Pinterest or X itself. It hands each approved post to Buffer, which holds your connected accounts and publishes at the time set. That keeps your account passwords out of Zeea entirely, and it means the queue is visible in two places: here, and in Buffer, where you can see and change anything Zeea sent.

Connecting a brand

Each brand connects its own Buffer account, under Brand → Channels. You paste a Buffer access token; Zeea checks it against Buffer, stores it where no browser can read it, and shows you the account and how many channels it holds. The token never comes back to the screen, not even to the person who pasted it.

Then you map networks to channels: which Buffer account is this brand’s Instagram, which its LinkedIn. A brand with two accounts on one network, say a company page and a founder’s profile, maps both; each post then carries a tick per account, with the brand’s default ticked, so mapping two is never an instruction to post on both.

What “in the queue” means

A post you approve goes to Buffer scheduled for its slot, and the board says scheduled. It is now Buffer’s to publish; Zeea checks back after the time and marks it published when Buffer confirms it went. A story is one Buffer post per frame, spaced so the queue cannot reorder them.

Nothing reaches Buffer without a person’s approval, and Zeea never quietly sends less than a post asked for. If a picture is missing or the words do not fit the channel’s limit, the post is refused with the reason, not sent bare.

Taking a post back, moving it, stopping it

• Pull back. On a post, Pull back & reopen removes it from Buffer’s queue and puts it back in review. If Buffer refuses to release it, the post stays exactly as it was and says so.
• Move it. Drag a post to another day on the calendar, or adjust a whole campaign’s timeline. A post already in Buffer is taken out, re-slotted and sent back, keeping its hour; the new time is written only after Buffer confirms the old post is gone, so the board and the queue can never disagree.
• A slot that has passed. Buffer refuses a time in the past. Zeea says so and asks you to pick a new day rather than publishing late on its own.
• Disconnecting a brand’s Buffer stops anything new being sent. Posts already in Buffer’s queue stay there and still publish; take them back first if they should not.

Keeping the two in step

If something is changed in Buffer directly, the calendar’s sync reads Buffer back and shows what differs, and lets you decide which side wins. It never guesses: a post that exists only in Buffer, or only here, is shown as exactly that.