WeKeKeWeKeKe
Sign InStart Trial
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 account that can DM @BotFather.
  • 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.

Create your bot with BotFather

1

Start BotFather

In Telegram search, open @BotFather and send /start.

2

Create bot credentials

Send /newbot, choose a display name, then choose a username ending in bot.

3

Copy your token

BotFather returns your API token. Copy it exactly and keep it private.

4

Optional: configure profile details

Use BotFather commands like /setdescription and /setuserpic so the bot is recognizable to fans.

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.

Account options roadmap

  • Current: one connected Telegram bot account per creator.
  • Planned: support additional Telegram bot accounts where operationally feasible.
  • Final behavior depends on provider and webhook constraints in each environment.