notion-api-automation
Notion API Automation
Why this exists
Notion API work is easy to get “mostly right” and still fail in production due to:
- Versioning:
Notion-Versionis required and features differ by version. - Database vs data source split: modern integrations must work with
data_source_idfor “rows”. - Properties vs content: page properties are not the same as page block content.
- Pagination + throttling: most listing endpoints are paginated; rate limits are tight.
- Validation schema: property values must match the data source schema exactly.
This skill provides reliable, repeatable workflows and drop-in request patterns.
Quick start
More from tristanmanchester/agent-skills
designing-beautiful-websites
>-
1.2Kreddit-readonly
>-
361styling-nativewind-v4-expo
>-
227animating-react-native-expo
>-
210track17
Track parcels via the 17TRACK API (local SQLite DB, polling + optional webhook ingestion)
73nextjs-framer-motion-animations
Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.
71