Buffer
Schedule and manage social posts, channels, ideas and post metrics in Buffer via the Buffer GraphQL Public API.
About
Buffer ships in the w6w first-party pack. It declares 14 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.buffer- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- Social Media · Marketing
Overview
Buffer queues and publishes social content from inside a workflow, across every channel a team runs — Instagram, Facebook, X, LinkedIn, Pinterest, TikTok, YouTube, Mastodon, Threads, Bluesky and Google Business Profile — through Buffer’s own GraphQL API.
Posts can be listed, created, edited and deleted, with per-network fields (a LinkedIn first comment, an X thread, an Instagram reel) passed straight to Buffer so nothing new the vendor adds ever needs a rebuild. Queueing, custom scheduling and posting-limit checks keep a bulk publish from silently overrunning a channel’s daily cap, and aggregated post metrics summarise engagement over a chosen window.
Beyond publishing, the Ideas backlog lets a workflow capture and group post concepts before they’re scheduled, and organization and channel listing give every other action the ids it needs. It suits marketing and social-media workflows that plan content in bulk, coordinate approvals across several organizations, and want performance numbers back in the same automation that queued the post.
Build with Buffer
Three routes to the same 14 actions. The Workflow tab is generated from Buffer's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Account
account-get The Buffer account behind this Connection — name, timezone, scheduling preferences and its organizations. Email addresses are opt-in.
Get Channel
channel-get One connected profile by id, including its weekly posting schedule — the slots Buffer fills when a post is added to the queue.
List Channels
channel-list Every connected social profile in an organization, with its network, handle and whether it is locked, disconnected or has a paused queue.
Get Daily Posting Limits
daily-posting-limit-list Per-channel posting headroom for a day — sent, scheduled, the cap, and whether the channel is already at it. Run before bulk scheduling; hitting the cap fails a post.
Create Idea
idea-create Save a piece of content to an organization's idea board. Ideas have no channel and no schedule — the target networks are an annotation only.
List Idea Groups
idea-group-list The groups (board columns) ideas can be filed under. Read-only — Buffer has no mutation for creating or renaming a group.
List Ideas
idea-list Page through an organization's ideas — the content backlog that has not been assigned to a channel yet. Cursor paginated.
List Organizations
organization-list Every organization (workspace) the connected Buffer account can see. Run this first — almost every other action needs an organization ID and Buffer has no default.
Create Post
post-create Schedule a post on one channel — queued, sent now, or at an exact time. One call is one channel; posting the same copy to several means one call each.
Delete Post
post-delete Delete a post by id. Buffer echoes the deleted id; deleting the same id twice fails with NOT_FOUND rather than succeeding.
Edit Post
post-edit Change the text, schedule, assets or metadata of a post that has not been sent. Fields left blank are not touched.
List Posts
post-list Page through an organization's posts, filtered by channel, status, tag or date. Cursor paginated — feed `pageInfo.endCursor` back in as the cursor.
Aggregate Post Metrics
post-metrics-aggregate Normalised performance totals across a date window — always postCount, reactions and comments, plus any metric every channel in scope supports.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Buffer's real ids.
{
"manifestVersion": "2",
"name": "buffer-example",
"steps": [
{
"id": "channel-get",
"uses": {
"app": "io.w6w.buffer",
"action": "channel-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"channelId": "<channelId>"
}
}
]
}Here are some of the things you can do
-
Get Channel
readchannel-get -
Get Account
readaccount-get -
List Channels
searchchannel-list -
Get Daily Posting Limits
readdaily-posting-limit-list -
Create Idea
performidea-create
+9 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Buffer, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Buffer. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "post-create",
payload: {
channelId: "<value>",
// text: "<value>",
mode: "<value>",
// schedulingType: "<value>",
// dueAt: "<value>",
// saveToDraft: "<value>",
// needsApproval: "<value>",
// tagIds: "<value>",
// imageUrls: "<value>",
// videoUrl: "<value>",
// linkUrl: "<value>",
// linkTitle: "<value>",
// linkDescription: "<value>",
// assets: "<value>",
// metadata: "<value>",
// ideaId: "<value>",
// aiAssisted: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action post-create --payload '{"channelId":"<value>","mode":"<value>"}'Give an AI agent Buffer — without giving it Buffer's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.buffer#channel-get",
"input": {
"channelId": "<channelId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Buffer connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Buffer's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Buffer itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Buffer declares its own checks, so its health is a property of the app rather than something the host guesses at.
Buffer platform status
Atlassian Statuspage summary for status.buffer.com. The verdict tracks the `Buffer API` component — the origin every action calls — rather than Buffer's global indicator, which also aggregates Login, Settings, Analytics, Community and the MCP server. `Publishing` and the per-network components are reported for attribution but do not drive the state: they affect whether a queued post goes out later, not whether an API call works.
API rate-limit headroom
Reads Buffer's structured `RateLimit` / `RateLimit-Policy` headers via a single `{ account { id } }` query. Buffer meters three concurrent windows — 15 minutes, 24 hours and 30 days — so all three are reported and the verdict is the worst of them.