| name | notion-prod-checklist |
| description | Execute a Notion API production deployment checklist and readiness verification.
Use when deploying Notion integrations to production, preparing for launch,
verifying go-live readiness, or auditing an existing Notion integration.
Trigger with "notion production checklist", "deploy notion integration",
"notion go-live", "notion launch readiness", "notion prod audit".
|
| allowed-tools | Read, Write, Bash(grep:*), Bash(curl:*), Bash(jq:*) |
| version | 1.38.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","productivity","notion","deployment","checklist"] |
| compatibility | Designed for Claude Code |
Notion API Production Deployment Checklist
Overview
A structured 12-section checklist for deploying Notion API integrations to production, covering authentication security, capability scoping, page sharing, rate limits, pagination, error handling, versioning, retries, monitoring, graceful degradation, data validation, and OAuth token lifecycle. Each section maps to a specific failure mode seen in production Notion integrations, and every item is testable — the skill produces a verified pass/fail report, not aspirational guidance.
Prerequisites
- Node.js 18+ with
@notionhq/client v2.x installed
- Working Notion integration tested in a development workspace
- Production Notion API token (internal) or OAuth credentials (public integration)
- Target databases and pages identified by ID
- Deployment platform configured (Vercel, Railway, AWS, etc.)
Verify SDK is installed:
node -e "const { Client } = require('@notionhq/client'); console.log('SDK loaded')" 2>/dev/null \
|| echo "MISSING: npm install @notionhq/client"
Instructions
Work through the checklist in order, marking each item pass or fail. A single fail in sections 1-6 is a deployment blocker.
- Run the pre-deploy smoke test (see Examples) to confirm the token is set, auth works, and target databases are reachable. This catches the most common failure — a page that is not shared with the integration — before you go deeper.
- Grade each of the 12 sections against its checkbox items. The summary table below is the map; the full item-by-item detail, fail criteria, and code snippets live in references/checklist-sections.md.
- Pull implementation patterns (rate-limited queue, paginator, typed error handler, retry, cache fallback, property validator, OAuth exchange) from references/code-examples.md as each section requires them.
- Record a pass/fail per section and total the blocking (1-6) vs non-blocking (7-12) failures.
- Emit the readiness report (see Output) with the final verdict: ready to deploy, or blocked with the count of items to fix.
The 12 sections at a glance
