Overview

Platform-level Telegram mechanics — bot setup, resource linking, admin commands, deep-linking, and how the webhook stays in sync.

Telegram is the first connector Subscriby shipped, and the one with complete coverage today. A project that installs it connects one Telegram bot, and that bot is what actually admits, removes and bans members as their subscriptions change. Other connectors sit beside it on the same project (see Connectors); this section is about Telegram's own mechanics.

This section covers the platform-level mechanics. What you sell and who you sell it to lives in For Creators; what your members experience lives in For Subscribers.

You need your own bot

Subscriby drives a bot you create with Telegram's @BotFather and connect with its token. That is what makes the bot yours — your name, your handle, your branding — rather than subscribers interacting with something that says Subscriby.

Start here

Running it

What Telegram supports

CapabilityLimit or note
ChannelsSupported
Groups and supergroupsSupported, up to 200,000 members
Automatic add / removeDriven by subscription status, including expiry and cancellation
BansSupported, both manual and automatic
BroadcastsTargeted at a chosen audience of your subscribers
Native paymentsTelegram Stars (XTR), alongside every other supported provider
  • Platforms overview — what else is planned, and when
  • For Creators — projects, plans, resources and members
  • Payment methods — per-provider setup, Telegram Stars included
  • Webhooks — outbound events for your own automation, distinct from Telegram's own webhook

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request