Can ntfy and Telegram Bot talk in both directions?

Yes. Build one flow that starts in ntfy and acts in Telegram Bot, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect ntfy to Telegram Bot

Move data between ntfy and Telegram Bot the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore ntfy Explore Telegram Bot

ntfy triggers: 1
ntfy actions: 8
Telegram Bot triggers: 1
Telegram Bot actions: 20

Automation ideas

What you can build with ntfy and Telegram Bot

A few flows teams run between ntfy and Telegram Bot. Use one as a starting point, or build your own from scratch.

New Message in ntfy creates Send Text Message in Telegram Bot
Triggers when a message is published to a ntfy topic. Needs the server to cache messages (ntfy.sh keeps them 12 hours); messages sent with "Do not cache" are never seen.
New Update in Telegram Bot creates Send Notification in ntfy
Triggers when the bot receives a Telegram update (message, callback query, poll answer, etc.).
New Message in ntfy creates Send Media in Telegram Bot
Triggers when a message is published to a ntfy topic. Needs the server to cache messages (ntfy.sh keeps them 12 hours); messages sent with "Do not cache" are never seen.
New Update in Telegram Bot creates Send File in ntfy
Triggers when the bot receives a Telegram update (message, callback query, poll answer, etc.).
New Message in ntfy creates Send Document in Telegram Bot
Triggers when a message is published to a ntfy topic. Needs the server to cache messages (ntfy.sh keeps them 12 hours); messages sent with "Do not cache" are never seen.
New Update in Telegram Bot creates Update Notification in ntfy
Triggers when the bot receives a Telegram update (message, callback query, poll answer, etc.).