10. Ship it
Take the Agora connector from green tests to a reviewed connector — the listing as creators will read it, the review checklist item by item, versioning, and what happens after Subscriby installs it.
Read the listing as a creator
Open connector.json and read the listing block as someone who has never seen the connector:
- The tagline says what it does in one line: "Sell access to private boards on your Agora forum, joined and left automatically." Seventy-nine characters.
- The overview says what a creator does (connect with a key), what a member experiences (buys on the portal, is added to boards, gets private messages) and what the connector watches (health of the forum, the boards and the bot). It does not repeat the capability list; the marketplace generates that from the manifest.
- The links: our documentation for creators, our support address, and Agora's privacy and terms.
- The marketing words read mid-sentence: "for forum communities", "your board", "a forum bot", "your forum account".
The checklist, item by item
manifest.file_is_the_source and migrations.own_tables_only: chapter 9's test, run with the package path.grep -r "App\\\\" src/ finds nothing; every core read and write went through Subscriby\Connector\Core\*.CredentialBag (the secret arrived there through the summary's meta); agora_forums holds neither; no Log:: call formats a bag or a header.lang/*.json files.already_member is a grant, a 404 is a revoke, pacing is one request a second against Agora's sixty a minute, and rate_limited classifies to RateLimited with Agora's Retry-After.Version it
The ports the manifest declares work on the platform end to end, so version moves from 0.1.0 to 1.0.0, the CHANGELOG.md gets its first entry, and the repository gets a tag. added_at stays 2026-10-01, the day of first publication.
Submit
Send the repository URL, the tag and the kit's summary line to [email protected], or through Request a connector on the marketplace. Subscriby reads the package against the checklist, runs the kit in its own suite, and installs it. The connector then appears in the marketplace's Under Development lane until Subscriby switches agora on, at which point creators can install it and its card reads Available Now with the Community badge and, for sixty days, New.
After launch
- A new Agora API version is an additive change: new fields, a new event type, a manifest
versionbump. - Agora members want to ask questions: a forum member's private message to the bot is filed into the Subscriby inbox through
Core\Support::ingest()and answered from the dashboard, the connector bindsSupportRelayto carry the answers back, the manifest gainssupport_relay, and itsversionbumps again. - Agora adds a rate limit header you did not map: one row in the classifier's table and a snapshot update, with a commit message that says so.
- Something breaks on the forum's side: ask Subscriby to pause the connector; inbound answers 503 and sends queue until you say resume.
What you built
A package with eleven ports, two tables of its own that hold no secret, one web route and one inbound route, ten language files, a manifest that says exactly what it can do, and a test suite that fails before review would. Every other connector is the same shape; only the platform's answers differ.
How is this guide?