Telegram bot for 1C metrics: architecture and security

Telegram Bot Architecture for Instant 1C Metrics Access

1C developers can build a Telegram bot that delivers real-time metrics to executives—like cash balances, daily profits, customer debts, and sales targets—without firing up the full 1C client. The system splits into three parts: an agent in the client's database, a VPS server, and the Telegram interface. This setup prioritizes security and keeps configuration dead simple: just enter a license key and connect.

Architecture: Three Independent Components

No monolithic dependencies here. The agent in the client database acts as a secure gateway, the server handles requests, and the bot crafts the user interface.

Client-Side Agent Extension

Installed as a 1C extension (.cfu file). It sends aggregated metrics over HTTPS—no business logic involved. Setup is straightforward: enter your license key and activate. The code is fully open-source for auditing—your team can verify exactly what's transmitted. It uses a blank configuration without the standard library (BSP) for faster updates and simplicity.

Open-source advantages:

• Transparency: See precisely which metrics are shared (balances, turnovers).
• No access to journal entries or personal data.
• Seamless integration with UT 11.5, UNF 3.0, BP 3.0+.

VPS Server Component

Deploy 1C with Apache on a Windows VPS. It receives packets from agents, validates subscriptions, and routes responses. The adapter pattern makes it easy to swap in Telegram, VK, or other messengers without touching the core. Caching keeps response times under 1 second.

Telegram Bot

Handles commands like /balance, /sales, /debts via webhooks. Built-in subscription payments. Two-factor auth: license key + ChatID.

Data Security Measures

Zero-tolerance for leaks or attacks. The agent sends only aggregated data—the server never sees individual transactions.

• HTTPS with certificate validation—every request is encrypted.
• RSA encryption—asymmetric keys thwart man-in-the-middle attacks.
• Context isolation—client data siloed in separate databases.
• Server-side validation—subscriptions checked centrally; agents can't be spoofed.
• Minimal storage—just metrics, no granular details.

Onboarding scenario:

• Grab your key from the bot.
• Install the .cfu in your 1C database.
• Enter the key and activate.

Requirements: 1C 8.3.20+, outbound HTTPS access.

Implementation and Scaling

SaaS model: server is proprietary, agent is open. Supports multiple databases and users (CEO, CFO, ops manager). Free tier for testing.

Live features:

• Multi-user access.
• Multiple databases per account.

Roadmap:

• Data anonymization.
• VK bot support.
• AI-powered natural language queries (read-only).
• Charts and PDF reports in chat.

This architecture works as a turnkey SMB solution or blueprint for custom bots.

Key Takeaways

• Security first: Aggregated metrics only, RSA encryption, 2FA—your data stays locked down.
• Effortless setup: Three steps, no RDP or web client needed.
• Scalable design: Messenger adapters, multi-database support.
• Open agent code: Full auditability builds trust.
• SaaS with free tier: $5–10/month or one-time license.

— Editorial Team