Any service can now write to you in Telegram

Half of all services have webhook notifications and no Telegram notifications. A payment went through, a build failed, a form was submitted: the event exists, but it sits in somebody else’s panel that nobody looks at. This is the shortest bridge from such a system to a person.

What is inside

1. Call from outside — the entry. The request body arrives on the data port.
2. Message text — a template. It currently prints everything that arrived as formatted JSON, so you can see which fields actually come through.
3. Message in Telegram sends the assembled text.
4. Done — the exit.

Notice the reference in the text field: {{ nodes.compose.output }}, not {{ inputs.input }}. The send node has no input port for text — its link to the previous step is an execution one — so the text is taken by node name. Getting this wrong does not fail; it sends an empty string.

What to set up for yourself

• The text. Once you can see what arrives, replace the whole-JSON dump with the fields you want: 💰 Payment {{ nodes.entry.data.webhook.payload.amount }} for order {{ nodes.entry.data.webhook.payload.order_id }}.
• The chat in the send node: REPLACE_ME to a chat or channel id.
• Different events. If the system posts several event types to one address, put a branch on the type field after the entry, so only what you care about reaches the chat.

What to connect

A Telegram bot and the Webhook target on the Publish tab. The address with its key goes into the other system. The key is the protection: the address does not work without it, so do not publish it where strangers will see it.