Integrations
Telegram
This page has been cleared and is ready for updated Builder Studio documentation.
A Telegram integration would let a workspace send and receive messages through a Telegram bot, so a workflow could be triggered by an incoming chat message and reply back to a chat or channel. That is the intended purpose of this entry.
Not available today
Telegram is not a connectable integration in the current build. It is on the canonical list of removed runtime surfaces, and there is no live provider connection, bot setup, or message webhook for it. Do not plan a workflow around it yet.
Current status
- There is no Telegram provider you can add from the integrations surface.
- There is no Telegram bot-token setup, no chat link flow, and no inbound message webhook wired into execution.
- Any Telegram naming you encounter is residual branding or a legacy, removed data surface, not an active integration.
What to use instead
While there is no first-class Telegram connector, you can still reach external systems through general-purpose surfaces:
- Use webhook trigger and webhook call behavior to receive and send HTTP events from your own relay if you operate a Telegram bridge yourself.
- Use the MCP Tool node to call an external MCP server that wraps a messaging provider you control.
For connectable providers
See the Integrations overview for the list of providers you can actually connect today, such as Fal.ai, Google Gemini, ElevenLabs, GitHub, and Google Workspace.
Was this page helpful?