Docs / Integrations / Telegram
Telegram Integration
Bring your own bot token (BYOB) to receive and send messages in WeKeKe.
Telegram connects through your own BotFather bot token. During connect, WeKeKe validates the token, registers a webhook for your account, and stores credentials encrypted at rest.
Prerequisites
- A Telegram bot created via BotFather.
- Your bot token from BotFather (for example: 123456789:AA...).
- A public HTTPS webhook base URL configured for your WeKeKe environment.
Connect in WeKeKe
1
Open Integrations
Go to Integrations in the sidebar.
2
Click “Connect Telegram”
Paste your BotFather token in the connect modal.
3
Optional webhook base URL
If needed, enter a custom public origin (for example, staging domain or tunnel).
4
Confirm connected state
Look for a green “Connected” status and account handle in the card.
Inbound message behavior
- Telegram delivers messages to WeKeKe through the registered webhook.
- A user must start or message your bot first before the chat appears in Inbox.
- Incoming messages are stored and can trigger automation rules.
Security notes
- Bot tokens are encrypted at rest before being persisted.
- Webhook requests are validated with a secret token header.
- Disconnect removes the stored token and unregisters the webhook.
Troubleshooting
- 401 Unauthorized: rotate bot token via BotFather and reconnect.
- No inbox updates: check webhook URL reachability and secret mismatch.
- Webhook 404: verify your base URL points to the active deployment.