Communication · Integration
Telegram
Add Telegram to your product for your customers, and give your AI agents governed access to it.
The Telegram integration worth embedding is the Bot API, and it is bot-scoped rather than account-scoped, which is the thing to be plain about: a customer creates their own bot, supplies its token, and your product then messages as that bot. Nobody authorises a personal Telegram account. The bot only reaches conversations somebody has started with it or added it to, so a group has to invite the bot before a single message can be sent there. Updates arrive either by webhook or by long polling, and only one of the two can be active per bot at a time. Messages are user-visible the instant they land, so sends are deduplicated per event rather than retried blindly. fastn keeps each bot token encrypted per tenant and follows the Bot API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer supply their own bot token, so notifications arrive from their bot rather than one you own.
Send alerts into the groups and channels a customer has added their bot to, with formatting and inline buttons.
Receive replies and button presses as updates, so a user can act on a notification without leaving the chat.
Choose webhook or long polling per bot, since only one delivery mode can be active at a time.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent posts an update into the chat a customer nominated, with the send logged and deduplicated.
An agent reads recent messages in a group it has access to before answering a question there.
An agent responds to a button press and runs the next step of a workflow within scoped permissions.
Example prompt
Post today's summary to the operations group through our bot and include a button to open the full report.
Set up Telegram in 4 steps
- 01Enable the Telegram connector in your fastn dashboard.
- 02Have each customer create their own bot and supply its token, since there is no personal account to authorise.
- 03Confirm which chats, groups and channels the bot has been added to, then choose webhook or long polling for updates.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Telegram integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Telegram integration without building it. Your customers connect their own Telegram account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Telegram update is not your on-call problem.
- One integration serves your product and your agents. The same governed Telegram connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
WhatsApp
Slack
DiscordOften used alongside
Tools the same teams tend to run next to Telegram, across other categories.
Aircall
Calendly
Gong
Google CalendarTelegram integration FAQ
How do I add a Telegram integration to my product?
Enable the Telegram connector in your fastn dashboard, then let each customer authenticate their own Telegram account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Telegram client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Telegram account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Telegram account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Telegram integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent posts an update into the chat a customer nominated, with the send logged and deduplicated.
Who maintains the Telegram integration?
fastn does. When Telegram changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own Telegram account?
Yes. Every customer authorises their own Telegram account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the Telegram integration?
A common starting point: let each customer supply their own bot token, so notifications arrive from their bot rather than one you own. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Telegram integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Telegram does not change your per-connector cost. You can start free with 3 connected accounts.
Add Telegram to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.