notion-workers: Instructions file for Codex

Notion Workers monorepo

This repo holds all of my Notion Workers. Each top-level directory (e.g. firecrawl/) is one deployed worker: a self-contained npm project with its own package.json, lockfile, src/index.ts, and workers.json.

For the full Notion Workers platform guide — capability API (tools, syncs, automations, webhooks, OAuth), sync patterns, testing, and debugging — read .agents/INSTRUCTIONS.md. Skills for sync work live in .agents/skills/, and .examples/ has one compilable reference example per capability type — when it and INSTRUCTIONS.md disagree on API shape, trust .examples/.

Conventions

• All ntn and npm commands run from inside a worker's directory, not the repo root. There is no root package.json and no shared dependencies.
• Workers are named after the upstream service they wrap (firecrawl, openlibrary), no -worker suffix. Directory name, package.json name, and deployed worker name (deploy --name) all match.
• workers.json is committed (it holds the workspace/worker IDs that link a directory to its deployed worker — IDs, not secrets). This deviates from the official scaffold's .gitignore. Never gitignore it here, and never delete it for an existing worker: without it, ntn workers deploy creates a new worker instead of updating.
• Secrets are never committed. Local dev reads .env (gitignored); deployed workers read env vars set via ntn workers env set / ntn workers env push. If you add a new secret, push it before deploying code that needs it.
• Each worker has a short README.md: what it does, its capabilities, and required env vars. Keep it current when you change capabilities.
• A worker may have its own AGENTS.md (with a CLAUDE.md symlink, like the root). Worker-specific rules there OVERRIDE these norms — read it before touching that worker. Example: twitter/ forbids the standard local-exec verify loop because of its token handling.
• Tool schemas use the j builder (import { j } from "@notionhq/workers/schema-builder"). SDK ≥ 0.4.0 no longer accepts raw JSON Schema objects in tool() — some examples in .agents/INSTRUCTIONS.md predate this; .examples/tool-example.ts shows the current API.
• Every tool input property is required. The SDK rejects schemas whose properties aren't all in required; .nullable() means present-but-null, not omittable. Agent callers omit fields they don't need and fail validation, so keep tool inputs to fields the caller will always send.
• No "type": "module" in worker package.json files. ntn workers exec --local (CLI 0.16.0) fails on ESM workers with Cannot read properties of undefined (reading 'run'). CJS mode works locally and deploys identically (requires typescript ≥ 5.8 to type-check importing the ESM SDK). new-worker.sh strips this from new scaffolds automatically.