Connectors

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 glanceCopy Anchor Link

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.

Available nowCopy Anchor Link

In public betaCopy Anchor Link

On the wayCopy Anchor Link

What every connector does the same wayCopy Anchor Link

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.

One plan on two platformsCopy Anchor Link

A project on the Growth Plan can run two connectors, and a plan can include places on both: a Telegram channel beside a Discord role, say. A member who pays gets every place the plan includes, whichever platform they bought through; the platforms differ only in how they let a member in.

What a member seesCopy Anchor Link

Every place a purchase includes is listed with where the member stands on it, on the receipt, on the membership page and in the bots, each with the connector's mark and the connector-named kind ("Discord Role · Ella's Kitchen"):

• You are in — the connector let them in itself: a Discord role, a server membership.
• Tap to join — a link the member walks in through: a Telegram invite link, a single-use Discord invite.
• Opens with the window — a pass held until its dates.
• Handed over by the organiser — a perk made by hand.
• Waiting for your … account — a place on a platform the member has not connected, with a Connect button in that platform's colour.

The portal's sidebar offers one button per connected platform, Open Telegram Bot and Open Discord Server, each with the platform's mark. The Discord button opens the server at its own address, which Discord shows only to the people already in it and turns everyone else away at the door; it is never an invite, because the server is what the project sells. The membership screen's and the portal Copilot's buttons use the same words.

A place on a platform the member has not connectedCopy Anchor Link

A member who signed in with one platform and bought a plan with a place on the other has access the connector cannot give yet: the core records the place as waiting and raises member.resource_pending. The member is shown it wherever they look. The receipt and the membership page list it with Connect Discord (or Connect Telegram); the Telegram bot's access screen lists it under Waiting for an account you have not connected with the same button; /subscriby status on Discord lists it under the membership line. The button is a signed door into the portal that lives half an hour: it signs the member in and opens the account page with the connect flow already started, so a Discord member sees the authorisation button and a Telegram member the bot's link and code. The same flow is under Account → Connected accounts, and signing in to the portal with the other platform links it too. Where it can, the bot's button opens the other platform directly instead: a Telegram member's Connect Discord opens Discord's authorisation page, a Discord member's Connect Telegram opens the project bot, and the command to type there (/subscriby link <code> on Discord, /start <code> on Telegram) is printed beside it, so nobody needs the portal in between.

A signed-in member who picks a plan with a place on a platform they have not connected is offered the connection on the checkout, above the plan summary and before the payment, with the same link and words; connected there, the access arrives with the receipt. Later puts it off, and the place waits as above.

A place still waiting a day after the purchase, or a pass window a day away, earns one reminder, in the member's chat and by mail, with the door; a member who stopped the project's follow-ups is never reminded, and the creator can switch the reminder off under Revenue Recovery → Settings.

The creator sees who waits: the Members page's Waiting on a Connection tab lists them, each row carries a chip naming the platform, and the flyout's Remind to connect sends the reminder at once. The REST API lists them with GET /v1/projects/{project}/members?access=waiting and nudges one with POST /v1/subscriptions/{subscription}/remind-connection; the Copilot's list_subscribers takes access: waiting and remind_member_to_connect does the same. A broadcast reaches the same members as one audience, Waiting on a Connection, from the composer, the bots, the API (audience: waiting_on_connection) and the Copilot. For a workflow, member.resource_pending is raised when the place starts waiting and member.resource_added when it lands, both carrying the same grant_id; the reminders in between raise nothing.

The moment the account is linked, every live purchase waiting on it is granted. Discord adds the member to the server with the role itself when their sign-in authorised the join, or mints a single-use invite otherwise; Telegram mints the member's invite link. The member is told in their chat and by mail that the place is theirs, member.resource_added fires, and the rows turn into You are in or Tap to join. Pass windows apply to the place whatever the platform: a role on a Thursday pass is given when the window opens and taken back when it closes. A purchase that ended before the account was linked is not granted late.

Build a connectorCopy Anchor Link

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.