What an agent can do in Buffer
Draft, schedule and read social posts and ideas.
Jobs on Rush that use Buffer
- How Does Real Estate Marketing Software Draft Posts in Each Realtor's Buffer When a Listing Goes Live?
- Draft Each Restaurant's Weekly Specials Posts as Buffer Drafts
- Schedule a Week of Social Posts in Buffer
- Report Social Post Performance From Buffer
Agents that use Buffer
How Buffer connects
Buffer is a built-in app: you sign in with your Buffer account on its own page, through Rush's own app, so you register no OAuth app. The sign-in asks only for the scopes listed below, and the run's token reaches api.buffer.com, the Buffer GraphQL API.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names buffer in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
Scopes the sign-in asks for:
offline_accessaccount:readaccount:writeposts:readposts:writeideas:readideas:writesnippets:readsnippets:write
POST https://api.phoenix.so/me/connections
{
"type": "app",
"name": "buffer"
}Whose Buffer account the agent uses
Your Buffer connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Buffer, and a run started with an API key uses the Buffer of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Buffer, and that agent's runs use their account and nothing else: never yours, never another user's.
More Marketing integrations
Frequently asked questions
How do I connect Buffer to Rush?
Open Settings → Connections in the console and connect Buffer, or send POST /me/connections with {"type":"app","name":"buffer"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Buffer account?
No. A run gets your Buffer connection only when it names it in connections ("connections": ["buffer"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Buffer?
Draft, schedule and read social posts and ideas. 4 published jobs use it; this page lists them.
Can my app's users connect their own Buffer?
Yes. Make each user an agent from your template, and they sign in to their own Buffer through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for marketing teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to