Telegram Business

Telegram bot for business automation — lead capture forms, inline keyboard menus, FAQ matching, appointment booking flows, and payment integration. Use for b...

Security Scan

The skill's stated purpose (Telegram business bot) matches the single credential it asks for (TELEGRAM_BOT_TOKEN), but the runtime instructions reference many external integrations and Python scripts that are not included or declared, which is inconsistent and warrants caution.

Purpose & Capability

Name/description match the requested TELEGRAM_BOT_TOKEN and Telegram bot functionality — that credential is reasonable for a Telegram bot. However the SKILL.md discusses CRM integrations (GHL), payment providers (Stripe), lead-scorers and other scripts, but the package declares none of the additional environment variables or credentials those integrations would reasonably need.

Instruction Scope

The instructions tell the agent/user to run a variety of Python scripts (e.g. {baseDir}/scripts/telegram_business.py, ../ghl-crm/{baseDir}/scripts/ghl_api.py, lead_scorer.py) and to set up webhooks and CRM calls, but this skill bundle contains no code files — only SKILL.md. The instructions also reference relative paths and placeholders that appear inconsistent (mixing ../ and {baseDir}). That mismatch (instructions expecting local scripts and secrets that are not provided or declared) is an operational/integrity concern. The docs also show handling of PII (emails, phones) and payment flows — these are expected for purpose, but you should confirm where that data is stored and which services will receive it.

Install Mechanism

No install spec and no code files — lowest risk from arbitrary installers. This is an instruction-only skill, so nothing in the package will be written to disk by an installer step.

Credentials

Only TELEGRAM_BOT_TOKEN is declared (appropriate as the primary credential). However the documentation references Stripe/payment providers and CRM APIs without declaring required API keys, webhook secrets, or other env vars. That omission could be benign (the skill expects the user to supply them locally), but it is an inconsistency you should verify before trusting the skill.

Persistence & Privilege

The skill does not request always:true or any system config paths and does not request persistent installation. It allows normal autonomous invocation (disable-model-invocation:false) which is the platform default; combine that with a bot token only if you trust the skill's origin.

What to consider before installing

Do not paste your production TELEGRAM_BOT_TOKEN into an unsigned/untrusted skill without verifying its code and source. This package contains only documentation (SKILL.md) and no runnable scripts, yet its instructions reference many local Python scripts and third‑party integrations (CRM, payment) that would require additional API keys and webhook setup. Before installing: (1) request the source repository or the actual scripts and review them; (2) confirm exactly which additional credentials (CRM API keys, Stripe key, webhook secret) will be used and whether they are declared; (3) test with a throwaway bot token in a sandbox Telegram bot and an isolated environment; (4) validate webhook URLs and where lead/payment/PII data will be transmitted or stored; (5) prefer installing only after you can inspect the code or obtain a published upstream release from a trusted homepage/repository; and (6) if you do provision a real bot token and suspect compromise, rotate the token immediately.

Telegram Business Bot

Build business automation on Telegram — lead capture forms, appointment booking, FAQ bots, payments, and community management.

Quick Start

export TELEGRAM_BOT_TOKEN="123456:ABC-DEF..."

# Send a message
python3 {baseDir}/scripts/telegram_business.py send-message <chat_id> "Hello from your business bot!"

# Send inline keyboard
python3 {baseDir}/scripts/telegram_business.py send-menu <chat_id> "How can I help?" '[{"text":"📅 Book Appointment","callback_data":"book"},{"text":"❓ FAQ","callback_data":"faq"},{"text":"💬 Talk to Sales","callback_data":"sales"}]'

# Start lead capture
python3 {baseDir}/scripts/telegram_business.py send-lead-form <chat_id>

Bot Setup

1. Create Bot via @BotFather

1. Open Telegram, search for @BotFather
2. Send /newbot
3. Choose name and username (must end in bot)
4. Copy the token → set as TELEGRAM_BOT_TOKEN

2. Configure Bot

/setdescription - Business description shown on bot profile
/setabouttext - Short about text
/setuserpic - Bot avatar
/setcommands - Set command menu:
  start - Get started
  book - Book appointment
  faq - Frequently asked questions
  contact - Contact us
  help - Get help

3. Webhook Setup

# Set webhook (use your server URL)
python3 {baseDir}/scripts/telegram_business.py set-webhook "https://your-domain.com/webhook/telegram"

# Get webhook info
python3 {baseDir}/scripts/telegram_business.py get-webhook

# Delete webhook (switch to polling)
python3 {baseDir}/scripts/telegram_business.py delete-webhook

Available Commands

Messaging

# Send text
python3 {baseDir}/scripts/telegram_business.py send-message <chat_id> "Hello!"

# Send with HTML formatting
python3 {baseDir}/scripts/telegram_business.py send-message <chat_id> "<b>Bold</b> and <i>italic</i>" --html

# Send with Markdown
python3 {baseDir}/scripts/telegram_business.py send-message <chat_id> "**Bold** and _italic_" --markdown

# Reply to a message
python3 {baseDir}/scripts/telegram_business.py send-message <chat_id> "Got it!" --reply-to <message_id>

