Notion AI features, 2025 and 2026

A dated inventory of every Notion AI capability across two years. What shipped, when, and the one architectural trait every entry on this list shares.

M
Matthew Diakonov
12 min read
Direct answer · verified 2026-05-28

Across 2025 and 2026 Notion AI shipped roughly twenty major capabilities. Four arcs carry the list. In 2025: AI Connectors for Gmail, Slack, Google Drive, Linear, Calendar, and GitHub; AI Meeting Notes and Enterprise Q&A starting May 13 2025 in Notion 2.51; autonomous Agents from Notion 3.0 on September 18 2025; and a pricing consolidation that bundled AI into Business. In 2026: Mobile AI parity and a refreshed model lineup in 3.2, Custom Agents in 3.3, Skills in March, Workers for Agents in 3.4 on April 14, and the Developer Platform on May 13 2026: Notion Workers, External Agents API with Claude and Codex as partners, the Notion Agent SDK, a Markdown API, and Database Sync.

Source checked 2026-05-28: notion.com/releases. Every dated entry below corresponds to a release page on that index.

The two-year arc, at a glance

Before the dated inventory, here is the shape. 2025 turned Notion AI from a writing helper into a workspace assistant that can pull from the rest of your stack and act on its own. 2026 turned that assistant into a platform other agents can plug into. Read top to bottom, every quarter widened either what the agent can think about or what it can do.

From assistant to platform

  1. 1

    Early 2025

    AI Connectors (Gmail, Slack, Drive, Linear) make Q&A pull from outside the workspace.

  2. 2

    Mid 2025

    Notion 2.51 (May 13) ships AI Meeting Notes; Notion 2.52 (July 10) extends Q&A across databases.

  3. 3

    Late 2025

    Notion 3.0 (Sep 18) rebuilds AI as autonomous Agents; Notion 3.1 (Nov 17) polishes the surface.

  4. 4

    Early 2026

    Notion 3.2 (Jan 20) mobile parity; Notion 3.3 (Feb 24) Custom Agents on trigger or schedule.

  5. 5

    Mid 2026

    Notion 3.4 (Apr 14) Workers for Agents; Developer Platform 3.5 (May 13) makes Notion an agent hub.

2025: every dated Notion AI release

This is what Notion shipped under the AI label in 2025, ordered by date. Every entry links back to a release note on notion.com/releases. Where the public release notes are silent on a precise date, the entry says so and uses the broader month.

Notion AI in 2025, in order

1

Q1 2025: Connectors mature

AI Connectors for Gmail, Slack, Google Drive, and Linear move from limited beta to general availability inside Notion AI's Q&A surface. The assistant starts answering workspace questions with citations pulled from outside Notion itself.

What it does: a question typed into Ask Notion searches Slack threads, Drive files, Gmail archives, and Linear issues alongside Notion pages, returning a cited answer. Where it runs: Notion's cloud, calling the connected service's API with the workspace's OAuth scope.
2

May 13 2025: Notion 2.51, AI Meeting Notes and Enterprise Search

AI Meeting Notes shipped as a new block that captures and summarizes meetings without requiring a bot in the call, with live transcription on Zoom, Google Meet, and Microsoft Teams. The same release strengthened Enterprise Search so AI Q&A could answer questions that drew from connected sources next to Notion content.

What it does: open a page during a meeting, the block transcribes audio in real time, summarizes the conversation, and extracts action items. Where it runs: Notion's cloud transcribes the audio stream the desktop or mobile app uploads. The meeting notes themselves land in the workspace via the Notion API.
3

July 10 2025: Notion 2.52, AI search across databases

Notion AI gained the ability to answer complex questions about databases by drawing from across property values and any notes on database pages. The Linear connector extended to include comments. Google Drive Q&A broadened across .docx, .pptx, .xlsx, .csv, and PDF.

What it does: a question like “which accounts in the sales CRM have call notes mentioning European data residency?” pulls from row property values and from body content on the row's child page. Where it runs: Notion's cloud, against indexed database content the workspace has already synced.
4

Mid 2025: Calendar and GitHub connectors

Connector coverage extended to Google Calendar and Notion Calendar for schedule briefings, and to GitHub (in beta) for surfacing issues, pull requests, and markdown files alongside workspace content.

