LinkyFlow for Buffer
The Buffer connection brings your Buffer account into Excel and the LinkyFlow web app: every social channel connected to it — a LinkedIn page, an X profile, a Facebook Page, an Instagram, Threads, Bluesky, TikTok, YouTube, Pinterest, Google Business or Mastodon account… —, the posts on each with their status, their date and their metrics, your ideas and your tags. You connect with a personal API key of your Buffer account. Load them as structured tables, every channel in the same workbook, and plan your posts in a sheet. It writes only what you ask, from the Actions pane, each change confirmed before it runs; Buffer then publishes each post at its date or when its queue reaches it.
One account, every network
Buffer complements the native LinkedIn and Facebook connections: one Buffer connection reaches every network you already connected to Buffer, with one key. The LinkedIn and Facebook connections go deeper into those two networks — comments and their moderation, for example. Use both side by side if you need to.
Key capabilities
Account, organizations, channels and tags
Account reads the account the key reaches: its name, time zone and creation date. Organizations reads the organizations it belongs to, with what their plan allows: channels, scheduled posts, members, ideas, tags. Channels reads the channels connected to an organization — their name, network, type and link — and whether each can publish: Disconnected (Buffer lost its access: reconnect it in Buffer), Locked (the plan locks it) or Queue Paused. Tags reads the organization's tags with their color.
Every read and write is for one Organization, one of the account's — the account's first when you leave it empty.
Posts
Posts reads the organization's posts on every channel, the latest first: drafts, posts awaiting approval, scheduled, being sent, sent and failed (error, with Buffer's reason). Each row has its text, Status, Network, Due At and Sent At, its link once sent, its tags and media, and, once sent, its metrics: impressions, reach, reactions, comments, shares, clicks… Narrow it by Channel, Status, Tag, a due date range (Due From, Due To) or a creation date range (Created From, Created To), and choose its Sort.
Ideas and templates
Ideas reads the organization's ideas: their title, text, the networks they are meant for, their target date and their group. Idea Groups reads the columns they are sorted into (To Do, In Progress…). An idea is never published.
Post Templates reads the templates a post can start from: Buffer's public library, your organization's internal templates and your own private ones, with their title, body and description. Narrow it by Visibility.
Post metrics
Post Metrics reads one row: how many posts were sent over a period and what they achieved, summed by Buffer — impressions, reach, reactions, comments, shares, reposts, clicks, engagement rate, views, saves… Leave From and To empty for the last 30 days, and narrow by Channel or Tag. Buffer reads its metrics once a day.
Posts written back to Buffer
From the Actions pane of Excel or the web app, one record at a time, each change confirmed before it runs:
- Create Post writes a post on a Channel: its Text, Images or a Video at public HTTPS addresses, and Tags. When places it:
addToQueueat the channel's next free slot (the default),shareNextat the head of the queue,customScheduledat its Due At,shareNowat once — or tick Save As Draft to keep it a draft in Buffer. - Update Post changes a post's text, date, images or tags, or takes it back to draft. A queued post is published as edited when its date comes.
- Delete Post removes a post from Buffer and its queue for good. A post Buffer has sent is not offered: it stays on its network, and Buffer keeps it.
- Publish Now publishes a post at once, whatever its date or its place in the queue: offered on a draft, a post awaiting approval, a scheduled or a failed one, never on one Buffer is sending or has sent. LinkyFlow reads the post again just before.
- Move In Queue moves a queued post to the top or the bottom of its channel's queue: offered on a post the queue holds, never on one dated by hand. LinkyFlow reads the post again just before.
- Create Idea writes an idea with a title or a text, its networks and a target date. Nothing is published.
- Create Tag, Update Tag and Delete Tag write the organization's tags: a name and a color (
#F523F1). A tag deleted is taken off every post and idea that carried it; they are kept. - Create Post Template, Update Post Template and Delete Post Template write your templates: a title, a body and a description, private to you unless you make it internal to the organization. Buffer's public library is never changed.
What you can do:
- Plan the posts of every network in one sheet, with their status and date, and fill your Buffer queue from it
- Spot the failed posts and the channels that can no longer publish before a post is missed
- Compare what your posts achieved channel by channel, with your own formulas
- Read a table in a cell with the
=LF.bufferfunctions, such as=LF.buffer.posts, and open the Buffer Posts and Buffer Post Metrics dashboards in Excel - Read the same account from ChatGPT or Claude through MCP
Buffer's limits
Buffer limits each API key to 150 calls every 15 minutes, 600 a day and 1,000 or 2,000 every 30 days (it depends on the account) on its free plan. Each table load is one call, each further page another: All results reads 10 pages at most and says when the answer is incomplete. When a limit is reached, LinkyFlow says so: wait, then try again.
What LinkyFlow may do
The key reaches every organization and channel of the account. On top of it, the connection's owner chooses in LinkyFlow what it may do — for example read posts and metrics, but never publish. See LinkyFlow permissions per connection.
Agents
The Inventory Stock Sync, Price Sync and Omnichannel Sales agents work on stores: a Buffer account holds no products, stock or orders, so it is not one of their connections.
ChatGPT and Claude
Through MCP, an assistant reads every table with the same connection. Every post written, edited, deleted, published now or moved in its queue, and every idea, tag and template written, is previewed first and runs only once you confirm.
What is not done
Channels are connected and reconnected in Buffer, not in LinkyFlow. Ideas are read and written, never edited or deleted: Buffer offers no way to. Snippets and team notes stay in Buffer: LinkyFlow does not read them yet. Buffer fetches a post's images and video from their addresses when it publishes: an address must stay reachable until then. Buffer publishes each post itself, at its date or when its queue reaches it: LinkyFlow schedules nothing of its own for Buffer.
Next steps: