n8n Telegram "Send and Wait": Approve Before Anything Gets Published

If an n8n workflow writes to a live site, put a human approval step in front of the write. The Telegram node has a Send and Wait for Response operation that sends you a message with buttons and pauses the workflow until you tap one. This guide shows how I used it so that nothing is published until I approve it, and what I have and have not tested.

What I built

I run a workflow that reads new comments on my WordPress site, asks Gemini for a draft reply, and then asks me in Telegram whether to publish it. The full workflow is described in my Korean write-up, and the WordPress authentication is in this guide. Here I only cover the approval step. I use n8n 2.8.3, self-hosted.

The approval node

The node is a Telegram node with these settings, taken from my workflow.

When the node runs, the workflow pauses. The n8n documentation says the workflow stays paused until the user responds, and that Limit Wait Time is the only documented way to resume it automatically.

Only the approved branch is allowed to write

Right after the approval node I use an If node named Approved? that checks whether {{ $json.data.approved }} is true.

• The true output goes to the nodes that write to WordPress: approve the original comment, post the reply, then send a confirmation message.
• The false output has no node connected. If I tap the disapprove button, the workflow has nothing left to run and ends.

This is the whole safety idea. The write nodes are reachable only through the approved branch, so a missed message, a wrong tap or a failed run cannot publish anything by accident.

What I tested

On 2026-10-07 I ran the workflow by hand with a test comment and tapped the approve button. After that, the original comment was approved on the site, the reply was posted, and I received the confirmation message. Nothing was written to the site before I tapped the button.

Options worth knowing about

These come from the n8n Telegram documentation. I did not set them in my workflow, so I describe them only as documented.

• Approve Within Chat lets you respond with one tap on the buttons instead of opening a browser link. It requires n8n to be reachable over public HTTPS on port 443, 80, 88 or 8443. If those conditions are not met, or the option is off, the node sends link buttons instead.
• Restrict Who Can Approve takes a comma-separated list of Telegram user IDs. If you leave it empty, anyone who can see the message can respond, which matters if you send the message to a group.
• Limit Wait Time resumes the workflow automatically after an interval or at a given time.
• After Decision controls whether the buttons are removed after someone responds.

The n8n documentation for the Wait node says a paused execution is offloaded to the database and reloaded when the resume condition is met. That page is about the Wait node, not the Telegram node, so I mention it only as related background.

What I did not test

• The disapprove path. By the structure of my workflow nothing is connected to the false output, but I have not tapped the disapprove button and checked the execution. Treat it as expected behavior, not as a result.
• I did not record whether my approve taps opened a browser page or worked inside the chat. My workflow leaves the Approve Within Chat option unset, which the documentation says means link buttons.
• I did not test Limit Wait Time, Restrict Who Can Approve, or what happens to a waiting execution if n8n restarts.
• I tested one n8n version (2.8.3). Option names may differ in other versions.

Sources: n8n Telegram node, message operations and n8n Wait node.