What it does: “brief me on next week” pulls events from connected calendars; “what is blocking the API refactor” surfaces GitHub issues and PRs. Where it runs: Notion's cloud, against the connector's API.
5

Mid 2025: AI pricing consolidation

Notion discontinued the per-seat AI add-on (around $8 to $10 per user per month depending on plan) and bundled unlimited AI into the Business plan at $20 per user per month. Plus became the AI-light tier, Business became the default for any AI-dependent workflow.

What it does: removes the up-sell from the AI surface and builds the foundation for the credit-metered model that arrives in 2026. Where it runs: the billing surface in Notion's cloud.
6

September 18 2025: Notion 3.0, Agents

The headline release of the year. Notion rebuilt the AI surface as autonomous Agents that can do up to 20 minutes of work across hundreds of pages on their own, creating documents, building databases, searching connected tools, and executing multi-step workflows. Personal Agents took instructions from a dedicated page.

What it does: an Agent can be given a task like “triage every page tagged Q4 planning, summarize, and assign action items” and work through the workflow autonomously. Where it runs: Notion's cloud, metered against the workspace's AI quota at first, then against Notion Credits in 2026.
7

November 17 2025: Notion 3.1

A polish and follow-on release that tightened the Agent surface introduced in 3.0, refined the model lineup behind the assistant, and added quality-of-life improvements to the Q&A flow.

What it does: smaller, on-the-margin improvements layered on the 3.0 architecture. Where it runs: the same cloud surface as 3.0.

2026 so far: every dated Notion AI release

2026 turned the assistant Notion built in 2025 into a platform. Four numbered releases plus a string of mid-cycle drops carry the year through late May. The dates below match the release-note pages at notion.com/releases.

Notion AI in 2026, in order

1

January 20 2026: Notion 3.2, mobile AI parity

Mobile AI reaches desktop parity. A refreshed model lineup, mobile AI note transcriptions, and a new People Directory pre-built database. The context window for cross-page operations triples from 20 to 50 pages.

What it does: the agent answers and acts from the phone the same way it does from desktop. Where it runs: the same cloud surface, reached from a different client.
2

February 24 2026: Notion 3.3, Custom Agents

Autonomous agents that run on a trigger or a schedule, twenty-four hours a day. Free to try through May 3 2026, then metered against Notion Credits starting May 4 2026. Over one million Custom Agents created since launch.

What it does: an agent fires on its own (every Monday at 9am, when a row in a database is created, when a tagged Slack message arrives) and executes a stored workflow. Where it runs: Notion's cloud scheduler dispatches the job; tools the job calls all live in the connector set.
3

March 2026: Custom Skills

Reusable AI tasks saved as first-class commands, callable from the text menu or by @mention. The prompt-as-snippet pattern becomes a named workspace primitive.

What it does: a repeatable prompt (“turn this into a stand-up update,” “extract risks from this spec”) gets a name and lives in the workspace library. Where it runs: same cloud surface, but parameterized.
4

April 14 2026: Notion 3.4 part 2, Workers for Agents

Sandboxed code execution arrives inside an agent run. Workers for Agents lets the agent run deterministic JavaScript or Python in a sandbox during a workflow. Mail, Calendar, and Slack join the first-class connector set for Custom Agents. AI Meeting Notes graduates from beta to general availability. Voice input for AI prompts ships on macOS and Windows.

What it does: an agent can call a deterministic Worker instead of asking the model to reason its way through a structured task, which is cheaper and more reliable. Where it runs: the Worker executes in Notion's sandbox, not on your machine. Voice input captures audio on the client and sends it to the cloud for transcription.
5

May 1 2026: Slack private channel Custom Agents

Custom Agents can read and reply in Slack private channels and direct messages, closing a coverage gap in the Slack connector that mattered for support and ops workflows.

Where it runs: the Slack OAuth scope grants Notion's cloud read and write access to private channels for the workspaces that opted in.
6

May 5 2026: Custom Agent admin controls

Per-agent credit limits, workspace-level credit limits (Enterprise), a credit usage dashboard with spend tracking, an approval flow for member requests to raise limits, and anomaly detection that automatically pauses unusual spending.

