Docs your customers actually find.
A fast help center with semantic search, a block-based editor, and your brand on your own domain. It is also what your AI agent learns from, so you write once and answer everywhere.
Fix “Why declined events still show as busy” once, and every surface answers with the new version.
Customers don’t search with your words.
They type “got charged for a calendar we removed” when your article is called “Delete a connection and its data.” Semantic search matches on meaning, so typos, synonyms and vague questions still land on the right doc.
Writing docs shouldn’t feel like work.
A block-based editor that gets out of the way. Type / for callouts, code blocks, images and step lists, then preview exactly what customers will see before you publish.
Reconnect an expired Google connection
Google can revoke a connection when a user changes their password or removes your app. The connection then moves to needs_reauth. Once it’s reconnected, free/busy and webhooks resume without any change to your code.
You’ll need your API key and the connection’s ID to finish. Existing events and webhooks are kept; calendar reads stay paused until the user approves access again.
Send the user back through connect
- In the Connection health dashboard, find the connection marked Needs reauth and copy its connection_id.
- Send your user back to the hosted connect page with that connection_id in the link.
- Once they approve Google’s consent screen, call GET /v1/connections to confirm it is active.
Your brand, your domain. Not ours.
Put your help center on help.yoursaas.com with automatic SSL, your logo and your colors, and on Enterprise, drop the “powered by” badge entirely. Customers should never feel like they left your product.
Write once. It feeds everything.
Your knowledge base isn’t a silo. Every other part of SapanBase runs on it.
Docs that keep up.
Import your help center in minutes and see it on your own domain. SapanBase is in private beta.
Private beta · Free for 14 days · New spots weekly