ActionBufferUpdated September 2026
What social profiles are connected to Buffer?
Short answer: You can list buffer profiles in Buffer by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Buffer List Buffer Profiles action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Sample request
{}
Returns
[{"id": "4eb854340acb04e870000010","avatar": "https://example.com/avatar.png","default": true,"service": "twitter","schedules": [],"service_username": "buffer","formatted_username": "@buffer"}]
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Buffer Profiles.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Buffer Profiles.
What does the List Buffer Profiles action do in Buffer?
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.
What inputs does List Buffer Profiles require?
List Buffer Profiles has no required inputs. Sensible defaults are applied if you leave fields blank.
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 Buffer Profiles support batch operations?
Run List Buffer Profiles 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
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.
ActionList Pending Updates
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.
ActionList 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?").
ActionSchedule 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.
ActionShare Update Now
Bypasses the queue and posts immediately. For real-time reactive content — "breaking news from our blog → post now to social".