What it does: turns the credit unit (which arrived alongside the May 4 metering of Custom Agents) into something admins can govern instead of just observe. Where it runs: the billing surface in Notion's cloud.
7

May 6 2026: Custom Agent Directory

A dedicated workspace library for browsing, pinning, and creating Custom Agents. The Agents Hall of Fame template gallery launches alongside it.

What it does: makes Custom Agents discoverable inside a workspace. Where it runs: the directory metadata is workspace state; the agents themselves still execute in the cloud.
8

May 7 2026: Plan Mode

Before executing a complex change (bulk database updates, multi-page edits), an agent now drafts a plan, surfaces it for review, and waits for confirmation. The chain-of-thought is exposed as an editable artifact, not a black box.

What it does: adds a confirm step to high-blast-radius actions. Where it runs: the plan is generated by the same cloud agent surface, then handed back to the user.
9

May 13 2026: Notion 3.5, the Developer Platform

The most architecturally significant release of the year. Notion Workers (a hosted code runtime with a CLI), the External Agents API with Claude and Codex as launch partners, the Notion Agent SDK (embeds Notion agents inside external apps), a Markdown API, Database Sync (pulls live records from Salesforce, Zendesk, Postgres), a rebuilt developer portal at app.notion.com/developers, expanded permissions, and four developer-changelog items (a meeting notes query endpoint, a 10,000-result pagination cap with a new request_status field, multi-value filters on select / status / multi_select, and agent-tool fixes).

What it does: turns Notion from a destination agents act on into a platform that hosts and orchestrates agents. Where it runs: Notion Workers execute in Notion's sandbox, the External Agents API dispatches over HTTPS from Notion's cloud to the partner agent's cloud, Database Sync pulls into Notion's storage. Workers is free through the beta, with credit-based pricing starting August 11 2026.

The Notion AI connector set, end of May 2026

The connector set is the shape of Notion AI's reach. Every entry here is a tool the cloud agent can call. Add a connector and the agent gains an arm. Remove one and the arm disappears. The following list captures what is wired up by the end of May 2026.

Built-in connectors the agent can call

Gmail

Search threads and archives. Summarize long threads. Draft replies.

Slack

Search public and private channels (May 1 2026), DMs, threads. Reply from Custom Agents.

Google Drive

Query .docx, .pptx, .xlsx, .csv, and PDF content. Cite back to source files.

Linear

Projects, issues, comments. Filter by assignee, creator, label.

Google Calendar

Read events, summarize the week. Pairs with Notion Calendar for unified views.

GitHub

Issues, pull requests, markdown files. Beta as of late 2025.

Notion Calendar

Tight integration. AI Meeting Notes attach to the meeting page automatically.

Salesforce

Pulled in via Database Sync (May 13 2026 Developer Platform).

Zendesk

Database Sync target. Tickets land in Notion databases.

Postgres

Database Sync target. Read live rows from your operational database.

Strava

Named example in the May 13 2026 Database Sync beta. Reads activity data.

External agents

Claude and Codex are the alpha launch partners for the External Agents API.

The trait every feature on this list shares

Walk the inventory once more and ask one question of each entry: where does this feature actually run? Read top to bottom, the answer is identical. Q&A runs in Notion’s cloud. Connectors run in Notion’s cloud. AI Meeting Notes transcription runs in Notion’s cloud. Agents in 3.0 run in Notion’s cloud. Custom Agents in 3.3 run in Notion’s cloud. Workers for Agents in 3.4 run in a Notion sandbox. The May 13 Developer Platform Notion Workers and External Agents API are both dispatched from Notion’s cloud.

That is the single fact no marketing page for any of the individual features lays alongside the feature list. It is not an accusation. A cloud agent with a deep connector set is the right answer for a lot of work, and Notion’s execution of that idea is strong. It is, however, the load-bearing architectural constraint, and naming it makes the next question easy to answer: which of your workflows live entirely behind public HTTPS APIs, and which require a process running on the machine itself.

0

Every feature in the 2025 to 2026 Notion AI list runs in Notion's cloud. The connector set is the agent's reach.

local processes on your Mac across every dated release

Where this leaves work that lives on your Mac

