Get user (yekar.buffer.get-user) | Read | The Buffer account this connection signs in as: its name and timezone, and every organization (workspace) it belongs to with that organization's plan limits - how many channels it may connect and how many posts it may hold scheduled. Those limits matter more than they look: going over either is refused rather than truncated. The timezone is the account default; each profile also has its own. |
List profiles (yekar.buffer.list-profiles) | Read | Every social account connected to this Buffer account, across every organization it belongs to, with the profile id that Create update needs. This is the tool to call first: a Buffer profile (Buffer now calls it a channel) is one destination - a Page, a channel, a handle - a post goes only to the profiles you name, and a Facebook Page and a Facebook group share the service name 'facebook' while being different places. Locked profiles (over the plan's channel limit) and disconnected ones are listed but cannot post. Buffer returns every profile in one response - there is no paging here, and the list is bounded by the plan. |
Get profile (yekar.buffer.get-profile) | Read | One connected account's details: which network it is, its handle, whether its queue is paused or the account is locked or disconnected, its timezone, and how many posting slots a day its schedule defines. That last number is what decides how far away 'the next slot' actually is - a profile with one slot a day queues tomorrow's post, not this afternoon's - and a paused queue sends nothing at all. |
List pending updates (yekar.buffer.list-pending-updates) | Read | The posts waiting in a profile's queue, soonest first, each with the time it is due. Nothing here has been published - every item reports published: false - which is exactly what makes this the tool for checking what an automation actually scheduled. hasMore says whether a later page exists; Buffer gives no total. Buffer pages by cursor, so a later page costs one extra request per 100 posts before it. |
List sent updates (yekar.buffer.list-sent-updates) | Read | Posts Buffer has sent from a profile, or tried to, newest first, with each one's engagement metrics as Buffer reports them (refreshed about once a day) and its link on the social network. Use this to confirm a queued post really went out - a post that failed at the network appears with status error and the reason, rather than silently missing. hasMore says whether a later page exists; Buffer gives no total. |
Get update (yekar.buffer.get-update) | Read | One post's current state: its text, whether it is still QUEUED, being sent, or has actually been sent, when it is due or when it went out, the network's link to it once it did, and why it failed if it did. This is the honest way to check on something an automation queued - published is true only once the network has the post. |
Create update (yekar.buffer.create-update) | Write | QUEUE a post to one or more connected accounts. By default this does NOT publish: Buffer adds it to each profile's queue and sends it at that profile's next scheduled slot, which may be hours away or tomorrow - check Get profile for how many slots a day it has. Pass now to send immediately, scheduledAt for a specific time, or top for the front of the queue. One call creates one post PER PROFILE, each with its own id, and each profile succeeds or fails on its own: items lists the posts made and failures any profile Buffer refused, so retry only those. The result reports published, which is false for anything queued or still being sent. |
Edit update (yekar.buffer.edit-update) | Write | Rewrite a post that is still in the queue, and optionally move it to a specific time. Only QUEUED posts can be edited - once Buffer has sent something, the post belongs to the social network and this cannot reach it. Media you do not pass is kept; passing pictureUrl replaces the images, and passing linkUrl replaces the link preview and removes any image, since Buffer cannot carry both. |
Share update now (yekar.buffer.share-update-now) | Write | Send a queued post immediately instead of waiting for its slot. This is the tool that turns a plan into something public, and it cannot be undone from here - Buffer hands the post to the social network, and deleting it afterwards is that network's job, not Buffer's. The post leaves the queue either way. Buffer usually answers while the post is still being sent, so published is often false here; check Get update to see it arrive. |
Move update to top (yekar.buffer.move-update-to-top) | Write | Move a queued post to the front of its profile's queue, so it takes the next available slot instead of waiting its turn. It does NOT send it - the post is still queued afterwards, just sooner. Use Share update now to publish immediately. Everything behind it shifts back by one slot. |
Delete update (yekar.buffer.delete-update) | Write | Remove a post from the queue before it is sent. This is how a scheduled post is cancelled. It only matters while the post is still QUEUED - once Buffer has sent it, the post lives on the social network and must be deleted there; Buffer's own record of it is not the post. |