Featurebase Integration
Keep your Featurebase help center current without writing every article by hand. Shipstar reads a period of commits, drafts a set of user-facing help articles, and puts them in front of you for review. Approve the set and the articles are created in your Featurebase help center — in the collection you picked, live or as Featurebase drafts.
Article sets drafted from your commits
Each run reads the commit window you choose and writes a set of help articles — one topic per article, with what the feature does, how to use it, and step-by-step instructions in a friendly, customer-facing tone. Internal refactors, CI, and dependency bumps are left out.
Schedule a recurring export
Exports now support JSON
Send exports to Google Drive
Why an export shows fewer rows
Review first, then create on approve
Nothing reaches your help center until you approve it. Edit titles and bodies, drop articles you don't want, and approve the set; Shipstar then creates the remaining articles in Featurebase. If a delivery fails part-way, retrying creates only the articles that are still missing — never duplicates.
Each article is recorded as it's created. A retry only creates the ones still missing.
Your collection, your publish state
Pick a default collection when you connect, and let any schedule override it with its own. Choose whether approved articles go live immediately or land as Featurebase drafts for a second review inside Featurebase. Scheduled runs can keep a collection filled week after week.
Connected with an API key
Featurebase uses organization-level API keys rather than OAuth. Paste a key in Destinations → Featurebase; Shipstar checks it against your help center before saving it, stores it encrypted, and shows a reconnect prompt if Featurebase ever rejects it.
The key is checked against your help center before it's saved. If Featurebase ever rejects it, the dashboard asks you to reconnect.
Why use Featurebase with Shipstar
- Help articles drafted from shipped code, reviewed before anything is created
- Articles created in the Featurebase collection you choose
- Live or Featurebase-draft publishing, per account
- Encrypted API-key connection with reconnect prompts
Frequently asked questions
Shipstar reads the commits in a period from your tracked GitHub repositories and drafts a set of help center articles. You review the set in the Shipstar dashboard (or over MCP), edit or remove articles, and approve it. On approve, Shipstar creates the articles in your Featurebase help center through the Featurebase API, in the collection the schedule or your destination default names.
No. Create an organization-level API key in Featurebase and paste it into Shipstar under Destinations → Featurebase. Shipstar validates the key against your help center before saving it, and stores it encrypted.
Yes. Set a default collection when you connect Featurebase, and pick a different collection on any schedule from its "Deliver to" section. All articles in one run land in the same collection.
That's up to you. The destination's "Publish as" setting creates articles live in your help center, or as Featurebase drafts so your support team can do a second review inside Featurebase before they go public.
No. Shipstar only creates new articles; it never edits or deletes content already in your help center. Updating existing articles from new commits is not part of the integration today.
The delivery fails, the set stays in review with the reason shown in the dashboard, and the person who scheduled it gets one email. Paste a new key under Destinations → Featurebase and retry from the review sheet; articles already created in the earlier attempt are kept and not recreated.
Works great with
Explore related pages
Ship it. Share it. Celebrate it.
Release notes on autopilot.
Free to start. Connect your repo in 30 seconds.
No credit card required · Setup in 30 seconds