Introducing the Discord Connector

The Discord connector is in public beta from today, in Subscriby 5.1.0. Open the Connectors Marketplace in any project, press Add to Discord, pick the server you manage, and one verified Subscriby app joins it: no bot to create, no token to paste. Put a role, a private channel or the whole server on sale, and a member who pays holds it the moment the payment settles and loses it the moment their access ends. On every plan, including Free; the card carries an Experimental badge while the beta runs.

Here is the one-sentence version: everything Subscriby does for a paid Telegram community it now does for a Discord server, from the same project, the same plans and the same member list.

The Short Version

• One verified app for every creator. Add it from the dashboard, drag its role above the roles you sell, and it grants and removes those roles for you. Nothing to host, nothing to keep alive.
• Three kinds of place: a role, a private channel (text, voice, stage or forum, gated behind a role the app manages) and membership of the server itself, each sold under one-time, recurring, pass and pass-series plans.
• Access follows payment, both ways. A member who connected their Discord account on your portal is added to the server by the app and given the roles; anyone else receives a single-use invite that is matched to their purchase the moment they arrive. When access ends the roles go, and a server plan either keeps the member’s seat or removes them, your choice per place.
• Create Members Area builds three private categories, eight channels and a role on sale in one press, beside whatever your server already has; nothing is replaced.
• Four slash commands. Members run /subscriby: what they hold, the plans with a Buy button, their passes, support, referrals and a cancel flow that offers your retention deal. You run /subscriby-admin, /subscriby-growth and /subscriby-support: plans, coupons, access codes, broadcasts, payment setup, referrals, the Partner Program, portal design, retention, Smart Links, the inbox, tasks and recovery, without leaving the server.
• Broadcasts post once in your announcement channel, mentioning the plans’ roles; members who asked for a copy get it as a direct message too.
• Support in the place you choose: members’ messages reach you as direct messages or as one thread per member in a private forum channel, and your replies go straight back.
• Linked Roles: a member can show a verified Subscriby membership on their Discord profile.
• Pass windows become scheduled events on voice and stage channels, and server-wide events for the rest, kept in step with the window for the month ahead.
• The Disaster Recovery Program covers Discord: every place on sale is checked every hour, the doctor names the fix rather than the fault, and standby places, a live channel mirror, one-action failover and identity relink are there on day one.
• Buy on one platform, get the place on the other. A member who bought a plan with a Discord role through your Telegram bot sees the waiting place on their receipt, on their membership page and in the bot, with the door to connect; they are reminded once, and you see who is waiting.
• Everywhere else you work: the REST API, the webhooks, the MCP tools, Zapier and n8n list a server’s roles and channels, sell a listed place and run the installation actions, and Subscriby Copilot answers “what is wrong with my connection?” from the doctor itself.

Why a Public Beta

The connector ran on production for a week in a private beta, on our own servers first, and the release that opens it carries what that week found. What the badge means now is simple: the connector is complete, it is open to every creator, and we are still watching it closely. Expect small changes between releases while it wears the badge, and tell us what you find: a reply to any Subscriby email reaches a person, and so does the support inbox in the dashboard. The badge comes off when the beta ends, and nothing you set up changes.

Getting Started

Three steps, in the order a first server takes them:

• Add the app. Open Connectors in your project, or the Connectors Marketplace, press Add to Discord, pick the server and approve what the app asks for; you come back with the server connected. Then drag the Subscriby role above the roles you will sell, in Server Settings. The doctor on the Connectors page tells you if it is not high enough.
• Put a place on sale. Resources, Create New Resource, pick Discord Role, Discord Channel or Discord Server, pick from the list the app can see and give it the title your members will read; or press Create Members Area and start from a server structure built for selling.
• Attach it to a plan and share your portal link. A member who pays connects Discord once and is in.

Running Discord beside Telegram on the same project needs the Growth Plan, as any second connector does; Discord on its own is free on every plan. The docs have the whole connector, page by page: Discord Membership App.

What Comes Next

Slack is the next connector, in development now; WhatsApp, Microsoft Teams, Discourse, Ghost, Google Drive, GitHub, Reddit, Guilded and Zoom are on the roadmap, and every one of them arrives on the same project, the same plans and the same members as the two before it. Leave your email on a connector’s marketplace page to hear the day it opens.

Go and add the app: app.subscriby.net/marketplace/discord.