Buffer
Also an agent toolBuffer classic API v1: read the authenticated user, list and manage social profiles and their posting schedules, read pending and sent updates (posts) per profile, create/edit/share/reorder/shuffle/destroy updates, look up link share counts, and read account configuration. Bearer access-token (OAuth2) auth against https://api.bufferapp.com/1 with .json-suffixed paths. Change notifications use polling of a profile's sent updates (page/count offset). NOTE: Buffer's classic v1 public API is legacy — closed to new OAuth applications; this pack models the documented v1 surface only.
18 actions · 1 triggers
The Buffer integration lets you connect Buffer to your automations with 18 actions and 1 triggers — and every action is also a tool an AI agent can call. Examples: Get Authenticated User, List Profiles, Get Profile, Get Profile Schedules, Update Profile Schedules. No blank-canvas wiring — connect it and use it in your workflows.
Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.
Triggers 1
Events in Buffer that can start a workflow.
New sent Buffer posts (polled)
Polls GET /profiles/{id}/updates/sent.json on a schedule, paging by page/count. Dedupe by update id; advance by sent_at.
Actions 18
What Zervanor can do in Buffer.
Profiles7
Get Profile
Get details of a single social media profile (GET /profiles/{id}.json).
Get Profile Schedules
Get the posting schedules for a profile (GET /profiles/{id}/schedules.json).
Update Profile Schedules
Set the posting schedules for a profile (POST /profiles/{id}/schedules/update.json). Body is form-encoded schedules[].
List Pending Updates
List a profile's pending (queued) updates (GET /profiles/{id}/updates/pending.json). Page/count paging.
List Sent Updates
List a profile's sent (published) updates (GET /profiles/{id}/updates/sent.json). Page/count paging. Recommended polling trigger source.
Reorder Updates
Reorder a profile's pending updates (POST /profiles/{id}/updates/reorder.json).
Shuffle Updates
Randomly shuffle the order of a profile's pending updates (POST /profiles/{id}/updates/shuffle.json).
Updates7
Create Update
Create one or more updates (posts) for one or more profiles (POST /updates/create.json).
Get Update
Get a single update by id (GET /updates/{id}.json).
Get Update Interactions
Get the interactions (likes, comments, reshares) an update has received (GET /updates/{id}/interactions.json). Page/count paging.
Edit Update
Edit an existing, not-yet-sent update (POST /updates/{id}/update.json).
Share Update Now
Immediately share a pending update, bypassing the queue schedule (POST /updates/{id}/share.json).
Destroy Update
Permanently delete an update (POST /updates/{id}/destroy.json).
Move Update To Top
Move an update to the top (next) position of its profile's queue (POST /updates/{id}/move_to_top.json).
Info1
Get Configuration
Get Buffer's configuration data — supported services, link-shortening options, and limits (GET /info/configuration.json).
Links1
Get Link Share Count
Get the number of shares a URL has received through Buffer (GET /links/shares.json).
Profiles.Json1
List Profiles
List the social media profiles connected to the authenticated account (GET /profiles.json).
User.Json1
Get Authenticated User
Get the single authenticated user (GET /user.json). Identity + connectivity probe.
Nothing matches your search.
Automations using Buffer
Build your own automation with Buffer in the visual builder.
Frequently asked questions
What can I automate with Buffer?
18 actions are available — for example: Get Authenticated User, List Profiles, Get Profile, Get Profile Schedules, Update Profile Schedules, and more.
Which Buffer events can start a workflow?
1 triggers — for example: New sent Buffer posts (polled).
Can Buffer be used as an AI agent tool?
Yes. Every Buffer action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.
How is the Buffer integration modelled?
Buffer is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.