ActionBufferUpdated September 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.

List Pending Updates in Buffer — start free All 6 Buffer actions

List Pending Updates in Buffer — start free

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.

Triggered by

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

Any of these apps can fire this action as part of a workflow.

Google Sheets → Buffer

2 Google Sheets triggers

HubSpot → Buffer

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Buffer returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Pending Updates support batch operations?

Run List Pending Updates inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Buffer's rate limits.

More actions