OtherReal-timeUpdated May 2026

Buffer

Buffer queue and scheduled social posts

Buffer is the social-scheduling tool built around the "queue" metaphor — each connected social profile has a posting queue with timed slots, and updates either flow into the queue (the default behaviour, posts go out at the next slot) or get scheduled to a specific time. Tiny Command exposes six actions, no triggers: List Profiles (returns every connected social profile across networks — Twitter/X, LinkedIn, Facebook, Instagram), Create Update (add to the queue without sending), Schedule Update (specify a future post time), Share Update Now (skip the queue, post immediately), List Pending Updates (queue and scheduled, not yet sent), and List Sent Updates (historical). The lack of triggers reflects Buffer's product shape — it's a one-way orchestrator from your workflow to the social networks. Updates can target multiple profiles in a single call (the profile_ids array fans out the same content), which is the typical use case: write a workflow that takes a blog-post URL and queues an announcement across Twitter, LinkedIn, and Facebook in one Create Update.

Connect Buffer

0triggers

6actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Buffer can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
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.	5 fields	View →
List 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.	2 fields	View →
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.	0 fields	View →
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?").	2 fields	View →
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.	5 fields	View →
Share Update Now	Bypasses the queue and posts immediately. For real-time reactive content — "breaking news from our blog → post now to social".	1 fields	View →

Recipes

Pre-built Buffer workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Buffer → Slack alerts

AI-triage every Buffer event, ping the right channel only when it matters.

Buffer → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Buffer → Notion database

Turn Buffer into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Buffer once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Buffer field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Buffer integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Buffer to Tiny Command?

Open the Tiny Command workflow builder, drop in a Buffer node, and click Connect. Authorize Buffer once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Buffer triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Buffer today. Use Tiny Command's universal Webhook or Schedule trigger to start Buffer workflows, then run any Buffer action you need.

What Buffer actions can I run from a workflow?

6 Buffer actions are available out of the box, covering other operations like "Create Update (Queue)". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Buffer integration real-time?

Buffer actions execute synchronously inside your workflow. Tiny Command waits for Buffer's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Buffer with Tiny Command?

No. Every Buffer trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Buffer API endpoint directly.

How much does the Buffer integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Buffer integration itself has no per-app surcharge.