If your work is largely cloud-shaped (Notion documents, Slack threads, Drive files, Linear tickets, Gmail), the 2025-2026 Notion AI feature set covers a lot of it. If your work spends real time inside Xcode, Logic Pro, QuickBooks Desktop, Final Cut, a native Mail client, or any in-house Cocoa tool, the inventory above will not reach it. There is no connector you can install to make the cloud agent talk to those apps, because those apps do not expose HTTPS surfaces for a cloud agent to call.

The way around that constraint is structural, not feature-by- feature. The agent has to run on the machine that has the apps on it. macOS exposes a system-wide accessibility API that lets a local process read the UI tree of any app the user has granted access to, click into menus, fill fields, and read back results. That is the layer that lets an agent reach beyond a browser tab, and it is only available to a process that runs on the Mac.

Fazm runs the same Claude Code agent package Notion’s May 13 Developer Platform connects to over HTTPS, but as a local Node subprocess on your machine. Concretely, the file acp-bridge/src/patched-acp-entry.mjs in Fazm’s open-source repo (github.com/m13v/fazm) imports ClaudeAcpAgent from @agentclientprotocol/claude-agent-acp/dist/acp-agent.js and runs it through runAcp under the user account. It is the agent that Notion’s External Agents API talks to over the network, run locally instead. Chats survive a Mac restart with the full conversation history intact, every chat has a one-click fork button, and the context does not auto-compact.

The simplest way to think about it: Notion AI 2025-2026 is the feature set you reach for when the work fits inside the connector set. A local-process agent is the layer you add when it does not.

Talk through which Notion AI features cover your workflow, and which need a local agent

Bring the list of repetitive tasks you actually want automated. We will walk through which ones live behind cloud connectors and which need a process on your Mac.

Notion AI features 2025 and 2026, FAQ

What is the full list of Notion AI features shipped in 2025?

Notion AI in 2025 split into four arcs. Q&A and Enterprise Search matured into a workspace question-answering layer that cites sources from pages, databases, and connected apps. AI Connectors landed for Gmail, Slack (including private channels), Google Drive (.docx, .pptx, .xlsx, .csv, PDF), Linear, Google and Notion Calendar, and GitHub (issues, PRs, markdown). AI Meeting Notes shipped on May 13 2025 inside Notion 2.51 as a botless transcription block that integrates with Notion Calendar, captures Zoom / Google Meet / Microsoft Teams audio in real time, and extracts action items. The biggest 2025 release was Notion 3.0 on September 18, which rebuilt the assistant as autonomous Agents that can do up to 20 minutes of work across hundreds of pages on their own. November 17 2025 added Notion 3.1. Across the year Notion also restructured AI pricing, eliminating the standalone $8 to $10 AI add-on and bundling unlimited AI into the Business plan at $20 per user per month.

What new Notion AI features have shipped in 2026 so far?

Through late May 2026 Notion shipped four numbered releases (3.2 in January, 3.3 in February, 3.4 across April, and 3.5 on May 13) plus a string of dated mid-cycle updates. Notion 3.2 brought mobile AI to desktop parity, a refreshed model lineup, AI note transcriptions on mobile, and a people directory. Notion 3.3 introduced Custom Agents that run on a trigger or a schedule. March added custom Skills as first-class reusable AI commands. Notion 3.4 part 2 on April 14 shipped Workers for Agents (sandboxed code execution inside an agent run) and added Mail, Calendar, and Slack to the connector set. Through May, Notion shipped Custom Agent admin controls on May 5, a Custom Agent Directory on May 6, Plan Mode on May 7, and the Developer Platform on May 13: Notion Workers (a hosted runtime with a CLI), External Agents API with Claude and Codex as launch partners, the Notion Agent SDK, a Markdown API, Database Sync, and a rebuilt developer portal at app.notion.com/developers.

Which 2025-2026 Notion AI feature is the most consequential?

Honest answer depends on whether you live inside Notion. If yes, Notion 3.0 on September 18 2025 is the inflection point. It rebuilt the assistant as an autonomous Agent that runs multi-step jobs across the workspace, set up the credit-metered surface that all later releases extend, and produced the trigger / schedule abstraction that Custom Agents in February 2026 inherited. If your work is mostly outside Notion, the May 13 2026 Developer Platform is the more consequential moment because it changes Notion from a place agents act on to a place agents are dispatched from. Both share one architectural fact: the agent run happens in Notion's cloud, not on your machine.

