| name | sales-buffer |
| description | Buffer (buffer.com) platform help — simple social media publishing/scheduling across 11 networks (Instagram, LinkedIn, TikTok, X, etc.) with queue scheduling, drafts, analytics, engagement, and link-in-bio. Two APIs: a current GraphQL developer API (Bearer key from publish.buffer.com/settings/api, plan-based rate limits, beta/free) and a deprecating legacy REST v1 (OAuth, 60/min); no webhooks. Use when building a Buffer API integration to auto-schedule posts or pull metrics, migrating a legacy v1 integration to the GraphQL API, hitting plan-based API rate limits, per-channel pricing exploding as you add accounts, the free plan's 3-channel or lifetime 8-connection cap, needing approval workflows (Team plan), Buffer lacking social listening, or choosing Free vs Essentials vs Team. Do NOT use for social media management strategy or tool selection across tools (use /sales-social-media-management), social listening (use /sales-social-listening), or influencer marketing (use /sales-influencer-marketing). |
| argument-hint | [describe what you need help with in Buffer] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","social-media-management","publishing","platform"] |
| github | https://github.com/bufferapp |
Buffer Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Build an API integration — auto-schedule posts, manage channels, pull post metrics
- B) Migrate a legacy v1 (
api.bufferapp.com/1) integration to the new GraphQL API
- C) Fix API rate limits / auth (Bearer key vs legacy OAuth) / the 2026 media (Assets Input) change
- D) Understand pricing — the per-channel model, free-plan caps, Team-gated features
- E) Configure a module — Publish/queue, Create (Ideas), Analyze, Community, approvals, Start Page
- F) Decide if Buffer fits — vs needing social listening, agency scale, or deep collaboration
-
Which API? Build new on the GraphQL API; only touch REST v1 for an existing integration you're migrating. There are no webhooks — anything reactive must poll.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Social media management strategy or tool selection across tools | /sales-social-media-management {question} |
| Social listening / monitoring (Buffer has none) | /sales-social-listening {question} |
| Influencer marketing | /sales-influencer-marketing {question} |
| Connecting Buffer to other tools generically (iPaaS) | /sales-integration {question} |
When routing, give the exact command, e.g. "This is a tool-selection question — run: /sales-social-media-management Buffer vs Hootsuite for a 3-client agency".
Step 3 — Buffer platform reference
Read references/platform-guide.md for the full reference — the module map (what's API vs UI-only), the per-channel pricing model (free-plan 3-channel + lifetime 8-connection caps, Team-gated approvals, no social listening), the channel/post data model with JSON shapes, and quick-start recipes (auto-schedule via GraphQL; poll metrics into a dashboard; migrate v1→GraphQL).
for the integration surface — the API (, Bearer key from , mutation, plan-based rate limits across 15-min/24-hr/30-day windows, the 2026-05 Assets-Input migration) and the (, OAuth, , 60/min). Note: on either.
