Skip to main content

Messaging Channels

Receive AI-powered security alerts on Telegram, Discord, or Slack. Aegis sends contextual descriptions with snapshots — and you can reply to ask follow-up questions.

Where to Find Channel Settings

⚙️ Settings → expand Persona → click Channels

You'll see a list of available channels, each showing its current status:

StatusMeaning
Enabled (green)Channel is active and sending/receiving messages
Configured (gray gear)Bot token is saved but channel is toggled off
Not setup (gray X)No credentials entered yet

Telegram Setup

  1. Open Telegram and start a chat with @BotFather
  2. Send /newbot and follow the prompts to create your bot
  3. Copy the bot token BotFather gives you
  4. In Aegis → Channels → select Telegram, paste the token into the Bot Token field
  5. Click Test Connection — if successful, you'll see your bot's username confirmed
  6. Toggle Enabled on
  7. Start a chat with your bot in Telegram to begin receiving alerts

Discord Setup

  1. Go to the Discord Developer Portal and click New Application
  2. Name your application, then go to the Bot section in the left sidebar
  3. Click Reset Token (or "Add Bot" if new) to generate a bot token — copy it
  4. Under Privileged Gateway Intents, enable:
    • Message Content Intent — required to read messages
    • Server Members Intent — optional, for member info
  5. Go to OAuth2 → URL Generator. Select the bot scope, choose permissions (Send Messages, Read Messages), copy the URL, and open it to invite the bot to your server
  6. In Aegis → Channels → select Discord, paste the token
  7. Click Test Connection to verify

Slack Setup

Slack requires more steps because it uses Socket Mode:

Step 1 — Create the App

Go to api.slack.com/appsCreate New AppFrom scratch. Name it (e.g., "Aegis-AI") and select your workspace.

Step 2 — Enable Socket Mode

Go to Settings → Socket Mode → toggle Enable Socket Mode ON → click Generate to create an App Token. Add scope connections:write. Copy the App Token (starts with xapp-).

Step 3 — Add Bot Scopes

Go to OAuth & PermissionsScopes → Bot Token Scopes, add all of these:

ScopePurpose
chat:writeSend messages
channels:historyRead channel history
channels:readSee channel list
im:historyRead DM history
im:readSee DM list
im:writeSend DMs
reactions:writeAdd reactions
reactions:readRead reactions
pins:writePin messages
pins:readRead pins
files:writeUpload files (snapshots)
users:readRead user info
app_mentions:readRespond to @mentions

Step 4 — Enable Events

Go to Event Subscriptions → toggle Enable Events ON → subscribe to bot events:

  • message.im — DMs to app
  • app_mention — @mentions in channels

Step 5 — Enable App Home DMs

Go to App Home → under Show Tabs, enable Messages Tab and check "Allow users to send slash commands and messages from the messages tab."

Step 6 — Install and Get Token

Go to Install AppInstall to Workspace → click Allow. Copy the Bot User OAuth Token (starts with xoxb-).

In Aegis, paste both the Bot Token (xoxb-) and the App Token (xapp-) into the Slack channel config.

After adding or changing scopes, you must reinstall the app to your workspace for changes to take effect.

DM Access Policy

Each channel has a DM Access Policy that controls who can send messages to your bot:

PolicyBehavior
Pairing (default)Users must enter a pairing code from the Aegis desktop app to link their account
AllowlistOnly specific user IDs can send messages — enter one ID per line
OpenAnyone can message the bot
DisabledDMs are turned off entirely

The Pairing mode is recommended — it ensures only people you authorize can interact with your security system.

Test Connection

After entering your bot token, click Test Connection to verify everything works. You'll see:

Success — green banner with your bot's username (e.g., "Connection successful! Bot: @YourBotName") → Error — red banner with the specific error message

Always test before enabling a channel.

Multiple Channels

You can configure and enable multiple channels simultaneously. For example:

→ Telegram for you → Discord for a family server → Slack for a work workspace

Each channel receives the same AI-generated alerts and supports two-way conversation.