ActionBufferUpdated June 2026

What's queued in Buffer?

Short answer: You can list pending updates in Buffer by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Buffer List Pending Updates action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this action All 6 Buffer actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Profile ID profile_id	string	Required	Buffer profile ID
Count count	string	Optional	Max number of updates to return (default 30, max 100)

Sample request

{
  "profile_id": "e.g. 4eb854340acb04e870000010",
  "count": "30"
}

Returns

{
  "total": 1,
  "updates": [
    {
      "id": "4eccf2e1512f7e6307000001",
      "text": "Hello world",
      "due_at": 1712839200,
      "status": "buffer"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Pending Updates.

What does the List Pending Updates action do in Buffer?

Returns the queue + scheduled updates for a profile, not yet sent. Useful for "is the queue full?" pre-flight checks before Create Update or for content-calendar visibility workflows.

What inputs does List Pending Updates require?

Required: Profile ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Buffer returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Pending Updates support batch operations?

Yes. Run List Pending Updates inside a Loop node to process arrays. TinyCommand handles Buffer's rate limits automatically so you don't have to throttle manually.

More actions

Other Buffer actions.

Action

Create Update (Queue)

Adds to the back of the queue — Buffer publishes at the next configured posting slot. For "auto-fill the queue with content from our blog" workflows where you want Buffer to time the actual send.

Action

List Buffer Profiles

Returns every connected social profile — X, LinkedIn, Facebook, Instagram, etc. — with the service type and connected account name. Useful for cross-network fan-out workflows that want to publish to all relevant profiles in one call.

Action

List Sent Updates

Returns the sent-update history for a profile with timestamps and engagement counts. Useful for weekly performance digests ("which posts got the most engagement this week?") and for failure-detection workflows ("did anything fail to send?").

Action

Schedule Update for Specific Time

Schedules a post for a precise time (vs Create Update which uses the queue). Useful for time-sensitive content — product-launch announcement at exactly 9am, event reminder 1 hour before start.

Action

Share Update Now

Bypasses the queue and posts immediately. For real-time reactive content — "breaking news from our blog → post now to social".

What's queued in Buffer?

The fields this action accepts.

Apps that pair well as the trigger for List Pending Updates.

Questions about List Pending Updates.

Other Buffer actions.