List Pending Updates: Buffer action

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. Tiny Command handles Buffer's rate limits automatically so you don't have to throttle manually.

More actions