A bakery's captions, drafted, approved, and posted from Telegram.

The bakery had photos, a voice, and no time. The job was not to write a scheduler, it was to make the decision to post take one tap while keeping the words and the picture honest.

• No new appThe owner already answers customers in Telegram all day. Approvals arrive where the conversation already is.
• No blank pageCaptions are drafted ahead of time, so the choice is approve or reject, not write something from scratch.
• No wrong cakeEvery caption is checked against a description of the actual photo before it is offered.
• No silent double postA row can only be published once, even when a tap is retried or a request times out.

A queue file on the server is the source of truth. Generation happens on a timer; the approval loop is the only interactive part; publishing is a single Graph API call.

• DraftA cron job asks the model for a caption in the shop's voice, validates it, and adds it to the queue with its photo.
• ReviewThe bot sends the photo and the caption with two buttons, and remembers which row is on screen.
• PublishAn approve tap posts the photo to the Page, then replies with the public link.
• RecordThe row is marked posted and mirrored to a Published tab; rejections go to a Rejected tab with the reason.

A caption is only useful if it is true. Three gates run before a draft ever reaches the phone, and a draft that fails is thrown away rather than sent with a warning.

const shared = subject_words(caption)
  .filter(w => photo_words.has(w));

if (!shared.length) {
  reject('caption does not match the photo');
}

rules: words 20..80
       hashtags === 4, PascalCase
       lines >= 5, one clause each
       no question marks
       banned: "elevate", "indulge", "—"

text.replace(/\s*[—–]\s*/g, ', ')

The tap is the fragile part. Telegram retries, requests time out, and an ack can arrive after the post is already live. The rules below keep one row from becoming two posts.

POST /{page-id}/photos
  url      = {public image url}
  caption  = {approved caption}
  access_token = {page token}

-> { id, post_id }

{
  "node": "Send ack",
  "onError": "continueRegularOutput"
}

if (status === 'Publishing'
    && age > 10 * 60 * 1000) {
  status = 'Queued';
}

What it does not do, written down so nobody assumes otherwise.

• One photo per postEach post carries a single picture. Several shots of the same cake go out as separate posts, because albums are not built.
• Every photo has to be looked at firstA photo needs a description on file before it can be captioned, so a fresh batch waits its turn and takes a little while to become postable.
• The words are set per shopThe voice is chosen once when the bot is set up. Changing the language or the tone means rewriting the instructions it works from, not flipping a switch.
• Someone still approvesNothing goes out on its own. The owner keeps the last word, which also means nothing is posted on a day nobody checks Telegram.