okhp3-notion-row-write

Topics in the source

• okhp3-notion-row-write
• Scope
• The rule: schema-first, always
• Minimal property-type table (wave 1)
• Idempotent upsert
• Chunking and limits
• Block-limit awareness
• Output contract

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Creates and updates Notion database rows against their actual, fetched schema. Always load okhp3-notion-core first, and okhp3-notion-identity-resolution if the data source is not yet confirmed. | In scope | Out of scope | |---|---| | Single-row and small-batch create/update, property mapping, idempotent upsert | If a property is missing, this skill stops and routes to schema-migration rather than inventing a field. Volume beyond a few dozen rows routes to a future bulk-data-ops skill. Deletion is okhp3-notion-destructive-ops | 1. Resolve the target data source (never a bare databaseid - see okhp3-notion-core Step 4). 2. Fetch its schema (GET /v1/datasources/:id) before constructing any write payload. Read the exact property names, types, and - for select/status/multi-select - the exact allowed option names. 3. Map only fields the fetched schema actually supports. If the data the user wants to write includes a field the schema does not have, stop and tell the user this requires a schema change - do not silently drop the field, and do not guess a property name that "should" exist. Route to a schema-migration skill (wave 2) for th

This is an excerpt. Refer to the complete source and its current requirements.