Notion Just Made Zapier Optional. Here's the Build.

Polling Salesforce every 15 minutes now costs 86 cents a month. Your middleware bill has a problem.

One pattern I keep seeing with operators who are actually pulling ahead in 2026: they have fewer software subscriptions, not more.

Over the past three years, I’ve watched categories of tools get compressed into platforms operators already pay for. Design tools got absorbed into Canva and then into every AI image generator on the market. Copywriting tools got pulled into any halfway decent chat window. Transcription tools showed up as built-in features across video platforms, meeting tools, and phones. Each category went from “you need a subscription for this” to “it comes with the thing you already have.”

Automation middleware has been the holdout. If you run Notion as your central workspace and you want it to talk to anything else (your CRM, your support platform, your payment processor), you’ve needed Zapier or Make or n8n sitting in the middle.

Notion just changed that equation.

On May 13, Notion shipped its Developer Platform: Workers, database sync, external agent support, and a CLI. It’s the most significant thing Notion has built in years, and a lot of the operators I talk to haven’t looked at it yet. Here’s what actually shipped and what to do with it.

What Notion Workers Actually Are

Workers are small pieces of code that run on Notion’s own servers. They can connect to any external API, trigger on events in your workspace, sync data on a schedule, and execute logic that Notion’s native automations have never been able to handle.

Think of the lightning bolt automations you already use in Notion databases: when a status changes, do this. Workers do that, with no ceiling. They can call Salesforce. They can pull from Zendesk. They can hit Stripe. They can check for duplicates across thousands of records. Any API that exists is now reachable from inside your workspace.

Three ways a Worker gets triggered:

As a tool for a Custom Agent: your Notion AI teammate calls the Worker when it needs data from an external system. As a webhook: something changes in your Notion database, the Worker fires automatically, no AI tokens involved at all. On a sync schedule: pull data from an external system every 15 minutes, every hour, or once a day, into a Notion database that stays live.

You deploy Workers through the Notion CLI. Run npm install -g ntn in your terminal. Authenticate once, write your Worker code (or have Claude Code write it from a plain-English description), and deploy it to Notion’s sandbox. It runs on their infrastructure, not yours.

Ivan Zhao, Notion’s co-founder and CEO, described the vision during the launch: “Any data, any tool, any agent” in one workspace.

Three Automations Worth Building First

The use cases that Notion and early practitioners are demoing are practical enough that I’d build them this week.

Company enrichment for your CRM. When you add a new company and fill in the domain, a Worker fires and auto-fetches the company logo, industry, size, and latest news from the web, filling in those properties automatically. Zero manual data entry at scale. This is the kind of thing operators were either doing by hand, paying a separate enrichment tool for, or running through a Zapier workflow that costs you a task every time it runs.

Status-triggered workflow automation. A project status changes to “offer signed” in your database. A webhook-triggered Worker fires: creates the onboarding document from a template, pings the relevant Slack channel, and creates the first task set in your project database. Fully automated, no AI tokens burned, pure code executing in under a second. This is the Zapier workflow that used to cost you 5-10 tasks per run, now running inside your existing Notion plan.

Live external data sync. Zendesk tickets, Stripe payment statuses, Shopify order updates: all pulled into dedicated Notion databases on a schedule and kept current. Synced properties lock automatically so nobody overwrites live data. You can add your own Notion-native columns on top of them. This is the integration that used to require a $40-80 per month middleware subscription.

The Cost Math

This is the part worth sitting with before your next billing cycle.

Matthias Frank, who runs one of the larger Notion consulting operations in Europe and has been building with Workers since the private beta, published his cost calculations after early testing:

“Polling Salesforce tickets every 15 minutes: 86 cents per month. Pulling from Jira once per day: 1 cent per month. Heavy usage at 9,800 runs per month: roughly $13 per month.” (matthiasfrank.de)

Compare that to what most operators currently pay for Zapier: $19 to $69 per month depending on volume. Make runs $9 to $29. Over a year, that’s $228 to $828 for middleware that Notion Workers could now replace for a meaningful chunk of standard use cases.

Workers are free to use through August 11, 2026, then shift to Notion’s credit system. Three months of free runtime to build and test at no additional cost.

Frank’s own verdict: “Internally, we’ve already stopped building no-code automations for our own workflows... Will we still be building with Make or N8N in six months? Honestly, probably not for most use cases.”

What’s Still Rough

Workers require Notion’s Business plan or above to deploy. That’s $16 per user per month billed annually. If you’re on Free or Plus, this isn’t available to you yet.

You have to use the CLI (ntn). There’s no UI-only path to deploying Workers. That’s a real barrier for operators who have never opened a terminal. The practical workaround: describe what you want in plain English to Claude Code or Cursor, let it write the TypeScript, then deploy it through the CLI. Early practitioners report doing this with no prior coding experience.

Webhooks only trigger on property changes in Notion databases, not on content edits inside pages. Automations based on someone typing inside a doc aren’t there yet.

External Agents (which would let Claude Code and Cursor operate natively inside your Notion workspace as first-class participants) are still on a waitlist, currently in private beta. Ramp, the fintech company, has already built over 300 automations on the platform. But for most operators, the best part of the announcement is still gated.

Workers also have runtime caps, and complex multi-step workflows that chain many operations together still have limitations. n8n and Make have more raw capability for sophisticated automation infrastructure. Workers are the right replacement for medium-complexity automations you’re currently running through middleware, not a full rebuild of a Zapier setup you’ve spent five years constructing.

The credit pricing structure after August is also not fully spelled out yet. Notion says it will follow the same system as Custom Agents, and early cost examples look favorable. But building critical automations on a credit system where pricing isn’t fully locked in carries some risk.

What This Means for Operators Who Are Paying Attention

For the last three years, I’ve watched the tools that used to require a separate vendor get pulled, one by one, into the platforms operators already pay for. The pattern is consistent. It starts with “this is a specialized tool, you need a subscription.” Then someone builds a version of it into the platform you’re already on. Then the specialized tool has to justify its existence with features you’ll never use.

The operators I work with who are consolidating their stacks the fastest share one trait: they’re building new automations on their existing platforms before they reach for a new tool. They evaluate what they already pay for first.

Notion Workers is the first credible signal that automation middleware has a compression timeline. It won’t complete in six months. But if you’re a Notion Business user and you’re currently running ten Zapier workflows that trigger on database property changes, a meaningful portion of those could probably live as Workers today, at a fraction of the cost, inside a platform you’re already paying for.

What to Do With This

If you’re on Notion Business or above, three steps:

Open your terminal and run npm install -g ntn. That installs the Notion CLI. Takes two minutes.

Go to Settings, then Features, then Workers, and activate it. Free through August.

Pick one Zapier or Make workflow you run every week. Write a plain-English description of what it does. Open Claude Code, paste the description, and ask it to write you a Notion Worker. Deploy it through the CLI and watch it run inside your existing workspace.

If you’re on a lower Notion plan, the useful move right now is an audit. List every automation you’re currently running through middleware, what triggers each one, and what it does. Most SMB operators who do this audit discover that 40-60% of their active Zaps are database event triggers. That’s exactly what Workers cover. You’ll be ready to consolidate when you move up.

If you want to think through where automation fits in your current stack, and what’s worth building versus buying, that conversation is something I have with clients regularly: muddventures.com/book.

And if you want to be in the room where operators are sharing actual builds like this in real time, that’s what the Abra AI community is for.

Andrew