Channels

Telegram

Prerequisites

• A Telegram account
• The Telegram app (mobile or desktop)

Step 1: Create a Bot

1. Open Telegram and search for @BotFather
2. Send /newbot
3. Enter a display name (e.g., “My Exolvra Assistant”)
4. Enter a username (must end in bot, e.g., my_exolvra_bot)
5. BotFather responds with your bot token — copy it

Step 2: Configure in Exolvra

1. Open the Exolvra dashboard and go to Channels
2. Click Configure on the Telegram card
3. Check Enabled
4. Paste the bot token from BotFather
5. Leave “Allowed Chat IDs” empty to allow anyone, or enter specific IDs to restrict access
6. Click Save Channel Settings
7. Restart Exolvra

Step 3: Start Chatting

1. Open Telegram and search for your bot’s username
2. Press Start or send any message
3. The bot responds through Exolvra’s AI agent

Finding Your Chat ID

If you want to restrict access to specific users:

1. Send a message to the bot with “Allowed Chat IDs” empty
2. Check the Exolvra console logs — you’ll see:

   Received Telegram message from Username (chat 123456789)

3. Copy the chat ID number
4. Add it to the “Allowed Chat IDs” field (comma-separated for multiple users)
5. Save and restart

Telegram troubleshooting

Discord

Prerequisites

• A Discord account
• Access to the Discord Developer Portal

Step 1: Create a Discord Application

1. Go to https://discord.com/developers/applications
2. Click New Application
3. Enter a name (e.g., “Exolvra Assistant”) and click Create

Step 2: Create a Bot User

1. In your application, go to the Bot tab
2. Click Add Bot (if not already created)
3. Under Token, click Reset Token and copy the token
4. Enable these Privileged Gateway Intents:
   • Message Content Intent
   • Server Members Intent (optional)

Step 3: Invite the Bot to Your Server

1. Go to the OAuth2 tab, then URL Generator
2. Under Scopes, check bot
3. Under Bot Permissions, check:
   • Send Messages
   • Read Message History
   • Read Messages / View Channels
4. Copy the generated URL and open it in your browser
5. Select the server to add the bot to and click Authorize

Step 4: Configure in Exolvra

1. Open the Exolvra dashboard and go to Channels
2. Click Configure on the Discord card
3. Check Enabled
4. Paste the bot token
5. Optionally add Guild IDs to restrict which servers the bot responds in
6. Click Save Channel Settings
7. Restart Exolvra

Step 5: Start Chatting

1. Go to your Discord server where the bot was added
2. Send a message in any channel the bot can see
3. The bot responds through Exolvra’s AI agent
4. You can also DM the bot directly

Finding Your Guild (Server) ID

1. In Discord, go to Settings → Advanced and enable Developer Mode
2. Right-click on your server name in the sidebar
3. Click Copy Server ID

Discord troubleshooting

Slack

Prerequisites

• A Slack workspace where you have admin permissions
• Access to the Slack API portal

Step 1: Create a Slack App

1. Go to https://api.slack.com/apps
2. Click Create New App
3. Choose From scratch
4. Enter a name (e.g., “Exolvra Assistant”) and select your workspace
5. Click Create App

Step 2: Configure Bot Permissions

1. In the app settings, go to OAuth & Permissions
2. Under Bot Token Scopes, add:
   • chat:write — Send messages
   • channels:history — Read messages in public channels
   • groups:history — Read messages in private channels
   • im:history — Read direct messages
   • im:write — Send direct messages
   • app_mentions:read — Respond to @mentions

Step 3: Install to Workspace

1. Go to OAuth & Permissions
2. Click Install to Workspace
3. Review the permissions and click Allow
4. Copy the Bot User OAuth Token (starts with xoxb-)

Step 4: Enable Events (Webhook Mode)

1. Go to Event Subscriptions and toggle Enable Events on
2. Set the Request URL to http://your-exolvra-host:5079/api/webhooks/slack
   • For local development, use a tunnel service like ngrok: ngrok http 5079
   • Then use the ngrok URL: https://abc123.ngrok.io/api/webhooks/slack
3. Under Subscribe to bot events, add:
   • message.channels
   • message.groups
   • message.im
4. Click Save Changes

Step 5: Configure in Exolvra

1. Open the Exolvra dashboard and go to Channels
2. Click Configure on the Slack card
3. Check Enabled
4. Paste the Bot User OAuth Token
5. Optionally paste the App Token (for Socket Mode, starts with xapp-)
6. Click Save Channel Settings
7. Restart Exolvra

Step 6: Start Chatting

1. In Slack, invite the bot to a channel: /invite @Exolvra Assistant
2. Send a message mentioning the bot or in a DM
3. The bot responds through Exolvra’s AI agent

Slack troubleshooting

Console (local CLI)

The Console channel provides a text-based chat interface directly in the terminal where Exolvra is running. No external accounts or setup required.

Configure

1. Open the Exolvra dashboard and go to Channels
2. Click Configure on the Console card
3. Check Enabled
4. Optionally change the prompt prefix (default: You> )
5. Click Save Channel Settings
6. Restart Exolvra

Usage

After restart, you’ll see in the terminal:

=== Exolvra Console Chat ===
Type your message and press Enter. Type 'exit' to quit.

You> Hello!
Assistant> Hi! How can I help you today?
You> exit

The console channel is useful for quick testing without opening the dashboard, headless server environments without a browser, and scripted interactions via piped input.

Managing channels

Viewing status

The Channels page shows the current status of each adapter:

• Active (green) — connected and receiving messages
• Stopped — configured but not running (usually means the app needs a restart)
• Not configured — no token or credentials set

Multiple channels

You can enable multiple channels simultaneously. Each channel creates separate sessions, and all conversations are visible in the Sessions page. Budget tracking applies across all channels.

Security

• Sandboxing — by default, messages from external channels (Telegram, Discord, Slack) run in sandboxed sessions with restricted tool access. Main sessions (dashboard chat) have full access.
• Allowlists — use chat ID or guild ID allowlists to restrict who can interact with the bot.
• Tokens — all tokens are stored in the local database, not in the git repository.