Still True

Built on the Buffer API

The last look before every post goes out

A scheduled post is a promise written on Monday about Friday. Still True re-reads your Buffer queue against the calendar, your own pages, the weather, remembrance days and the news, and holds the posts the world has made wrong. Every hold is reversible and explained inside Buffer.

A small business's day of posts, replayed on a real day

Departures

Five things that change after you hit schedule

The calendar

Weekdays that do not match their date, "tomorrow" that now means another day, a time or a date already passed, "good morning" at 20:30.

Join us Friday 14 November: 14 November 2026 is a Saturday.

Your own pages

The product page, the shop and the ticketing page are the source of truth. Still True reads their structured data: price, stock, event date and status.

Back in stock, €49 while the page says out of stock.

The weather

Sunshine and outdoor plans against the forecast for the hour the post goes out, with the next dry slot proposed.

Terrace open this afternoon ☀️ into 90 % rain.

Remembrance days

National days of mourning and remembrance in your audience's country, from a sourced calendar of 31 days in 17 countries.

Friday 13th flash sale in Paris on 13 November.

The world

Red and orange GDACS disaster alerts and Wikipedia's Current Events, matched to the audience's country and to the words in the post.

Our prices are on fire 🔥 the day a wildfire alert hits.

What happens when the world moved

  1. Re-checked on time. Every scheduled post is read again 60 and 10 minutes before it goes out, and every few hours before that.
  2. Held, never deleted. High-confidence problems (sold out, cancelled, a date already passed, wording that echoes an active disaster) move the post to drafts in Buffer. Everything else gets a note.
  3. Explained inside Buffer. A note on the post and a tag say what changed and where it was read, so the team sees it in Buffer itself.
  4. One tap to fix or release. A corrected price, the right weekday or the next dry slot is proposed. Release puts the post back at its original time.

How it uses Buffer

Need Buffer API
Connect any Buffer account OAuth 2.0 Authorization Code with PKCE, rotating refresh tokens
Read the queue cheaply posts filtered by status and a due-time window, one query per organisation per check
Local day and hour channels: timezone, service, queue state
Hold without deleting editPost(saveToDraft: true); release with editPost(mode: customScheduled, dueAt)
Explain inside Buffer createCollaborationNote on the post, and createTag / tagIds
Apply a fix editPost(text) or a new dueAt