Connectors Marketplace

The Connectors Marketplace at www.subscriby.net/connectors lists every connector Subscriby knows about: the platforms it gates access on, sends messages through and takes payments from today, and the ones on the roadmap. The dashboard's per-project Connectors page, the GET /connectors endpoint and the MCP resource subscriby://connectors/catalog render the same catalogue, so what the site promises is what a creator can install.

Lanes

Cards are grouped by status:

Badges

• Official (the check mark by the name) — built and maintained by Subscriby.
• Community — built by a third party against the connector SDK and reviewed by Subscriby.
• New — added to the catalogue within the last 60 days.
• Trending — the most installed connector over the last 30 days.

Sorting and filtering

Cards come most popular first: the connector running on the most projects tops its lane, and the hero shows the most popular icons with a count of what is available and what is on the roadmap. Sort by switches to Newest (when the listing was added) or Name. The chips narrow the list to Official, Community, Available Now or Coming Soon, and the category row to Messaging, Community, Payments or Productivity. Every choice is a plain link (?sort=, ?filter=, ?category=), so a filtered view can be shared; the line under the toolbar says how many of the connectors are showing. Cards that already run on projects say on how many.

A connector's page

Each card opens a page built from the connector's manifest, so nothing on it is typed by hand:

• Overview — the connector's own description.
• What it can do, in plain words — what you can sell access to (each named after the platform, such as "Telegram Channels", with the name members see and a four-row checklist of the plan shapes that kind of place can be sold under: one-time payments, recurring subscriptions, time-limited passes and pass series, a dash marking the ones it cannot), what it does for you (automatic access, messages to members, a support inbox, backups and so on, each in one sentence), how many everyday tasks you can run from inside the platform, and what you need to have ready to connect it (a token, a sign-in, or nothing when Subscriby runs the connection for you).
• Made by, Category, Sign-in required, Version, Added, Status — the manifest's listing block.
• More info — documentation, support, privacy policy, terms and homepage links, when the connector publishes them.
• Pricing — official connectors are free; a second connector on the same project needs the Growth plan (the multi_connector capability).

Get Started on an available connector signs you in (or registers you) and opens that connector inside the app, where Connect to a project installs it on the project you pick.

Notify me

A Coming Soon card (and an Under Development one, until it is enabled) shows a Notify me form instead of the capability section. Leave an email and Subscriby writes to it the day the connector launches. The address goes to one marketing contact book with the connector's key attached and nothing else is sent to it. Asking to be notified about a connector that is already available redirects you to its page with a note to install it instead. The form is rate-limited to six submissions a minute per visitor.

Build a connector

Every connector on the page is a Composer package built on the Subscriby connector SDK: it declares its manifest in a connector.json file (key, resource kinds, capabilities, messaging limits, management commands, the listing block with the words the public site borrows for that platform, and its install fields), binds the ports it implements, and passes the SDK's conformance kit before Subscriby reviews and installs it. Building a connector explains the manifest, the ports, the data rules and the kit. If you would rather we built it, use Request a connector on the directory to tell us which platform your community lives on.

Where else the catalogue appears

• Dashboard — Connectors in the sidebar opens the in-app marketplace: the same cards with search, the same chips, category and sort, a count of how many of your projects each connector runs on, and Connect to a project on the available cards, which opens a pending installation on the project you pick and takes you to that project's Connectors page to enter the credentials. Opening a card shows Overview (the public page's content) and Configuration (reachable directly with ?tab=configuration on the connector's address, which the count badge on a card links to): every installation of that connector on your projects with its state, the fields it asked for on connect, its settings, and its capabilities grouped as Messaging, Access, Recovery and Payments, each with a line on what it does and a switch where the project may turn it off on that installation (messages, broadcasts, the support inbox, built-in payments and the recovery facets; access control and the rest are Always On, and so is account recovery on a project, because that switch belongs to the connector as a whole rather than to one project), plus a Manage on project button. Switching Built-in payments off hides the connector's currency from the payment-method picker and from plan pricing, refuses a new method for it and stops offering it at checkout; sales already made are untouched. A switched-off capability is honoured everywhere at once: a broadcast is refused before it is queued, a health check is skipped, a reply is not relayed. A project's own Connectors page and its Browse Marketplace view list the same cards with Install. See Connectors.
• API — GET /connectors returns the listings with status, badges, category, links and the declarative install and settings fields.
• MCP — the list_connectors and get_connector tools and the subscriby://connectors/catalog resource.
• Zapier and n8n — the connector dropdowns read the same endpoint.