//Message Bridging

Message Bridging

Complete guide to cross-platform messaging

Core Feature
Discord
Telegram

Message bridging allows you to connect Discord and Telegram servers, automatically forwarding messages between platforms to keep your communities synchronized. This guide covers everything from basic setup to advanced configuration options.

Overview

What is Message Bridging?

Message bridging creates a real-time connection between your Discord and Telegram servers, automatically forwarding messages from one platform to another. This keeps your communities synchronized regardless of which platform they prefer.

Discord Server

Original message posted

Bridge
Telegram Group

Message automatically forwarded

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

Setup Guide

  • Invite the Flake bot to your Discord server with admin permissions
  • Add the Flake bot to your Telegram group as an admin
  • Verify both servers appear in your dashboard

Ready to get started?

Create your first message bridge and start connecting your communities.

Advanced Configuration

Message Filtering

Control which messages get bridged using conditions

Contains Condition

Filter messages based on content keywords

message contains “announcement“

User Conditions

Filter by sender role or username

user has role “Moderator“

AND/OR Groups

Combine multiple conditions with logic operators

(message contains “event“ OR message contains “announcement“) AND user has role “Staff“

Channel Mapping

Configure which channels to bridge

Discord (Origin)

  • • Select multiple channels (optional)
  • • Leave empty to bridge all channels
  • • Commonly used for #announcements

Telegram (Target)

  • • Select one target channel
  • • Required for Discord targets
  • • Usually the main chat

Message Templates

Template Variables

Customize message formatting with dynamic variables

{username}

The original sender's username

Example: JohnDoe

{message}

The original message content

Example: Hello everyone!

{server}

The source server name

Example: Gaming Community

{channel}

The source channel name

Example: #general

{timestamp}

Message timestamp

Example: 2:30 PM

{platform}

Source platform (Discord/Telegram)

Example: Discord

Template Examples

Basic Format

[{server}] {username}: {message}

Output: [Gaming Community] JohnDoe: Hello everyone!

Detailed Format

🔗 **{platform}** message from **{username}** in {channel}:
{message}
Sent at {timestamp}

Includes platform info, timestamp, and formatting

Simple Format

{message}

Forward just the message content without metadata

Common Use Cases

Community Sync

Keep Discord and Telegram communities in sync

Example: Bridge announcements from Discord #announcements to Telegram general chat

Support Channels

Provide support across multiple platforms

Example: Bridge support requests between Discord #help and Telegram support group

Event Coordination

Share event information across platforms

Example: Bridge event planning messages between Discord #events and Telegram events channel

Moderation Coordination

Keep moderator teams synchronized

Example: Bridge moderator discussions between Discord #mod-chat and Telegram mod group

Troubleshooting

Messages are not being bridged

Check that both servers are active, the bridge is enabled, and the bot has proper permissions in both platforms.

Only some messages are bridged

Review your bridge conditions - they may be filtering out certain messages. Check the conditions section of your bridge configuration.

Images are not bridging properly

Ensure both platforms support the media format and the bot has media upload permissions in the target channel.

Bridge is showing as offline

This usually indicates a connectivity issue. Check that both servers are connected and the bridge service is running.

Message formatting looks wrong

Different platforms have different markdown support. Adjust your template to account for platform-specific formatting.

Still having issues?

If you're experiencing problems not covered here, our support team is ready to help.