Importing from Google Keep

When to use

When a user imports Google Keep notes exported via Google Takeout (unzip it and pass the Takeout or Keep folder). You own it end to end. Read limestone-vault-conventions, working-with-collections, and importing-from-obsidian first.

Run the import (one tool call)

Call limestone_import_notebook(path, collection_name) with the folder (the one holding Keep/, or Keep/ itself). Returns the usual summary + unconverted list.

How the import works (what the tool does)

Takeout writes a .json (authoritative) + .html (ignored) per note, plus media:

Google Keep	Limestone
each note JSON	a record (title, else its first line)
textContent	the note body
listContent (checklists)	- [ ] / - [x] checkboxes
labels	real note tags
microsecond timestamps	Created / Updated date properties
attachments (images/audio)	stored beside the note, embedded as ![[filename]]

Trashed notes are skipped; archived notes are kept.

Finalizing (your job)

The importing-from-obsidian playbook applies. Keep-specific: Keep's color, pinned, and archived flags aren't mapped — add properties for any the user tracks. Resolve unconverted items (unsupported attachment types) as usual.

Evolving this skill

If the Takeout schema shifts, work out the mapping and propose an update here or to importers/google_keep.py. Keep the two in sync.