Inline Keyboards

# Simple menu (buttons in rows of 2)
python3 {baseDir}/scripts/telegram_business.py send-menu <chat_id> "Choose an option:" '[
  {"text":"Option A","callback_data":"opt_a"},
  {"text":"Option B","callback_data":"opt_b"},
  {"text":"Option C","callback_data":"opt_c"}
]'

# URL buttons
python3 {baseDir}/scripts/telegram_business.py send-menu <chat_id> "Visit us:" '[
  {"text":"🌐 Website","url":"https://example.com"},
  {"text":"📸 Instagram","url":"https://instagram.com/example"}
]'

# Answer callback query (acknowledge button press)
python3 {baseDir}/scripts/telegram_business.py answer-callback <callback_query_id> "Processing..."

# Edit message (update after button press)
python3 {baseDir}/scripts/telegram_business.py edit-message <chat_id> <message_id> "Updated text!"

Lead Capture

# Send lead capture form (multi-step inline flow)
python3 {baseDir}/scripts/telegram_business.py send-lead-form <chat_id>

# Process lead data (after collecting via conversation)
python3 {baseDir}/scripts/telegram_business.py process-lead '{"chat_id":123,"name":"John Doe","email":"[e-mail]","phone":"[phone]","interest":"AI automation","source":"telegram"}'

FAQ System

# Match question to FAQ
python3 {baseDir}/scripts/telegram_business.py faq-match "What are your business hours?"

# Send FAQ menu
python3 {baseDir}/scripts/telegram_business.py send-faq-menu <chat_id>

Media

# Send photo
python3 {baseDir}/scripts/telegram_business.py send-photo <chat_id> "https://example.com/image.jpg" "Caption here"

# Send document
python3 {baseDir}/scripts/telegram_business.py send-document <chat_id> "/path/to/file.pdf"

# Send contact card
python3 {baseDir}/scripts/telegram_business.py send-contact <chat_id> "[phone]" "John" "Doe"

Lead Capture Flow

The bot guides users through a multi-step form:

1. Start → Welcome message with menu buttons
2. "Get Quote" → Asks for name
3. User sends name → Asks for email
4. User sends email → Asks for phone (optional)
5. User sends phone → Asks for service interest (buttons)
6. User selects service → Confirmation + thank you
7. Lead data is output as JSON for CRM integration

Integration with CRM

# Capture lead from Telegram, score it, add to GHL
LEAD='{"name":"John","email":"[e-mail]","phone":"+1555...","source":"telegram"}'
SCORE=$(python3 ../lead-gen-pipeline/{baseDir}/scripts/lead_scorer.py "$LEAD")
python3 ../ghl-crm/{baseDir}/scripts/ghl_api.py contacts create "$LEAD"

FAQ Automation

Define your FAQ in the script's FAQ_DATABASE:

FAQ_DATABASE = [
    {"q": "What are your hours?", "a": "We're open Mon-Fri 9am-6pm EST.", "keywords": ["hours", "open", "schedule"]},
    {"q": "Where are you located?", "a": "123 Main St, New York, NY", "keywords": ["location", "address", "where"]},
    {"q": "How much does it cost?", "a": "Plans start at $99/mo. Reply 'pricing' for details.", "keywords": ["cost", "price", "pricing", "how much"]},
]

The FAQ matcher uses keyword matching + fuzzy similarity. For AI-powered matching, pipe through the LLM.

Payment Integration

Telegram supports native payments via Payment Providers (Stripe, etc.):

# Send invoice
python3 {baseDir}/scripts/telegram_business.py send-invoice <chat_id> '{
  "title": "Consultation Fee",
  "description": "1-hour AI automation consultation",
  "payload": "consultation_001",
  "provider_token": "STRIPE_TOKEN",
  "currency": "USD",
  "prices": [{"label": "Consultation", "amount": 9900}]
}'

Note: amount is in smallest currency unit (cents for USD). $99.00 = 9900.

Group Management

# Get chat info
python3 {baseDir}/scripts/telegram_business.py get-chat <chat_id>

# Get member count
python3 {baseDir}/scripts/telegram_business.py get-member-count <chat_id>

# Pin a message
python3 {baseDir}/scripts/telegram_business.py pin-message <chat_id> <message_id>

# Set chat description
python3 {baseDir}/scripts/telegram_business.py set-description <chat_id> "Welcome to our community!"

Webhook Payload Handling

When using webhooks, incoming updates look like:

Message:

{"update_id": 123, "message": {"chat": {"id": 456}, "from": {"id": 789, "first_name": "John"}, "text": "/start"}}

Callback (button press):

{"update_id": 124, "callback_query": {"id": "abc", "data": "book", "message": {"chat": {"id": 456}}}}

Parse with:

python3 {baseDir}/scripts/telegram_business.py parse-update '<json>'

Credits

Built by M. Abidi | agxntsix.ai YouTube | GitHub Part of the AgxntSix Skill Suite for OpenClaw agents.

📅 Need help setting up OpenClaw for your business? Book a free consultation