Skip to content
memberfy
US

Telegram

Turning Telegram on in Ready-made integrations: create a bot with BotFather, paste the token, add the bot to the group and use Find my group. Messages carry only the first name, in the community's language.

Telegram posts a short message to a group or channel through your bot: "Posts a short message to a Telegram group or channel through your bot."

Role: owner and admin. How to turn on, test, disable and remove any app is in Ready-made integrations.

1. Create the bot

  1. In Telegram, open a chat with @BotFather.
  2. Send /newbot, choose the name shown on the messages and the bot's username (it ends in bot).
  3. BotFather replies with the token, something like 123456789:AAH…. Copy it.

Use a bot just for Memberfy. A bot already connected to another service through a webhook does not let Memberfy find the groups ("This bot is connected to another service (webhook), so Telegram does not show its groups. Use a bot just for Memberfy.").

2. Put the bot in the group

  1. Add the bot to the group (or, in a channel, as an admin allowed to post).
  2. Send a message in the group. That is what makes the group show up for the bot.

3. Turn it on in Memberfy

  1. In Settings › Integrations and APIs › Integrations, click Telegram.
  2. Paste the token into Bot token.
  3. Under Group or channel, click Find my group and pick the group from the list. The id is filled in for you. If nothing shows: "No group found. Add the bot to the group, send a message there and try again."
  4. Choose the events and check This app will receive: ….
  5. Click Turn on and then Send test.

If you already know the group id (a negative number, like -1001234567890) or the @username of a public channel, you can type it straight into the field.

What reaches the group

The same messages as Discord, in plain text, without link previews, for the six events (member joined, purchase completed, subscription started, subscription canceled, event registration, course completed). Only the first name, never the e-mail, in the community's language.

Common problems

  • "The provider refused the credentials." The token was changed in BotFather (/revoke). Paste the new one and save.
  • "The provider could not find the channel or group." The bot left or was removed from the group. Add it again and test.
  • The app became Failing. See Turned off after failures.