Can ConnectUC and Telegram Bot talk in both directions?

Yes. Build one flow that starts in ConnectUC 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 ConnectUC to Telegram Bot

Move data between ConnectUC 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 ConnectUC Explore Telegram Bot

ConnectUC triggers: 8
ConnectUC actions: 6
Telegram Bot triggers: 1
Telegram Bot actions: 20

Automation ideas

What you can build with ConnectUC and Telegram Bot

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

New Recording in ConnectUC creates Send Text Message in Telegram Bot
Triggers when a new call recording is available
New Update in Telegram Bot creates Create Contact in ConnectUC
Triggers when the bot receives a Telegram update (message, callback query, poll answer, etc.).
New Recording in ConnectUC creates Send Media in Telegram Bot
Triggers when a new call recording is available
New Update in Telegram Bot creates Set Do Not Disturb in ConnectUC
Triggers when the bot receives a Telegram update (message, callback query, poll answer, etc.).
New Recording in ConnectUC creates Send Document in Telegram Bot
Triggers when a new call recording is available
New Update in Telegram Bot creates Find CDR in ConnectUC
Triggers when the bot receives a Telegram update (message, callback query, poll answer, etc.).