Appearance
Telegram Bot
Connect HELIX to Telegram for mobile notifications and basic agent commands. The Telegram integration lets you stay informed about task activity and interact with your agents on the go.
Setting Up the Bot
Step 1: Create a Telegram Bot
- Open Telegram and message @BotFather
- Send
/newbot - Follow the prompts to name your bot (e.g., "HELIX Mission Control")
- BotFather gives you a bot token — copy it
Step 2: Connect to HELIX
Add the bot token to your HELIX configuration:
Via the onboarding wizard: Paste the token in the Telegram step during first setup.
Via environment variables:
bash
# In your .env file
TELEGRAM_BOT_TOKEN=123456789:ABCdefGHIjklMNOpqrSTUvwxyz
TELEGRAM_ALLOWED_USER_IDS=12345678,87654321Via Settings: Go to Settings > Integrations > Telegram and paste the bot token.
Step 3: Get Your User ID
To receive notifications, HELIX needs your Telegram user ID:
- Message @userinfobot on Telegram
- It replies with your user ID (a number like
12345678) - Add this to
TELEGRAM_ALLOWED_USER_IDSor enter it in your user profile settings
Step 4: Enable Notifications
Each user controls their own Telegram notifications:
- Go to Settings > Profile in the HELIX dashboard
- Toggle Telegram Notifications on
- Enter your Telegram User ID
- Save
Notification Types
The Telegram bot sends the same notifications as the in-app bell:
| Notification | Example Message |
|---|---|
| Task Assigned | "Task 'Write blog post' assigned to Sierra" |
| Task Completed | "Sierra completed 'Write blog post'" |
| Approval Needed | "Task 'Write blog post' needs your review" |
| Agent Error | "Sierra encountered an error on 'Write blog post'" |
| Mention | "Clement mentioned you in a comment on 'Write blog post'" |
Security
Allowed User IDs
The TELEGRAM_ALLOWED_USER_IDS environment variable restricts which Telegram users can interact with the bot. Only listed user IDs can:
- Receive notifications
- Send commands to the bot
This prevents unauthorized users from accessing your HELIX instance through Telegram.
Bot Token Security
Keep your bot token secret. If compromised:
- Go to @BotFather and use
/revoke - Create a new token
- Update the token in HELIX settings
- Restart HELIX services
Troubleshooting
Bot Not Sending Notifications
- Verify the bot token is correct in
.envor Settings - Check that your Telegram user ID is in
TELEGRAM_ALLOWED_USER_IDS - Confirm Telegram notifications are enabled in your HELIX profile
- Make sure you've messaged the bot at least once (Telegram requires this before a bot can message you)
- Check backend logs:
docker compose logs backend | grep telegram
Bot Not Responding to Commands
- Verify the bot is running: check gateway logs for Telegram connection
- Confirm your user ID is in the allowed list
- Restart the gateway:
docker compose restart gateway