Notion Workers and CLI: Custom Code in 2026
Notion Workers run custom code on Notion's own infrastructure to sync databases and power agents, while a new CLI lets developers and coding agents build and deploy them.
Notion has spent years being a place to organize information. In 2026 it added a way to run code, quietly turning the workspace into something closer to a platform. Workers and a new CLI let you sync external data, power custom agents, and extend Notion without standing up a single server of your own.
Quick answer
Notion Workers are a hosted runtime that runs custom code on Notion's own infrastructure, powering database sync, agent tools, and webhook triggers without you managing servers. A new Notion CLI lets developers and coding agents sign in, read and act in Notion, and build and deploy Workers. Starting August 11, 2026, Workers run on Notion credits. Custom Agents also got a dedicated Library home and a directory.
Key takeaways
- Workers run custom code on Notion's infrastructure, so there are no servers for you to manage.
- They power database sync, agent tools, and webhook triggers behind the scenes.
- A new Notion CLI lets developers and coding agents build, deploy, and act in Notion.
- Custom Agents now live in a dedicated Library with a browsable directory and access controls.
- Starting August 11, 2026, Workers run on Notion credits, so plan for the cost.
What Workers actually are
The most significant developer change in Notion for 2026 is Workers, a hosted runtime for custom code. Previously, extending Notion with anything beyond its built-in automations meant running your own server: somewhere to host the code, handle webhooks, and stay online. Workers remove that. You write the code, and it runs on Notion's infrastructure.
Under the hood, Workers now power several features you may already use. Database sync, agent tools, and webhook triggers are all built on the Workers primitive. When you sync an external data source into a Notion database, a Worker is doing the fetching and updating, with no server for your team to maintain.
That is the headline capability: you can now sync any data source that has an API into your Notion databases without managing infrastructure. For teams that previously wired up brittle middleware to keep Notion in step with another system, this collapses a whole category of maintenance.
The Notion CLI
Alongside Workers, Notion shipped a command-line interface built specifically for developers and coding agents. With the CLI you can sign in to your workspace, read and take action in Notion, and build and deploy Workers, extending the workspace however your team needs.
The mention of coding agents is deliberate. A CLI is exactly the kind of interface an AI coding agent can drive, so an agent can now read your Notion data, make changes, and deploy Workers on your behalf. That fits the broader pattern of tools exposing scriptable interfaces for agents to use, which our comparison of Claude Code versus Cursor covers in the coding context.
For human developers, the CLI is the ergonomic way to work with Workers: sign in, iterate on your code locally, and deploy without clicking through a web UI.
Custom Agents get a real home
Notion's AI story in 2026 leans heavily on agents, and the management around them matured. Custom Agents now have a dedicated place in your Library, with a Custom Agent Directory to browse every agent in the workspace, pin favorites, and create new ones to automate busywork around the clock.
Crucially, there are access controls. You can choose who can create Custom Agents, either specific individuals or user groups, and expand that access over time as you build confidence. That governance matters, because an agent with write access to your workspace is exactly the kind of thing you want to gate carefully. Our guide to Notion 3.0 AI agents covers how those agents behave day to day.
| Capability | Before | 2026 |
|---|---|---|
| Run custom code | Your own server | Workers (Notion-hosted) |
| Sync external data | Custom middleware | Workers-powered database sync |
| Developer interface | API and web UI | Notion CLI |
| Manage custom agents | Scattered | Library home and directory |
| Control who builds agents | Limited | Per-user or group access control |
Wider AI upgrades
The Workers and CLI news arrived alongside a broader set of AI improvements. Notion AI in 2026 expanded its context window to 50 pages (up from 20), added cross-page AI blocks, sub-three-second autofill, relation-aware autofill, voice input, and workspace-level prompt templates. Individually these are incremental; together they make the AI features noticeably more capable on real, sprawling workspaces.
The context window jump is the one to notice. A 50-page context means the AI can reason over much larger documents at once, which changes what kinds of summarization and analysis are practical.
The credits question
There is a cost dimension you cannot ignore. Starting August 11, 2026, Workers run on Notion credits. If you build automations on Workers, factor credit consumption into your planning, especially for high-frequency syncs or webhook-heavy workflows. A Worker that fires constantly will draw more credits than an occasional batch job. Model your usage before you commit critical automations to Workers so the bill does not surprise you.
What to do right now
- Identify a manual data sync in your workspace that a Worker could automate.
- Install the Notion CLI and sign in to your workspace to experiment.
- Build a small Worker to sync one external API into a Notion database.
- Set access controls for who can create Custom Agents before opening it up.
- Model your credit usage, since Workers run on credits from August 11, 2026.
- Explore the Custom Agent Directory to see what your team has already built.
Frequently asked questions
What are Notion Workers?
Workers are a hosted runtime that runs your custom code on Notion's own infrastructure, with no servers for you to manage. They power database sync, agent tools, and webhook triggers, letting you extend Notion programmatically.
Do Workers cost extra?
Starting August 11, 2026, Workers run on Notion credits. High-frequency syncs and webhook-heavy automations consume more credits, so model your expected usage before committing important workflows to Workers.
What can the Notion CLI do?
The CLI lets developers and coding agents sign in to a workspace, read and take action in Notion, and build and deploy Workers. It is the ergonomic way to work with Workers and is designed to be drivable by AI coding agents.
Can I sync any external data into Notion now?
Effectively yes, if the source has an API. Workers-powered database sync lets you pull any API-accessible data source into a Notion database without running your own middleware or servers.
How do I control who can build agents?
Notion's Custom Agents now live in a dedicated Library with access controls. You can grant agent-creation ability to specific individuals or user groups and expand access gradually as you gain confidence in how agents behave.
