
Pp Notion
- 339 installs
- 1.9k repo stars
- Updated August 4, 2026
- mvanhorn/printing-press-library
pp-notion is a Printing Press Notion CLI skill that manages pages and blocks, syncs workspaces to local SQLite, detects stale pages, and tracks changes for developers automating knowledge-base operations.
About
pp-notion is an Apache-2.0 skill from mvanhorn/printing-press-library that drives the notion-pp-cli Go binary for Notion workspace automation. It manages pages and blocks, syncs a Notion workspace to a local SQLite database, detects stale pages, and tracks changes over time. Trigger phrases include find stale notion pages, sync notion to local, use notion-pp-cli, run notion, and export notion page. Developers reach for pp-notion when agents or scripts must read and write Notion databases, publish reports into workspaces, or keep local mirrors current for diffing and search. Installation builds notion-pp-cli via Go module github.com/mvanhorn/printing-press-library/library/other/notion/cmd/notion-pp-cli.
- Notion API
- Database sync
- Page publishing
- Workspace automation
- Printing Press connector
Pp Notion by the numbers
- 339 all-time installs (skills.sh)
- +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #475 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mvanhorn/printing-press-library --skill pp-notionAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 339 |
|---|---|
| repo stars | ★ 1.9k |
| Last updated | August 4, 2026 |
| Repository | mvanhorn/printing-press-library ↗ |
How do you sync Notion workspaces to local SQLite?
Read and write Notion databases and pages through Printing Press to sync knowledge bases, publish reports, or automate workspace updates.
Who is it for?
Developers automating Notion knowledge bases who need CLI or agent-driven sync, export, and stale-content detection with local SQLite mirrors.
Skip if: Teams standardized on Confluence or Google Docs without a Notion API workflow or developers avoiding local CLI tooling.
When should I use this skill?
Notion pages must be synced locally, exported, updated, or audited for stale content through notion-pp-cli.
What you get
Local SQLite mirrors, stale-page reports, exported Notion pages, and updated workspace blocks synced from CLI runs.
- SQLite workspace mirrors
- exported Notion pages
- stale-page reports
By the numbers
- Licensed under Apache-2.0
- Builds notion-pp-cli from Go module github.com/mvanhorn/printing-press-library/library/other/notion/cmd/notion-pp-cli
Files
<!-- GENERATED FILE — DO NOT EDIT. This file is a verbatim mirror of library/productivity/notion/SKILL.md, regenerated post-merge by tools/generate-skills/. Hand-edits here are silently overwritten on the next regen. Edit the library/ source instead. See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
Notion — Printing Press CLI
Prerequisites: Install the CLI
This skill drives the notion-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:
npx -y @mvanhorn/printing-press-library install notion --cli-only2. Verify: notion-pp-cli --version 3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.
If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.4 or newer):
go install github.com/mvanhorn/printing-press-library/library/productivity/notion/cmd/notion-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
When to Use This CLI
Use notion-pp-cli when you need to manage Notion pages and blocks from the terminal, detect stale pages, or track what changed since a given time. Run sync once to populate the local store, then stale and changed work offline. Not a substitute for the Notion web UI for day-to-day editing.
Unique Capabilities
These capabilities aren't available in any other tool for this API.
Agent-native plumbing
- `changed` — Show everything in the workspace added, edited, or deleted since your last sync or a given timestamp.
_Use at the start of an agent session to orient on what has changed before taking action._
notion-pp-cli changed --since 2h --jsonLocal state that compounds
- `stale` — List pages and records not edited in N days, filterable by database, parent, or tag.
_Use to identify dead pages before workspace cleanup or to flag deliverables overdue for review._
notion-pp-cli stale --days 30 --db ProjectDB --agentCommand Reference
blocks — Block endpoints
notion-pp-cli blocks delete— Delete a blocknotion-pp-cli blocks query-meeting-notes— Query meeting notesnotion-pp-cli blocks get— Get a block by IDnotion-pp-cli blocks update— Update a blocknotion-pp-cli blocks children list— List children of a block or pagenotion-pp-cli blocks children append— Append blocks to a page or block
comments — Comment endpoints
notion-pp-cli comments create-a— Create a commentnotion-pp-cli comments delete-a— Delete a commentnotion-pp-cli comments list— List commentsnotion-pp-cli comments retrieve— Retrieve a commentnotion-pp-cli comments update-a— Update a comment
custom-emojis — Custom emoji endpoints
notion-pp-cli custom-emojis— List custom emojis
data-sources — Data source endpoints
notion-pp-cli data-sources create-a-database— Create a data sourcenotion-pp-cli data-sources retrieve-a— Retrieve a data sourcenotion-pp-cli data-sources update-a— Update a data source
databases — Database endpoints
notion-pp-cli databases query <database_id>— Query records in a database with optional filter/sortnotion-pp-cli databases create— Create a databasenotion-pp-cli databases retrieve— Retrieve a databasenotion-pp-cli databases update— Update a database
file-uploads — File upload endpoints
notion-pp-cli file-uploads create-file— Create a file uploadnotion-pp-cli file-uploads list— List file uploadsnotion-pp-cli file-uploads retrieve— Retrieve a file upload
notion-search — Manage notion search
notion-pp-cli notion-search— Search by title
oauth — OAuth endpoints (basic authentication)
notion-pp-cli oauth create-a-token— Exchange an authorization code for an access and refresh tokennotion-pp-cli oauth introspect-token— Introspect a tokennotion-pp-cli oauth revoke-token— Revoke a token
pages — Page endpoints
notion-pp-cli pages update— Update a pagenotion-pp-cli pages create— Create a pagenotion-pp-cli pages get— Get a page by IDnotion-pp-cli pages move— Move a pagenotion-pp-cli pages markdown export— Export a page as markdown
users — User endpoints
notion-pp-cli users get— List all usersnotion-pp-cli users get-self— Retrieve your token's bot usernotion-pp-cli users get-userid— Retrieve a user
views — View endpoints
notion-pp-cli views create— Create a viewnotion-pp-cli views delete— Delete a viewnotion-pp-cli views list— List viewsnotion-pp-cli views retrieve-a— Retrieve a viewnotion-pp-cli views update-a— Update a view
sync pages — Sync all pages and databases to local SQLite
notion-pp-cli sync pages— Sync all pages and databases via search API (run before stale/changed)notion-pp-cli sync pages --full— Full resync from scratchnotion-pp-cli sync pages --type database— Sync databases only
Finding the right command
When you know what you want to do but not which command does it, ask the CLI directly:
notion-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
Recipes
Morning triage: what changed overnight
notion-pp-cli changed --since 8h --jsonShow everything edited in the last 8 hours — use at session start to orient before taking action.
Find stale pages before cleanup
notion-pp-cli stale --days 30 --json --select id,title,days_since_edit,last_edited_timePages untouched for 30+ days, sorted oldest-first. The Notion UI has no equivalent filter across multiple workspaces.
Export a page as markdown
notion-pp-cli pages markdown export <page-id>Fetches the page content as markdown via the native Notion markdown endpoint — no conversion needed.
Read block children of a page
notion-pp-cli blocks children list <page-id> --json --select id,typeList all top-level blocks on a page with their types and IDs.
Auth Setup
Requires a Notion Internal Integration token. Create one at notion.so/my-integrations, share your top-level pages with it, then set NOTION_BEARER_AUTH (or NOTION_TOKEN) in your environment.
First-run setup:
notion-pp-cli doctor # verify auth
notion-pp-cli sync pages # sync all pages + databases (~15k pages, takes 2-3 min)
notion-pp-cli stale --days 30 # now works
notion-pp-cli changed --since 24hRun notion-pp-cli doctor to verify setup.
Agent Mode
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
- Pipeable — JSON on stdout, errors on stderr
- Filterable —
--selectkeeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
notion-pp-cli comments list --block-id 550e8400-e29b-41d4-a716-446655440000 --agent --select id,name,status- Previewable —
--dry-runshows the request without sending - Offline-friendly — sync/search commands can use the local SQLite store when available
- Non-interactive — never prompts, every input is a flag
- Explicit retries — use
--idempotentonly when an already-existing create should count as success, and--ignore-missingonly when a missing delete target should count as success
Response envelope
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.
Agent Feedback
When you (or the agent) notice something off about this CLI, record it:
notion-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
notion-pp-cli feedback --stdin < notes.txt
notion-pp-cli feedback list --json --limit 10Entries are stored locally at ~/.notion-pp-cli/feedback.jsonl. They are never POSTed unless NOTION_FEEDBACK_ENDPOINT is set AND either --send is passed or NOTION_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Output Delivery
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
Named Profiles
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
notion-pp-cli profile save briefing --json
notion-pp-cli --profile briefing comments list --block-id 550e8400-e29b-41d4-a716-446655440000
notion-pp-cli profile list --json
notion-pp-cli profile show briefing
notion-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 4 | Authentication required |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Argument Parsing
Parse $ARGUMENTS:
1. Empty, `help`, or `--help` → show notion-pp-cli --help output 2. Starts with `install` → ends with mcp → MCP installation; otherwise → see Prerequisites above 3. Anything else → Direct Use (execute as CLI command with --agent)
MCP Server Installation
1. Install the MCP server:
go install github.com/mvanhorn/printing-press-library/library/productivity/notion/cmd/notion-pp-mcp@latest2. Register with Claude Code:
claude mcp add notion-pp-mcp -- notion-pp-mcp3. Verify: claude mcp list
Direct Use
1. Check if installed: which notion-pp-cli If not found, offer to install (see Prerequisites at the top of this skill). 2. Match the user query to the best command from the Unique Capabilities and Command Reference above. 3. Execute with the --agent flag:
notion-pp-cli <command> [subcommand] [args] --agent4. If ambiguous, drill into subcommand help: notion-pp-cli <command> --help.
Related skills
FAQ
What CLI does pp-notion use?
pp-notion uses the notion-pp-cli Go binary from github.com/mvanhorn/printing-press-library. Agents invoke it to manage Notion pages, sync workspaces into SQLite, detect stale pages, and export content.
Can pp-notion keep a local copy of Notion data?
pp-notion syncs Notion workspaces to a local SQLite database so developers can diff changes, search offline mirrors, and audit stale pages without manual exports from the Notion UI.