Telegram: reach Hermes from a private bot conversation

What Telegram is for

The official Telegram integration supports conversation, attachments, voice messages, and delivery of scheduled results. It is useful when the agent runs elsewhere and you want a familiar mobile interface. The bot is a route into the configured Hermes environment, so setup should include both connectivity and authorization. Begin with your own direct conversation before considering groups or recurring delivery.

What you need

• A Telegram account, a bot created through a documented setup route, and a running Hermes gateway.
• Protected bot credentials and an explicit allowed-user configuration for the intended audience.

Set it up

1. 1

   Follow the official desktop/dashboard setup or the documented manual bot setup. Store the token through the configured local secret mechanism rather than pasting it into ordinary chats. In the dashboard or Desktop app, use Messaging > Telegram > Create with QR. Or run hermes gateway setup, choose Telegram, and configure TELEGRAM_BOT_TOKEN and TELEGRAM_ALLOWED_USERS. Start hermes gateway and send a private test message.

2. 2

   Authorize the intended user, establish a private test conversation, and define which operations the agent may perform from that surface.

Check it works

• Send a harmless question and confirm the reply comes from the expected profile. Test an attachment or delivery destination only if the workflow requires it.
• Verify that an unapproved user cannot operate the agent and that a scheduled result reaches the intended conversation.

Limits and failure points

• Bot presence text is not proof of a healthy gateway or a successful task.
• Group visibility, membership and mention triggers are separate from access grants. An authorized user can reach the configured agent tools, including terminal access by default; use separate tool/approval/sandbox settings to restrict authority.

Messaging setup

All messaging platforms

• How to set up Hermes Agent on Telegram

Spotted something wrong or out of date? Tell us on X at @HermesWatcher↗ (opens in a new tab) and we will fix it.