Can OpenPhone and Telegram Bot talk in both directions?

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

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

OpenPhone triggers: 5
OpenPhone actions: 4
Telegram Bot triggers: 1
Telegram Bot actions: 20

Automation ideas

What you can build with OpenPhone and Telegram Bot

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

Call Recording Completed in OpenPhone creates Send Text Message in Telegram Bot
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
New Update in Telegram Bot creates Send Message in OpenPhone
Triggers when the bot receives a Telegram update (message, callback query, poll answer, etc.).
Call Recording Completed in OpenPhone creates Send Media in Telegram Bot
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
New Update in Telegram Bot creates Create Contact in OpenPhone
Triggers when the bot receives a Telegram update (message, callback query, poll answer, etc.).
Call Recording Completed in OpenPhone creates Send Document in Telegram Bot
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
New Update in Telegram Bot creates Update Contact in OpenPhone
Triggers when the bot receives a Telegram update (message, callback query, poll answer, etc.).