Clipwise has no account, so instead of signing in you hand it a key that Notion gives you. That key decides exactly which databases it may write to — and you can take it away again at any time. Here's every step, including the two places people usually get stuck.
Clipwise runs on Chrome and on browsers built on it: Edge, Brave, Arc and Opera. Install it from the Chrome Web Store, and a setup guide opens by itself in a new tab.
An integration is Notion's way of letting a tool write into your workspace without a middleman. Making one is free and takes about thirty seconds.
notion.so/my-integrations and click New integration.Clipwise works fine. Nobody else sees this name.ntn_. Older integrations start with secret_ and those still work.
Open the setup guide that appeared after installing, or click the Clipwise icon and go to its settings. Paste the secret in the field and save.
That secret is stored in your own browser, in chrome.storage.local. It is sent to one place only: Notion's own API. There is no Clipwise server it could travel through, because there isn't one.
notion.so/my-integrations, click your integration and reveal it there. If you'd rather start fresh, make a new integration and paste the new secret over the old one.
This is the step almost everyone misses. Creating the integration doesn't give it access to anything yet — you decide per database. Until you do this, Clipwise's database list stays empty, which looks like a bug but isn't.
Open any article and click the Clipwise icon. Your database is in the list, the fields that the page tells us about are already filled in, and you pick a status or tags yourself. Click Save to Notion and you get a link straight to the new page.
Ctrl+Shift+S (Cmd+Shift+S on a Mac). It saves to your last database without opening anything.chrome://extensions/shortcuts and set whatever you like. Useful if another extension already claimed that combination.
Nine times out of ten the database isn't connected to the integration yet — go back to step 4. Notion only shows a tool what you explicitly hand it.
Already done that? Two more things to check: it must be a real database rather than a plain page, and it must live in the same workspace you selected when creating the integration. Switching workspaces means making a second integration for that one.
Usually a copying slip: a missing character, or a space at the end. Copy the secret again from notion.so/my-integrations and paste it fresh.
If it still refuses, the integration may have been deleted or its secret regenerated in Notion. Make a new integration, paste the new secret and connect your database to it again.
Some pages only load their article once you scroll, and some are built entirely out of images, which leaves nothing to save. Scroll through the article once before clipping and try again — that fixes most cases.
Still wrong? Send me the address of that page. Genuinely: most of the improvements in version 0.2 started as exactly that kind of message.
Chrome hands each shortcut to one extension only, so another one may have claimed it first. Open chrome://extensions/shortcuts to see who has it and set a different combination for Clipwise.
The shortcut also needs a database to have been used at least once, since it saves to your last one.
It's hiding in the puzzle-piece menu at the top right of your browser. Open that menu and click the pin next to Clipwise to keep it on the toolbar.
In Notion, open the database, choose ··· › Connections and remove the integration. Or delete the whole integration at notion.so/my-integrations, which cuts off every database at once.
Uninstalling the extension removes the secret from your browser along with it. Nothing about you is stored anywhere else, because there's nowhere else.
One person reads all of these — me. Questions like yours are how this guide got written, so don't worry about bothering anyone.
Email is roansp27@gmail.com and reaches me directly. The Support tab needs no account beyond the Google one you already use for Chrome, and GitHub is handiest if you want to paste a link to the page that clipped wrong.