Bot Integration Setup

Configure Telegram Bot with Make.com Automation

Integration Overview

This guide will help you set up the complete automation system with Telegram bot and Make.com integration for real-time data collection and automation.

Telegram Bot

Command interface

Make.com

Automation workflows

GEM Backend

Data processing

1 Create Your Telegram Bot

  1. Open Telegram and search for @BotFather
  2. Send command: /newbot
  3. Choose a name for your bot (e.g., "GEM Enterprise Bot")
  4. Choose a username ending in 'bot' (e.g., GEMEnterpriseBot)
  5. Save your bot token: 123456789:ABCdefGHIjklMNOpqrSTUvwxYZ
Important: Keep your bot token secure. Never share it publicly.
Configure Bot Settings

Send these commands to BotFather:

/setdescription
GEM Enterprise Bot - Automated security, real estate, and asset recovery services

/setabouttext
Advanced automation bot for cybersecurity monitoring, property management, and digital asset recovery.

/setcommands
start - Start the bot
help - Show available commands
scan_network - Security network scan
threat_report - Get threat assessment
property_list - View available properties
track_wallet - Monitor crypto wallet
status - Check system status

2 Create Telegram Channel

  1. In Telegram, click Menu → New Channel
  2. Name it: "GEM Enterprise Alerts"
  3. Make it Public or Private as needed
  4. Add your bot as an administrator with these permissions:
    • Post messages
    • Edit messages
    • Delete messages
  5. Get your channel ID:
    • Post any message in the channel
    • Forward it to @userinfobot
    • Save the channel ID (e.g., -1001234567890)

3 Set Up Make.com Automation

Create Make.com Account
  1. Go to make.com and sign up
  2. Create a new scenario
  3. Add the Telegram Bot module
  4. Connect with your bot token
Security Monitoring Workflow
Trigger
Bot Command
GEM API
Process
Response
Create Webhook in Make.com
  1. Add a "Webhooks" module as trigger
  2. Copy the webhook URL: https://hook.make.com/xxxxxxxxxxxxx
  3. Add "HTTP" module to send data to GEM API
  4. URL: https://www.gemcybersecurityassist.com/make/webhook
  5. Method: POST
  6. Headers: Content-Type: application/json
Webhook URLs:
GEM to Make.com: Your Make.com webhook URL
Make.com to GEM: https://www.gemcybersecurityassist.com/make/webhook

4 Configure Environment Variables

Add these environment variables to your application:

TELEGRAM_BOT_TOKEN=your_bot_token_here
TELEGRAM_CHANNEL_ID=-1001234567890
MAKE_WEBHOOK_URL=https://hook.make.com/your_webhook_id
Current Configuration Status
TELEGRAM_BOT_TOKEN Not Set
TELEGRAM_CHANNEL_ID Not Set
MAKE_WEBHOOK_URL Not Set
Please configure all environment variables to enable bot functionality.

5 Connect Bot to GEM Backend

Set your Telegram bot webhook to receive updates:

curl -X POST https://api.telegram.org/bot{YOUR_BOT_TOKEN}/setWebhook \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.gemcybersecurityassist.com/telegram/webhook"}'

6 Test Your Integration

Test Commands

Send these commands to your bot to test functionality:

/start

Initialize bot and receive welcome message

/status

Check system status and connections

/scan_network

Test security scanning workflow

Test Make.com Webhook

API Endpoints

Webhook Endpoints
Endpoint Method Description
/telegram/webhook POST Receives Telegram bot updates
/make/webhook POST Receives Make.com automation triggers
/telegram/bot-setup GET This setup page
Event Types for Make.com
  • security_alert - Security threat detected
  • property_update - Property status change
  • recovery_update - Asset recovery progress
  • user_onboarding - New user registration
  • schedule_viewing - Property viewing request

Troubleshooting

  • Check if webhook is properly set
  • Verify bot token is correct
  • Ensure bot has permission to read messages
  • Check server logs for errors

  • Verify webhook URL is correct
  • Check Make.com scenario is activated
  • Test with manual trigger in Make.com
  • Check webhook authentication if configured

  • Verify channel ID is correct (should start with -100)
  • Ensure bot is admin in the channel
  • Check bot has permission to post messages
  • Test with direct message first