Message bridging
Discord and Telegram, in real time.
Real-time channel sync between Discord and Telegram, including authors, attachments, edits, replies, and reactions. Choose which messages get forwarded using the same condition builder you’d use for automations.
What a bridge does
- Cross-Platform Support
- Bridge messages between Discord and Telegram seamlessly
- Smart Filtering
- Use conditions to control which messages get bridged
- Custom Templates
- Format messages with variables and custom styling
- Channel Mapping
- Map specific channels between platforms
- Media Support
- Bridge images and files between platforms
- Real-time Sync
- Messages are bridged instantly as they are sent
Seven steps to a live bridge
Seven steps. The bridge stays disabled until the last save, so nothing is forwarded before you’re ready.
- 01
Add Your Servers
Connect your Discord and Telegram servers to Flake
- 01Invite the Flake bot to your Discord server with admin permissions
- 02Add the Flake bot to your Telegram group as an admin
- 03Verify both servers appear in your dashboard
- 02
Create a Bridge
Set up a new message bridge between your servers
- 01Navigate to the Bridge section in your dashboard
- 02Click "Create Bridge" to start the setup wizard
- 03Your new bridge will be created in disabled state
- 03
Configure Servers
Select which servers to bridge between
- 01Choose your origin server (where messages come from)
- 02Select your target server (where messages will be sent)
- 03Make sure both servers are active and properly configured
- 04
Map Channels
Define which channels should be bridged
- 01Select origin channels (leave empty to bridge all channels)
- 02Choose the target channel for bridged messages
- 03For Discord, a target channel is required
- 05
Set Conditions
Add filters to control which messages get bridged
- 01Add conditions to filter messages by content, author, or other criteria
- 02Use "contains" conditions for keyword filtering
- 03Group multiple conditions with AND/OR logic
- 06
Customize Message Format
Design how bridged messages will appear
- 01Use template variables to include sender info, timestamps, etc.
- 02Customize the message format for your community style
- 03Preview how messages will look before enabling
- 07
Enable and Test
Activate your bridge and verify it works correctly
- 01Save your configuration and enable the bridge
- 02Send a test message to verify bridging works
- 03Monitor the bridge performance in your dashboard
ready to configure
Open the dashboard and create the bridge.
The bridge editor walks the same seven steps. The first message goes through within seconds of enabling it.
Variables for the bridged format
Use these inside the message template to keep author, channel, and origin context on the receiving side.
- $username
The original sender's username
JohnDoe
- $message
The original message content
Hello everyone!
- $server
The source server name
Gaming Community
- $channel
The source channel name
#general
- $timestamp
Message timestamp
2:30 PM
- $platform
Source platform (Discord/Telegram)
Discord
Four common bridge shapes
Four shapes that show up across the customer base. Reach for the one that matches your conversation, not the most-features one.
- case · 01
Community Sync
Keep Discord and Telegram communities in sync
e.g. Bridge announcements from Discord #announcements to Telegram general chat
- case · 02
Support Channels
Provide support across multiple platforms
e.g. Bridge support requests between Discord #help and Telegram support group
- case · 03
Event Coordination
Share event information across platforms
e.g. Bridge event planning messages between Discord #events and Telegram events channel
- case · 04
Moderation Coordination
Keep moderator teams synchronized
e.g. Bridge moderator discussions between Discord #mod-chat and Telegram mod group
Common issues
still stuck
Talk to the people who wrote the code.
Support is run by the same team that ships the product. Both rooms below are watched during working hours, and answers do not go through a tier-one queue.