ActionBufferUpdated September 2026
How do I post immediately via Buffer?
Short answer: You can share update now in Buffer by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Buffer Share Update Now action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Update ID update_id | string | Required | Update ID to share now |
Sample request
{"update_id": "e.g. 4eccf2e1512f7e6307000001"}
Returns
{"message": "Update shared!","success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Share Update Now.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Share Update Now.
What does the Share Update Now action do in Buffer?
Bypasses the queue and posts immediately. For real-time reactive content — "breaking news from our blog → post now to social".
What inputs does Share Update Now require?
Required: Update 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 Share Update Now support batch operations?
Run Share Update Now 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 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.
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.