Connect
Buffer: connect with an API key, then draft, schedule and measure posts
TL;DR
Buffer connects with one API key from Buffer → Settings → API. The key reaches every Buffer organization of that login, and each channel becomes its own connection, grouped under its organization. 14 reads and 20 writes; scheduling and publishing always wait for a person.
Connect step by step
- 1In Buffer open Settings → API and create an API key (give it Buffer's notes permission if the agent should read and write team notes).
- 2In Agent Planners open Integrations → Buffer, paste the key and press Connect. The key is checked with Buffer first, then stored encrypted and never shown again.
- 3Every channel of every organization the key reaches appears on the card under its organization.
- 4To replace a key, use Replace key with a new key of the same Buffer login. Several keys can be connected; each is its own sign-in.
Channels are added in Buffer (publish.buffer.com → Channels), then found by Refresh accounts — Buffer's API cannot connect one. Disconnect deletes the stored key and the channel rows.
Duplicates
- A Buffer channel that is the same account as one connected directly here and able to publish (X Organic, a Facebook Page, Instagram, YouTube) is marked a duplicate and hidden in the picker.
- The agent will not publish to it through Buffer; it names the direct connection to use. A LinkedIn company page that LinkedIn Ads also reaches stays visible and publishable through Buffer.
What works
- Ordinary (your approval setting decides): draft posts, ideas, channel-less drafts, notes, tags.
- Always a person: scheduling (a time, the queue, or the next slot), posting now, changing a scheduled post, moving it in the queue, deleting a post or a tag. A preview sends nothing.
- Same text twice: the same text on the same channel within 12 hours is refused unless you say it is a repost.
- Text: checked against each network's limit and Buffer's counting rule before sending, refused, never cut (for example X 280 on a free profile, LinkedIn 3,000, Bluesky 300 graphemes).
- Media: public https links Buffer fetches when it publishes; signed or expiring links and login-only share links are refused, and Buffer has no upload.
- Metrics: one sent post's metrics as Buffer normalizes them (refreshed about once a day), or metrics summed over a window. No follower or channel analytics.
- In a project: a post a project task drafts or schedules is linked to its plan item and listed on the project page; when the item moves, the post is flagged for a person, never moved on its own — see Projects.
Limits
- What Buffer's API cannot do (19 operations, refused by name with where to do them): connect, disconnect or reconnect a channel; edit a profile or channel settings, the posting schedule or the queue; edit or delete an idea; upload media; approve or reject a post; reply to comments; recurring posts; team members and API keys; deleting a sent post from the network.
- Rate limits on the plan we measured: 150 requests per 15 minutes, 600 a day and 3,000 in 30 days, shared by every key and MCP connection of the Buffer account. list_organizations and get_limits show what is left.
- Plan limits: Buffer's plan caps channels, scheduled posts, ideas and tags (a Free plan holds 3 tags and reads metrics for the last 31 days only).
Troubleshooting
- A channel is missing. Connect it in Buffer, then press Refresh accounts.
- "over its limit". Shorten the text yourself — it is never cut.
- A channel is hidden. It is a duplicate of a direct connection; publish through that one.
- Tested live: connecting and the reads ran on a real Buffer account; creating, scheduling and deleting posts have not been sent live yet.
Frequently asked questions
- Where is my Buffer API key kept?
- On our server, encrypted. It is never shown again; replace it from the card or delete it with Disconnect.
- Does deleting a post in Buffer remove it from X or LinkedIn?
- No. Deleting a sent post in Buffer only forgets it in Buffer; delete it on the network itself.