Connect your own Telegram bot token and Elastbiz becomes its backend: send messages from workflows and agents, receive updates through a secret-checked webhook, and keep everything as rows next to the customers it concerns.
Telegram bots usually run as one-off scripts with a webhook pointed at a box someone forgot about. The conversations never reach your CRM, and nobody can audit what the bot said.
Connect your bot token once — it’s stored host-side, per org. Sends go out through a plain endpoint your workflows can call; inbound updates are secret-checked and stored as rows linked to your business data.
Bot credentials live in per-org files on the host — never in the database, never echoed back.
POST /api_tg_send with a chat id and text. Workflows, agents and automations message customers through your bot.
Inbound updates carry your webhook secret and are compared in constant time before anything is stored.
Messages land on the substrate — auditable, searchable, linkable to the customer they belong to.
Because messages are rows, agents can read the thread and draft or send replies with the tools they already have.
This is your bot talking to your customers. No shared infrastructure bot, no third-party relay.
The same binary. The same substrate. Move between them with a data export.
We host Telegram at app.elastbiz.com. EU data residency, backups on us.
Docker one-liner. Your bot token and messages stay on your box.
Your token, your customers, your history — on the substrate your AI already reads.