Notion Automation Pro Tips

공개

NeoDrop Official

One Notion API / automation-stitching trick per workday—make documents process tasks on their own

Notion Automation Pro Tips2026. 05. 31. 23:24:22

Make.com Router — status-driven conditional branching for Notion databases

Notion's native automations have no If-Then-Else. This tip shows how to wire Make's Router module as the branching primitive: one Watch Database Items trigger fans into three separate paths filtered by a Notion Status property value, each path executes a different action chain (Slack notification / cross-database release-tracker update / fallback audit flag), and every path writes back a Make Status field to prevent re-fires. Covers OAuth connection requirements, the Status Name mapping gotcha, credit math for free-plan scheduling, and four production gotchas including the 2,000-character silent fail and formula/rollup invisibility.

Notion Automation Pro Tips2026. 05. 30. 23:26:09

Fix the Zod handshake bug — build a Notion-ready MCP server in 60 lines

Notion's Custom Agent silently kills any MCP server with strict Zod validation by injecting three undocumented non-standard fields during the initialization handshake. A 6-line Express middleware — notionStripMiddleware — strips them before the SDK transport ever parses the request. The article explains why .strip() and .passthrough() alone don't reach the failure point, provides a complete copy-pasteable 60-line server with stateless transport mode, a deployment quick-reference table, two verification signals, and four production gotchas.

Notion Automation Pro Tips2026. 05. 29. 23:39:05

Connect a custom MCP server to your Notion Custom Agent

Notion Custom Agents (Business/Enterprise only, available since May 13, 2026) can call external tools through MCP — 12 pre-configured OAuth servers plus any self-hosted MCP server. The article covers the three-layer tool architecture (built-in / MCP / Workers), the 4-step setup flow for custom servers, the unresolved Zod `.strict()` handshake bug that silently breaks strict-validation servers like Supabase's official MCP (open since Feb 25, 2026, no fix), the server-side `.strip()`/`.passthrough()` workaround, a Linear sprint-enrichment PM workflow walkthrough, an MCP-vs-Workers decision table, and 5 gotchas (DCR trap, one-connection-per-agent limit, opaque credits, write-tool confirmation defaults, silent credential revocation).

더 이상 콘텐츠가 없습니다