What did Notion 2.51 add to Notion AI in May 2025?

Notion 2.51 on May 13 2025 introduced AI Meeting Notes as a new block. It captures and summarizes conversations without requiring a bot in the call, integrates with Notion Calendar so a meeting can attach to a page automatically, captures audio in real time across Zoom, Google Meet, and Microsoft Teams, and extracts action items. The same release strengthened Enterprise Search so AI could answer questions that pulled from connected sources alongside Notion content. AI Meeting Notes hit general availability inside Notion 3.4 in April 2026, which means the May 2025 launch was the beta and the April 2026 release made it stable.

Which AI Connectors did Notion ship across 2025 and 2026?

By the end of 2025 Notion AI had connectors for Gmail (search archives and recent threads), Slack (including private channels and DMs), Google Drive (search across .docx, .pptx, .xlsx, .csv, and PDF), Linear (projects and issues with comments), Google Calendar and Notion Calendar (schedule briefings), and GitHub in beta (issues, pull requests, and markdown). April 14 2026 confirmed Mail, Calendar, and Slack inside the broader connector set and made them first-class in Custom Agents. May 1 2026 closed a gap by giving Custom Agents the ability to read and reply in Slack private channels. May 13 2026 added the Developer Platform's Database Sync feature, which is structurally a new class of connector that pulls live records from Salesforce, Zendesk, Postgres, and similar systems into Notion databases.

Did Notion ship voice input for AI in 2025 or 2026?

Notion shipped voice input for AI prompts in April 2026 on macOS and Windows, alongside Notion 3.4. The 2025 release calendar contained transcription (meeting notes), but the keyboard-or-hotkey voice input you can use to dictate a prompt is a 2026 feature, not a 2025 one.

How did Notion AI pricing change across 2025 and 2026?

Notion discontinued the per-seat AI add-on in May 2025 and bundled unlimited AI into the Business and Enterprise plans. Plus became the AI-light tier and Business at $20 per user per month became the AI-included default. In 2026 the pricing surface shifted again: Custom Agents were free to try through May 3 2026, started metering against Notion Credits on May 4 2026, and Notion Workers (the May 13 Developer Platform runtime) is free through the beta with pricing on credits starting August 11 2026. The 2025 change consolidated AI into a tier. The 2026 change introduced a credit unit that meters specific actions inside the tier.

Can any of these Notion AI features drive native Mac apps like Xcode, Logic Pro, or QuickBooks?

Structurally, no. Every Notion AI feature from 2025 and 2026 runs inside Notion's cloud. The agent reaches the world by calling HTTPS APIs that have been wired up as connectors. Native Mac apps without a public HTTPS surface (Xcode, Logic Pro, QuickBooks Desktop, Final Cut, a custom in-house Cocoa tool) have nothing for the cloud to call. The May 13 2026 Developer Platform connects Notion to external agents like Claude Code and Codex, but the connection is a network call: Notion's cloud talks to the agent service, which still does not have a process running on your Mac with access to your apps. To drive a native macOS app you need a process running on the machine that can use macOS accessibility APIs. That is the architectural line Notion's roadmap does not cross.

How does Fazm relate to Notion's External Agents API?

Fazm runs the same Claude Code agent package Notion's Developer Platform connects to, but as a local Node subprocess under your user account. The file acp-bridge/src/patched-acp-entry.mjs in Fazm's open-source repo imports ClaudeAcpAgent from @agentclientprotocol/claude-agent-acp/dist/acp-agent.js and spawns it through runAcp. The Node process holds the agent loop, mediates tool calls, and uses macOS accessibility APIs to reach the browser, native Mac apps, and Google Workspace. It is the agent that Notion's External Agents API talks to over HTTPS, run locally instead. Persistent sessions survive a Mac restart, every chat has a one-click fork button that opens a new window with the full prior context, and the conversation does not auto-compact.

How did this page land for you?

React to reveal totals

Comments ()

Leave a comment to see what others are saying.

Public and anonymous. No signup.