Overview

How connectors work — the platforms a project runs on, what is live today, what is on the roadmap, and how to build one.

A Subscriby project runs on connectors. A connector is the package that speaks to one platform: it admits and removes members from the places you gate, carries your messages, verifies who a member is, and, where the platform has one, takes its native payment. A project installs any number of them, a plan can mix resources across them, and one purchase grants access on all of them.

Every connector is listed on the public Connectors Marketplace, lane by lane, straight from the same catalogue the dashboard installs from. The per-project Connectors page is where you install one, connect it, watch its health and remove it.

Status at a glance

Connector	Lane	Places it gates	Broadcast	Access codes	Native payment
Telegram	Available now	Channels, groups and supergroups	✅	✅	Telegram Stars
Discord	Under development	Servers and roles	—	—	—
Slack	Coming soon	Workspaces and channels	—	—	—
WhatsApp	Coming soon	Groups	—	—	—

Also listed as Coming Soon on the marketplace: Microsoft Teams, Discourse, Ghost, Google Drive, GitHub, Reddit, Guilded and Zoom. The roadmap says what each lane means and what "coming soon" commits us to.

One connector is free; a second one on the same project needs Growth

Official connectors cost nothing. Installing a second connector on one project, or publishing a plan whose resources span two connectors, needs the multi_connector capability, which the Growth plan carries. The Connectors page says so before you install.

Available now

Complete coverage, live today.

Your own bot, created with @BotFather and connected with its token, runs the membership: members are admitted to private channels, groups and supergroups the moment they pay and removed when their access ends, broadcasts go out paced inside Telegram's limits, Telegram Stars is a payment method, and the whole creator toolkit is reachable from the platform bot as well as the dashboard.

Advantages — why creators start on Telegram.
Onboarding — create your account and connect your first bot.
Bot features — what subscribers see.
Admin commands — creator controls inside the bot.

On the way

Discord

Under development.

Server memberships granted as roles, with single-use invites for members who are not in the server yet, and slash commands for creators.

Slack

Coming soon.

Workspace-based memberships and paid channels, with member management through Slack's bot APIs.

Coming soon.

Group memberships through the WhatsApp Business API, with template-based messages.

What every connector does the same way

Whatever the platform, a connector plugs into the same Subscriby:

Access — a paid subscription turns into a grant on each resource of the plan. The connector decides how a grant is delivered (an invite link, a membership, a role, or a task for you to do by hand); the subscription rules decide when it starts and ends.
Identity — a member is one person with an account on each connector they use. The portal is where they link and unlink those accounts, and a purchase made before an account is linked waits as a pending grant until it is.
Messages — confirmations, reminders, broadcasts and support replies are written once and rendered by each connector in its own format and within its own limits.
Health — every installation and every gated place is probed on a schedule; the Disaster Recovery Program uses the same probes to know when to act.
Recovery — standby installations, standby places and account relinking exist wherever the platform lets a connector offer them; the readiness checklist only ever lists what your connectors can do.

Build a connector

Connectors are Composer packages built on the Subscriby connector SDK. Building a connector explains the manifest, the ports, the data rules and the conformance kit a package passes before Subscriby reviews and installs it.