Integrations · Notion
Your customers in Notion, with MRR and risk kept current.
Teams that run customer success in Notion keep a customer database by hand, and it drifts from billing within a week. Keep writes that database for you: one row per paying customer, updated when the revenue, the risk, or the renewal changes.
What a row carries
You choose the fields: customer name, email, a link back to the account in Keep, MRR, currency, status, risk level and its reason, renewal date, last activity, usage in the last 30 days, the latest NPS answer, and the team member who owns the account. Each goes to a property of a compatible type — a number to a number, a date to a date — and Keep refuses the rest instead of converting it.
Your own columns, views, and filters stay yours. Keep writes only to the properties you mapped, and never creates or changes properties in your database.
How it stays in sync
Keep remembers which page belongs to which customer, so a sync never creates a second one. A page is written only when what it would receive changed; an unchanged customer costs no request at all.
A customer who stops paying is updated to canceled with MRR 0, and the page stays. Requests follow Notion's rate limit; a large first sync that runs out of time continues where it stopped.
What Keep reads and writes
| — | Keep and Notion |
|---|---|
| Connection | OAuth. You pick which pages and databases Keep may access; it sees nothing else. |
| Scope | One Notion connection per Keep workspace, and one database per connection. |
| Reads | The databases you shared, and the properties of the one you chose. |
| Writes | Pages in that database, in the properties you mapped. Never deletes a page, never changes the schema. |
| Direction | Keep to Notion only. Changes made in Notion do not come back. |
| Stores | The access token, encrypted with AES-256-GCM, and which page holds each customer. |
How to connect
Create the database
In Notion, a database with the columns you want: MRR as a number, status and risk as selects, renewal as a date.
Authorize Keep
Connect Notion from Integrations and share that database. Only a workspace owner or admin can connect.
Map and sync
Pick the database, confirm the suggested mapping, and start the sync.
Questions
- What if someone edits a row in Notion?
- Keep is the source of truth. An edit to a mapped property is overwritten the next time that customer changes in Keep. Columns Keep does not map are never touched.
- What happens to the pages if I disconnect?
- They stay in Notion as they are, and nothing changes in Keep. Reconnect and pick the same database, and Keep updates the same pages again.
- Can two Keep workspaces share one Notion?
- Each Keep workspace has its own connection. One workspace can never see or use another's, even when the same person belongs to both.
- Which plan includes Notion?
- Every plan. All Keep features, including every integration, are in all plans; the difference between plans is monitored MRR.
Other integrations
Stop maintaining the customer list by hand.
Connect your billing and Notion, and the database fills itself.