Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure
How to: connect Telegram
Reach an evenfire agent from Telegram.
On minikube (quickstart stack)
- Complete the Quickstart so the platform runs.
- Create a bot via @BotFather; copy the bot token.
- In the Control UI, open External Channels (
/external-channels) → Create, pick your Host and the Telegram provider, enter the bot handle, paste the bot token as the write-only credential, and grant access to the users who may use it. See In the Control UI below. - Message the bot from the allowed user account.
Putting CLERUM_TELEGRAM_BOT_TOKEN / CLERUM_TELEGRAM_USER_ID in .env and
re-running make minikube-setup does not enable Telegram: setup no longer
writes channel credentials from .env, and the default minikube
CommunicationChannel declares no Telegram entry. channel-reader reads those
variables only in its standalone dev mode.
channel-reader polls Telegram and forwards allowed senders to mcp-host.
Users not in the allowlist are dropped.
Any cluster (CRD path)
Telegram is declared as a CommunicationChannel CRD bound to a Host, with
the bot token in a platform-managed Secret.
- Deploy the stack (Minikube guide for local).
- Create or edit a
CommunicationChannel(see CRD reference and examples). - Point
Host.spec.channelsat that channel. - Store the bot token in the Secret / channel credentials path your overlay
expects (see service README for
channel-reader).
Example shape:
apiVersion: clerum.io/v1alpha1
kind: CommunicationChannel
metadata:
name: all-channels
spec:
hostRef: 'chatllm'
telegram:
- channelId: 'telegram-general'
chatType: 'group' # required — private | group | supergroup
userIds: ['123456789'] # allowed senders
Both channelId and chatType are required on every telegram[] entry; the
API server rejects the resource without them.
In the Control UI
External Channels → /external-channels → Create builds the same
CommunicationChannel resource as the CRD path above: pick the host, the
Telegram provider, add the bot token as a write-only credential, and grant
access to specific users/teams — writing spec.access.users /
spec.access.teams (distinct from the legacy per-entry telegram[].userIds
pre-filter). See Control UI.
Approvals over Telegram
When approval policy enables Telegram approvers, approval requests arrive with
inline Approve / Deny buttons (or reply /approve / /deny); callbacks are
signature-checked and authorized before a decision is applied. See
Configure approvals.
Troubleshooting
| Symptom | Check |
|---|---|
| Bot never replies | Token set in .env? channel-reader deployed and READY? mcp-host healthy? |
| Your messages ignored | CLERUM_TELEGRAM_USER_ID / CRD userIds match your numeric id |
| Channel looks wired but silent | Channel CRD hostRef, secrets, channel-reader logs, NetworkPolicies |
More FAQ: FAQ.