As a regular user of both Google Keep and Obsidian, I set out to make it easier to exchange data between both apps.
KeepSidian syncs notes between Google Keep and Obsidian, on demand or automatically on a schedule. The current plugin experience centers manual sync around the Sync Center, where you can review a download, upload, or two-way plan before anything changes in your vault or in Google Keep.
Please share your feedback in the issues section on GitHub.
The connection to Google Keep is established through a flask server based on Keep-It-Markdown, which handles the heavy lifting. This is particularly useful for users who cannot run Python scripts on their computers.
When you start a sync, you will provide your Google Keep email and a token generated during installation. These credentials are stored on your computer, sent when you sync, and then discarded. KeepSidian stores sync tokens in Obsidian secret storage when available, and does not log or store your credentials or notes on the server.
KeepSidian now centers manual sync around one primary action: Sync now.
Sync now opens the Sync Center and immediately starts building a reviewable download plan.Open sync center opens the same surface without starting a sync, so you can choose the mode first.Last successful syncAll datesCustomEvery manual sync is review-first. The setup view builds a plan, then the larger review modal shows grouped counts and the exact notes/actions before execution. While a sync is running, the status bar, notices, and review modal stay in sync so you can track progress from either place.
Each sync activitiy is recorded in a time stamped activity log file under _KeepSidianLogs/ in the target directory as
Markdown list items. This file is rotated daily.
You can enable background syncing on a 24 hour schedule by default. Project supporters can customize the interval in hours. Project supporters can also choose to run a two-way sync whenever background syncing.
When background-sync is enabled, a status bar indicator is shown in the bottom right.
KeepSidian is useful for all users. However, some advanced features that may incur additional processing, third party costs or developer time shall be released to users who choose to support KeepSidian development. Anyone can choose to support the project here: 🌎 Support KeepSidian.
v1.0.14:
v1.1.0:
v1.1.2:
Active supporters can manage billing or unsubscribe from inside Obsidian. Open
Settings > KeepSidian > Exclusive features for project supporters, then use the Stripe customer-portal link shown in
the active subscription section.
Some upcoming features that I plan to work on include:
What would you like to see next?
Please rank the upcoming features here or add your own!
- KeepSidian wishlist - Google keep features.
- Google Calendar features (coming soon): I'd love to hear what you want for this feature.
KeepSidian can be installed from the community plugin store, as well as a few other options outlined below.
After installation, go to "Settings > Community Plugins > KeepSidian" in Obsidian to configure the plugin.
In the plugin settings, you will need to provide:
/KeepSidian.{now.*} and {note.*} variables such as year, month, day, or
date.{title}.oauth2_4...
token and let KeepSidian exchange it through the server.PRIVACY NOTE: THIS TOKEN IS ONLY STORED ON YOUR COMPUTER. When supported by your Obsidian version, KeepSidian stores the token in Obsidian secret storage.
Starting with v2.0.3, KeepSidian can be used on mobile. A community member takes Google Keep notes on the go from their smartwatch, then uses KeepSidian on their phone to sync those notes into Obsidian.
KeepSidian on mobile still requires a sync token, but it does not include the token retrieval wizard. The easiest path is to retrieve the token on desktop, copy it, paste it into a temporary Google Keep note, then open that note on your phone and copy/paste the token into KeepSidian settings. Any other reliable copy/paste method between desktop and phone works too.
The plugin adds the following frontmatter to each synced note:
When a local note and its Google Keep counterpart have both been modified since the last sync, KeepSidian now attempts
to merge the differing bodies of the notes. The frontmatter of the existing note is preserved and excluded from the
merge comparison. If the merge succeeds, the note is updated in place; otherwise, the incoming version is saved as a
separate -conflict-<timestamp>.md file.
media/ directory.media/.Please share your feedback in the issues section on GitHub.