Connect Discord

Discord connects the same way Slack does — one bot, added to a server. Once it’s in, running /investigate in any channel it can see starts a case, and alerts and watches can post there too once you pick a channel.

Install the bot

1. In the console, open your project’s settings and choose Integrations under Connections.
2. In the Discord section, click Add to Discord. You’re redirected to Discord to pick a server and approve the bot.
3. Approve the requested permissions — the bot needs to send messages, post embeds, and create threads for each investigation. Discord sends you back to the Integrations page, and a Discord connected confirmation appears.

If your server requires an admin to approve new apps, ask an admin to add the bot, then connect again.

Pick your channels

Once connected, the Discord section shows your server with a Connected badge and three more settings groups:

1. Under Channel routing, choose a Default channel — this is where an alert- or watch-triggered case posts when there’s no existing thread to reuse (a case that started with /investigate always replies in its own thread, regardless of this setting). Optionally set a Critical, Warning, or Info override to route those severities to a different channel; anything without an override falls back to the default. Pick No default channel to clear it.
2. If your project has more than one connected AWS account or Kubernetes cluster, use Channel scope to bind a channel to the one it means — add a channel binding, pick the AWS and/or Kubernetes connection, and /investigate in that channel always targets it.
3. Optionally turn on Quiet hours to defer non-critical posts to the end of a window you set — critical posts always go through immediately.
4. Click Save Discord settings.

There’s no test-message button here — nothing to test against until a default channel is configured and something posts.

What starts working

• Running /investigate in any channel the bot can see starts an investigation. The Investigator acknowledges right away and opens a dedicated thread for that case.
• Running /continue inside that thread follows up on the same investigation; run it at the channel level instead, and it follows up on whichever investigation was started there most recently.
• Alerts and watches deliver their results into the routed channel, opening their own thread there too, so a later /continue works the same way it would on a human-started investigation.
• When the Investigator needs input partway through, it asks in the thread — sometimes with a dropdown you can answer directly.

Daily use — how threads map to cases and how to answer a pending question — is covered in The Investigator in Discord.

Disconnect

The Discord section shows the connected server’s name and ID with a Connected badge. Click Disconnect to remove it — /investigate stops working in that server, but you can reconnect anytime.

If it doesn’t connect

• If you land back with a Connection failed message, the reason is shown — most commonly the install wasn’t completed, or your server needs admin approval first.
• If Discord couldn’t verify the app’s credentials, try connecting again; if it keeps failing, contact support.
• “This Discord server is already connected to another Microtica project” — a server can only be connected to one project at a time. Disconnect it from the other project first, then connect it here.

Next: Connect Git providers