How to Set Up Content Approval via Telegram Bot

Telegram beats email and Slack for content approval on three dimensions. First, it is on a device people already check constantly — making the probability of a fast response much higher than a separate platform. Second, Telegram bots support InlineKeyboard buttons that attach directly to a message, so the approver can act without opening a link or navigating to a different interface. Third, the Telegram Bot API allows programmatic control of the entire flow — sending, receiving button callbacks, and triggering downstream workflow steps — with a simple, well-documented API.

The system has three components: the content generation workflow (upstream), the Telegram bot (the approval interface), and the publishing workflow (downstream). The Telegram bot is the bridge — it receives generated content from upstream, presents it to the approver, collects the decision, and passes the result downstream.

The bot itself is typically not a standalone application — it is an n8n workflow with a Telegram Bot node at its center. The bot does not need to run continuously; it responds to webhook events sent by Telegram when a button is pressed. This makes it serverless-compatible and extremely low-overhead.

The content preview message should contain everything the approver needs to make a decision in under 30 seconds. Use Telegram's MarkdownV2 formatting to structure it clearly. A standard preview for a social post should include: the target platform (bold header), the proposed publish date and time, the full post text, hashtags, and a note on the content format (carousel, single image, Reel, etc.).

For high-volume batches, group multiple posts in a single message session rather than sending one message per post. Send posts as a numbered list in one message, then attach the InlineKeyboard with numbered Approve buttons for each item. This lets the approver process 10 posts in a single Telegram session without scrolling through a flood of individual messages.

Each InlineKeyboard button carries a callback_data string that the n8n webhook receives when pressed. Use a consistent naming convention: "approve_{postId}", "edit_{postId}", "reject_{postId}". In your n8n workflow, a Switch node routes on this callback_data value. Approve routes to the scheduling queue. Edit triggers a re-generation prompt asking the approver what to change, then loops back with a new draft. Reject discards the post and logs the reason.

Set a timeout on the Wait node — 48-72 hours is practical for most businesses. If no response arrives in that window, the workflow auto-sends a reminder message and waits another 24 hours. If still no response, the post is held in draft status for manual review rather than auto-published.

Approved posts enter the scheduling queue in your publishing layer. If you are using a tool like Buffer or Airtable as a scheduling hub, the n8n workflow writes the approved post data (text, platform, scheduled time) to the appropriate record. If you are publishing directly via API, the post enters a time-based queue and fires at the designated time.

A confirmation message is sent back to the Telegram approval chat: "Post approved. Scheduled for [platform] on [date] at [time]." This closes the loop and gives the approver visibility into the publishing schedule without needing to log into any separate dashboard.

A Telegram content approval workflow transforms a friction-heavy, asynchronous process into a 30-second mobile action. The combination of inline buttons, formatted previews, and automated downstream routing makes it the most practical approval interface for content factories operating at volume. If your team's content approval is currently happening over email or WhatsApp threads, this upgrade alone will cut your approval cycle time by 70-80%.