Connect conversations across Discord channels

How Relay works

Each Relay joins two or more chosen text channels, with a maximum of 6 endpoints per Relay. One-way sends from the source to its destinations; two-way allows eligible messages to move in both directions. Relay uses managed Discord webhooks to show the sender's display name and avatar at the destination.

Setting up Relay Studio

1. Invite Relay into every participating server and enable Message Content Intent for the application.
2. Use /setup (Manage Server required) to open the visual dashboard.
3. Select connected servers, channels and direction, then enable the message features you need.
4. Review permissions and save. Sources need View Channel and Read Message History; destinations need permissions including Manage Webhooks, and suitable send permissions.
5. Send a test member message and check its destination and reply/edit behavior.

Supported content and safety

Eligible member messages can relay attachments, embeds, native link previews, reply context, edits, deletes and public threads. Private threads are not relayed. Arbitrary bot and webhook-authored messages are not mirrored, and Relay ignores its own webhooks to avoid loops. Destination mention parsing is suppressed so relayed messages do not automatically re-ping users, roles or @everyone.

Plans and message synchronization windows

The retention window controls how long older message edits and deletes can still be matched to destination copies. It is not a stored archive of conversation text. After downgrading, extra saved Relay routes remain configured but inactive until your plan allows them again.

Commands and troubleshooting

/help provides guidance; /setup opens Relay Studio; /relay status checks the current channel; /premium status shows your plan and limits. Missing permissions, deleted channels and disabled webhooks can make a Relay unhealthy; check the dashboard and repair the affected destination.