Discord Translator Bot Setup: Complete Configuration Guide

A reliable Discord translator bot setup starts with one decision: choose the target language for each audience, then attach that language to the right channel, role, category, or flag reaction. With Interaction Bot, log in through Discord, select your server, open Translation in the dashboard, add each configuration, and save the page. The walkthrough below covers every control you need after the bot has joined your server.

1. Open the dashboard and select your server

Go to Interaction Bot and click Login or Go to dashboard. Discord opens an OAuth consent screen for the identify and guilds scopes. After authorization, choose the server and click Configure. The official dashboard guide confirms that all configuration pages sit in the left navigation; on mobile, open it with the top-left menu button.

Before adding rules, make sure Interaction Bot can view the source channels and send messages in every destination channel. If you have not installed it yet, complete the invite first, then return here.

Roduz’s six-minute Interaction Bot walkthrough demonstrates the product-specific setup flow and slash-command translation alongside the dashboard configuration discussed below.

2. Choose the bot language and translation targets

On Overview, check the Bot Language card and select the available server-facing bot language. Do not mistake this for a universal translation target. Each automatic translation rule has its own Language field, so use that field as the output language for the audience covered by the rule.

Run /languages in Discord before you build rules if you need to confirm a language is available. The official translation command reference lists /languages, /translate <message> <language>, and /detect <message> as the basic checks.

A practical plan looks like this:

3. Configure per-channel automatic translation

Open Translation > Channel Translation, then click Add a configuration. According to Interaction Bot’s channel translation documentation, the three required choices are:

1. Channel: where the bot watches incoming messages.
2. Sending Channel: where it posts the translation. Choose the same channel for an inline multilingual chat, or a separate channel for a cleaner feed.
3. Language: the target language.

Open Options only when you need to change behavior. Style can be Embed, Webhook, or Message. Delete Message removes the original, Delete Translation removes the bot’s output, Translate Bot includes bot-authored messages, and Always Send also produces output when the message already matches the target language.

Click Save in the popup, then use the page-level Save control to publish the running configuration. Repeat the rule for another target language only if that audience genuinely needs a second output.

4. Enable flag-based translation

Open Translation > Flag Translation and add a configuration. Select the channel, switch Activated on, and choose a sending mode:

• Each time: translate whenever a new flag reaction is added.
• One time: translate only if flag translation has not already handled that message.

Auto Delete removes the translated output automatically. Save both the popup and the page. Members can now react to a message with a country flag emoji to request the corresponding language, which is also the first translation method shown in the official getting-started guide.

Flag mode is the lowest-noise option for channels where most members share a language but occasionally need help. Test with a flag that has an unambiguous language association, then verify the translation appears in the configured channel.

5. Restrict automatic translation by role

Open Translation > Role Translation and click Add a configuration. Choose a Discord role and its target Language. Interaction Bot will translate messages from members who carry that role when their message does not match the configured target, as the role translation guide explains.

The optional controls include Style, Sending Channel, Delete Message, Delete Translation, and Always Send. Leave Sending Channel empty to post beside the source message, or set a destination such as #staff-translations.

Role rules are filters, not Discord permission gates. Use them to target translation behavior, for example @Spanish to English, while Discord’s own channel permissions still decide who can read and write. Avoid giving one member several overlapping translation roles until you have tested the output, or one message may match multiple rules.

6. Translate an entire category

Open Translation > Category Translation, add a configuration, choose the category, and set its Language. This applies automatic translation across the channels currently grouped under that Discord category. Interaction Bot’s current dashboard also exposes Style, optional Sending Channel, Delete Message, Delete Translation, Translate Bot, and Always Send for category rules.

Use a category rule when channels share one audience and one target language, such as all channels under “Spanish Support.” Use individual channel rules when rooms need different targets or destinations. The command reference defines a category as the place where every channel underneath it should be translated and notes that the bot needs read and write access there.

7. Test the complete setup

Create or use a quiet test channel, then check one feature at a time:

1. Post a full sentence in a language different from the configured target. Confirm the translation appears in the intended sending channel and in the selected style.
2. Add a flag reaction to that original message. Confirm Each time or One time behaves as chosen.
3. Ask a member with the configured role to post the same test. Then repeat without the role to confirm the rule’s scope.
4. Post in two channels under the configured category. Move a temporary test channel outside the category and confirm the category rule no longer covers it.
5. Check deletion settings only after you have verified the text, because an enabled Delete Message rule can remove the source.

If nothing happens, first check that you saved the popup and the page. Then verify the bot can view the source, send in the destination, and read message history. Use /detect <message> on a representative sentence if automatic detection seems wrong. Interaction Bot’s FAQ warns that very short messages, emojis, and other noise can cause language misidentification; /config detector <char> can raise the minimum message length used for automatic translation.

Once each isolated test passes, repeat one real conversation path from start to finish. That final check catches overlapping rules, wrong destinations, and deletion settings before members encounter them.