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).

Notion Automation Pro Tips2026. 05. 28. 23:25:17

Enrich your Notion databases with cross-workspace context using Custom Agent Autofill

Custom Agent Autofill is the credits-powered upgrade to Basic Autofill: it can pull context from other databases in your workspace and from the web before writing properties — Basic Autofill can't. Covers the two-mode difference, the $10/1,000 credits cost model with PM math (200 runs/month = $10–$60), a step-by-step competitor-tracking enrichment workflow, multi-property fill pattern, agent chaining via property-edited triggers, and 6 gotchas including the global web-toggle trap, independent permission scope risks, and workspace-shared credit exhaustion.

Notion Automation Pro Tips2026. 05. 27. 23:25:16

Query tasks across linked Notion databases with relation and rollup filters

The Notion API's `relation.contains` filter only accepts a page UUID, not a project name — so querying tasks by "linked to a P0 project" requires a two-step UUID bridge: first query the Projects database for P0 pages, collect their IDs, then feed those IDs into a compound filter on the Tasks database. Covers the three mutually exclusive rollup filter shapes (any/every/none, date, number), shows how to compose relation + rollup filters in one compound query, and delivers a complete `p0BlockerScan` Worker tool with pagination, error handling, and 6 gotchas.

Notion Automation Pro Tips2026. 05. 26. 23:27:44

Build a sprint risk dashboard with Notion API compound filters

The Notion API's compound filter nests `and`/`or` conditions up to two levels deep, mirroring the Notion UI filter panel exactly. This tip walks through a complete `SPRINT_RISK_FILTER` (P0 + In Progress|Blocked + `"me"` + due within a week), wraps it in a Notion Worker as a `sprintRiskDashboard` tool using `iteratePaginatedAPI` for automatic pagination, provides three drop-in PM filter variants, and documents four gotchas: `"me"` returning nothing for internal integrations, UTC-only date resolution, the `timestamp` filter's prohibition on the `property` field, and the 10,000-row pagination ceiling.

Notion Automation Pro Tips2026. 05. 25. 23:18:58

Auto-triage feature requests with Notion AI Autofill + Automations

Notion AI Autofill (March 2026) auto-classifies new Feature Request rows into Category and Priority Select properties the moment a page is created — then a database automation routes P0s to Slack and Bugs to a separate tracker, with zero manual triage. Covers the two-layer Autofill model (Basic vs. Custom Agent), the 'on edit' latency gotcha, and how to chain Property edited automations downstream.

Notion Automation Pro Tips2026. 05. 24. 23:24:12

Route Notion rows to Jira, Linear, or Slack with n8n's Switch node

A four-node n8n chain — Notion Trigger → Set → Switch → action nodes — routes new or updated Notion database rows to Jira, Linear, or Slack based on a property value. The key non-obvious step is a Set node that flattens Notion's nested JSON before the Switch conditions fire. Built from templates #4386 and #14120; includes credential setup for all three tools, an optional closed-loop write-back to Notion, and an honest rundown of the Notion Trigger's active beta bugs.

Notion Automation Pro Tips2026. 05. 23. 23:24:56

3 patterns every production Notion Worker needs

Three built-in SDK and CLI patterns that close the most common production failure modes for Notion Workers: `worker.pacer()` smooths outbound API call rate to prevent 429s; HMAC-SHA256 signature verification secures webhook endpoints from spoofed payloads (with Notion's 5-failure auto-lock explained); and `--local`/`--preview` flags on `ntn workers sync trigger` let you iterate sync logic against real source data without writing a single row to your live Notion database.

Notion Automation Pro Tips2026. 05. 23. 00:19:38

Notion External Agents API: what it is, why you can't use it yet, and the MCP bridge that works today

Notion's External Agents API (Alpha/waitlist, May 2026) lets Claude Code, Cursor, and Codex join your workspace as OAuth participants — but the waitlist blocks you today. This tip covers what the API actually is, how it differs from Workers and Custom Agents, and walks through the working MCP bridge workaround in 5 steps (~45 min).

Notion Automation Pro Tips2026. 05. 21. 23:47:48

Register multiple tools in one Notion Worker so your Custom Agent can do more than one thing

A Notion Custom Agent wired to a single `worker.tool()` hits a ceiling fast — real PM workflows need both lookup and write operations in the same conversation. This tip shows how to register two `worker.tool()` calls in one `src/index.ts`: a read-only `lookupRoadmapItem` (auto-executes via `readOnlyHint: true`) and a write `flagAsBlocked` (gates on confirmation). The Custom Agent routes between them automatically using LLM function-calling. One `ntn workers deploy` covers both.

Notion Automation Pro Tips2026. 05. 20. 23:44:29

Give your Notion Custom Agent a real data tool with `worker.tool()`

Custom Agents can't see your Notion databases by default — they can only reason over text already in the conversation. `worker.tool()` registers a TypeScript function in Notion's hosted runtime that the agent can call on-demand with typed arguments. This tip walks through building a `querySprintDatabase` tool: scaffold, schema with the `j` builder, `readOnlyHint` for auto-execution, local dry-run, deploy in 30 seconds, and connect to a Custom Agent via the "+ Add connection" UI. Free through August 11, 2026; Business/Enterprise plan required.