Fix Telegram bot environment configuration

- Updated .env with correct TELEGRAM_BOT_TOKEN and N8N_WEBHOOK_URL
- Added env_file directive to docker-compose.telegram-bot.yml
- Telegram bot now starts successfully with /validate command working

.env

@@ -153,7 +153,7 @@ CONFIRMATION_TIMEOUT_MS=30000
 # n8n instance URL (for workflow automation)
 # Get from: https://n8n.io (cloud) or self-hosted
 # Example: https://your-username.app.n8n.cloud
-N8N_WEBHOOK_URL=https://your-n8n-instance.com
+N8N_WEBHOOK_URL=https://flow.egonetix.de/webhook/3371ad7c-0866-4161-90a4-f251de4aceb8
 
 # n8n API key (if using n8n API directly)
 N8N_API_KEY=your_n8n_api_key
@@ -171,8 +171,8 @@ TRADINGVIEW_WEBHOOK_SECRET=your_tradingview_webhook_secret
 # 1. Create bot: Message @BotFather on Telegram, send /newbot
 # 2. Get token from BotFather
 # 3. Get chat ID: Message @userinfobot or your bot, it will show your chat ID
-TELEGRAM_BOT_TOKEN=1234567890:ABCdefGHIjklMNOpqrsTUVwxyz
-TELEGRAM_CHAT_ID=123456789
+TELEGRAM_BOT_TOKEN=8240234365:AAEm6hg_XOm54x8ctnwpNYreFKRAEvWU3uY
+TELEGRAM_CHAT_ID=579304651
 
 # Discord Webhook (good for team channels)
 # 1. Go to Discord channel settings

docker-compose.telegram-bot.yml

@@ -7,6 +7,8 @@ services:
       dockerfile: Dockerfile.telegram-bot
     container_name: telegram-trade-bot
     restart: unless-stopped
+    env_file:
+      - .env.telegram-bot
     dns:
       - 8.8.8.8
       - 8.8.4.4