Two writes, two reads
Publish a page, add to one, pull a page in, or search your workspace into your session. Reads make no AI call, so they cost nothing, and they only ever reach what you shared with the integration.
Create a page in your database from what you selected, add a decision to the end of a running document, or pull a page and a search back into the work session your agents read.
Notion is usually where a team's own writing lives, which makes it both a destination and a source. Create page is the row that's on out of the box; the other three are a checkbox away on the same card.
Notion's permission model is the thing to understand first: an integration sees nothing until you share a database with it. Everything Khint can do is bounded by that, deliberately.
Publish a page, add to one, pull a page in, or search your workspace into your session. Reads make no AI call, so they cost nothing, and they only ever reach what you shared with the integration.
A created page is logged as a session entry once Notion confirms, so the agent you run next writes with it in hand, and your AI client reading over MCP sees it too.
Create page and Append to page are workflow steps, including as branches of a parallel step: one press can write the Notion page and post the Slack update from the same text.
Turning the card off hides the rows and stops workflows using it while the token stays for an instant reconnect. Forget credentials is the separate, deliberate clear.
Notion grants access per integration and per page, opt-in. Khint inherits that model rather than working around it, which is why an empty database picker is a Notion sharing step, not a bug.
Security and privacyNotion's own model: an internal integration, then the databases you explicitly share with it.
Go to notion.com/my-integrations, create an internal integration, and copy its secret token.
This is the step everyone misses. In Notion, open the database you want Khint to write to, click the ••• menu, then Connections, and add your integration. A database you haven't shared is invisible to it.
Paste the token and Save. It goes into your operating system's keychain.
Khint lists the databases the integration can see, which is exactly the ones you shared in step two. If the list is empty, that step is why.
Cmd+Shift+K, then Create page. Append to page, Pull page and Search can be switched on from the same card.
An integration is where work comes in and goes out. These three are what happens in between.
Because it hasn't been shared with the integration. Notion integrations see nothing by default: open the database in Notion, click the ••• menu, then Connections, and add yours. The picker lists exactly the databases you've shared, so an empty list always means that step is missing.
Notion AI works on the page you have open in Notion. Khint works on whatever you've selected in whatever app you're in, and Notion is one of the places the result can land. The two answer different questions: improving a Notion page, versus getting something that's not in Notion into it.
No, unless you switch Knowledge on for Notion, and then only into a local full-text index on your Mac that never reaches our servers. Without it, a Notion page is in Khint only for as long as the local Memory session you pulled it into.
The Notion call is free. Writing the page content from your selection is one normal agent run against your monthly credits. Pulls, searches and pickers cost nothing.
Yes. Create Notion page and Append to Notion page are both workflow steps, so a workflow can clean up your text and file it in one press. A parallel step can also write to Notion and Slack at the same time from the same running text.
Free with 300 credits a month. No credit card. macOS 13+ or Windows 10 22H2+.