Notion AI features, April 2026: the week two products landed on "skills" from opposite directions
Every other guide on April 2026 Notion AI just relists the changelog: Workers for Agents, AI Autofill, voice input, Mail plus Calendar plus Slack. Below the feature list is the part no one is covering. On April 14 Notion added Agent Skills (save a workflow, call it by name). Six days later Fazm shipped 17 agent skills as plain Markdown files in the .app bundle. Same primitive, same week, opposite implementations. This guide walks through every Notion AI change that actually shipped this month, then shows the specific files and code lines that make the two converge and diverge.
Every Notion AI feature shipped in April 2026
The big drop was Notion 3.4 part 2 on April 14, 2026. There were eleven distinct AI-adjacent changes. Two days later a model swap took the default to Anthropic Opus 4.7 (3x fewer tool errors vs 4.6 by Anthropic's own numbers). Below is the complete list with the one-line user-facing consequence for each, grouped by where the change lives.
Workers for Agents
Sandboxed code execution for Custom Agents. Enterprise-only at launch. Lets the agent run a short code block instead of chaining API connector calls.
AI Autofill in databases
Custom Agents enrich, extract, and categorize rows on write. The database column becomes the agent trigger.
Notion Agent Skills
Save a workflow once (weekly update, doc reshape, brief prep), call it by name. The reusable unit for Custom Agents.
Mail + Calendar + Slack
New integrations tab on the Custom Agent settings page. First-party auth, agent reads and writes across the three.
Inline Doc Edits
Select text, the agent edits it in place instead of returning a response you have to paste.
Voice Input (hold to speak)
Microphone button on AI prompts. macOS + Windows. Scoped to AI interactions, not block-level editing.
Custom AI Meeting Notes instructions
Fix your team format once (decisions, action items, risks). Every summary follows it.
Salesforce + Box connectors
Search accounts, opportunities, contracts, proposals. Pulls records into the agent turn.
AI Meeting Notes API
Transcripts and summaries exposed to third-party integrations for automated follow-up flows.
n8n MCP integration
Custom Agents call n8n workflows. First public MCP hook inside Notion's agent runtime.
Opus 4.7 as default model
Shipped April 16. Anthropic reports 3x fewer tool errors vs Opus 4.6. Flipped silently for all Notion AI users.
The change the other recaps skip
Read the list back. Workers for Agents is a runtime. Autofill is a database trigger. Mail, Calendar, Slack, Salesforce, Box are integrations. Inline edits and voice are surface ergonomics. Meeting Notes API is a public endpoint. That leaves one item that is different in kind: Notion Agent Skills. A skill is not a surface, not a connector, not an API. It is the unit of reusable agent behavior. The same week Notion added that primitive, Fazm v2.4.0 shipped a version of the same primitive from the other direction. If you line the two up, the difference is not what each can do, it is where each one lives and what each one can read on the way to doing it.
“Fazm v2.4.0 ships 17 Markdown skill files inside the signed .app bundle. Zero of them are compiled. All of them are readable in any editor and forkable into your own project.”
Contents/Resources/BundledSkills/ on 2026-04-20
Skill, Notion edition: how Notion Agent Skills execute
A Notion Skill is a saved prompt-plus-context bundle inside Notion. You capture a workflow once (the release notes list three canonical examples: draft weekly update, reshape a doc in team format, prep a brief before a meeting), give it a name, and re-call it on demand. The skill runs in the Notion Agent. The agent can read from Notion docs and databases, from AI Meeting Notes, and from whatever is wired in the integrations tab (Mail, Calendar, Slack, Salesforce, Box, n8n MCP). The rails are those surfaces. Anything outside them is out of reach.
What happens when you call a Notion Skill
Invocation
You type or speak the skill name into the Notion Agent. The hold-to-speak microphone shipped in 3.4 part 2 works here. Skill name becomes the agent's entry prompt.
Context pulled from Notion surfaces
The agent reads the current doc, the database row it was triggered from, AI Meeting Notes you link, or whatever context the skill was captured with.
Tool calls to the integration allowlist
Gmail, Outlook, Google Calendar, Outlook Calendar, Slack, Salesforce, Box, and the n8n MCP server are reachable. No other tool is reachable. This is the wall.
Model call (Opus 4.7 by default after April 16)
After the model swap the skill runs on Opus 4.7 unless the workspace manually pins an older model. Custom Agents can also be assigned one of the new efficient models (GPT-5.4 Mini, Haiku 4.5, MiniMax M2.5).
Write back to a Notion surface
Inline Doc Edits means the result can land directly in the selected text. Otherwise output goes to a chat pane, a database cell, or a shareable read-only chat link (new in 3.4 part 2).
Skill, Fazm edition: 17 Markdown files inside a signed app
Fazm v2.4.0 (April 20, 2026) ships its skill layer as static files in the signed .app. Every skill is a .md document with YAML frontmatter. No code generation step, no compiled binary, no Notion-like cloud registry. The Claude host inside Fazm picks up the whole folder at launch. Here are the exact filenames, pulled fresh from Contents/Resources/BundledSkills/.
What a single skill file looks like. This is xlsx.skill.md, trimmed for display. Opening it in any text editor gives you the whole thing. Copying it into another Claude-based host (Claude Code, Claude Desktop, a custom ACP client) makes it work there.
The execution layer each skill sits on
A skill is only as reachable as the tools underneath it. Notion Skills sit on Notion surfaces plus the integrations tab. Fazm skills sit on five MCP servers that are hardcoded in the .app, plus any MCP servers the user adds at ~/.fazm/mcp-servers.json. Both lists are worth naming explicitly.
Fazm v2.4.0 skill execution layer
The five built-in MCP servers are declared on one line of acp-bridge/src/index.ts. The set is fixed inside any release build.
The same primitive, from two sides
If you hold the two implementations next to each other, the shape is the same: a reusable unit of agent behavior with a name. The differences are in where the unit lives, what it can read, and how much of it you can inspect. Here is the side-by-side.
| Feature | Notion Agent Skills | Fazm skills |
|---|---|---|
| Storage format | Saved object inside a Notion workspace | Plain .md file with YAML frontmatter |
| Shipped | 2026-04-14 in Notion 3.4 part 2 | 2026-04-20 in Fazm v2.4.0 |
| How you inspect one | Navigate to the skill inside Notion | Open the .md file in any text editor |
| How you fork one | Duplicate inside Notion (stays in Notion) | Copy the .md file to another Claude host |
| What the skill can read | Notion docs, databases, Meeting Notes, integrations allowlist | Anything reachable by 5 built-in MCP servers plus user MCP |
| What the skill can drive | Gmail, Outlook, Calendar, Slack, Salesforce, Box, n8n MCP | Any Mac app via AXUIElement accessibility APIs |
| Portability | Tied to Notion Agent runtime | File moves to any Claude-compatible host |
| Code execution | Workers for Agents, Enterprise plan only at launch | Runs locally via macos-use, playwright, or user MCP |
| Voice invocation | Hold-to-speak microphone on AI prompts | Floating bar push-to-talk in Fazm UI |
| Default model after April 16 | Opus 4.7 default (Custom Agents can pin) | User-selectable (Opus 4.7, Sonnet 4.6, Haiku 4.5) |
Why accessibility APIs matter for any "drive my apps" feature
When Notion added Mail, Calendar, and Slack to the Custom Agent on April 14, the mechanism was first-party cloud APIs. That approach is reliable but lives or dies on whether Notion has wired that specific provider. The alternative, which Fazm defaults to, is the macOS Accessibility API. AXUIElement calls return role, title, value, focused state, frame, and children of any window element as structured text. No screenshots, no vision OCR, no per-app integration contract. That is what lets Fazm reach apps Notion cannot list: Preview, Numbers, Keynote, Xcode, Figma Desktop, Logic, Final Cut, Zoom, Discord, the Finder sheet you already have open. The accessibility path is what desktop agents run on when they are not boxed into a provider allowlist.
Driving a local Mac app without a cloud integration
Agent can only reach apps that are in a cloud-API allowlist. Notion 3.4 added Mail, Calendar, Slack, Salesforce, Box. Everything else on your Mac is invisible.
- Waits on Notion to expose each new provider
- Cannot read Preview, Numbers, Keynote, Xcode, Final Cut
- No access to the window you have open right now
- Secret storage lives outside your machine
A practical April 2026 split
If you already live in Notion, the April 14 release is a real upgrade. You do not need to leave for the flows Notion is designed to serve: docs, databases, meeting notes, CRM-adjacent agent work, Mail plus Calendar plus Slack. The question the other recaps skip is what to do when the workflow touches something outside that allowlist. A clean split works:
Which skill layer to run for which flow
- Draft a weekly update from Notion docs and database rows → Notion Agent Skill (3.4 part 2 is the right tool).
- Prep a brief from Notion pages plus Gmail plus Google Calendar → Notion Agent Skill via the new integrations tab.
- Summarize every new Salesforce account into an AI Meeting Notes follow-up → Notion (Salesforce connector + AI Meeting Notes API).
- Edit a .xlsx sitting in ~/Downloads and save it back → Fazm xlsx skill (no Notion surface involved).
- Pop a PDF open in Preview, extract a figure, paste it in Keynote → Fazm skills over macos-use.
- Drive the Xcode Organizer through a release upload → Fazm skills over macos-use (Notion cannot reach Xcode).
- Pull a Figma layer, resize it, push it to a WhatsApp thread → Fazm skills over playwright + whatsapp MCP.
- Run the same skill across both surfaces → fork the Fazm .md into a Notion skill body, or vice versa.
What "same primitive" means for the next release cycle
The bet worth making in April 2026 is that every serious agent host will treat a skill (a named, reusable unit of agent behavior) as the reusable artifact, not prompts and not tools. Claude Code got there first with skill.md. Notion is there now with Agent Skills. Fazm is there with BundledSkills/. Cursor has rules. If all four standardize on a Markdown-plus-frontmatter shape (as Claude Code, Fazm, and the agent-skills-on-disk flavor of Notion's Custom Agents already do), the portability becomes real: one .md file, four hosts.
Until that settles, the useful thing for a Notion AI user in April 2026 is to know where each side's wall sits. Notion Skills do everything inside Notion and the allowlist. Fazm skills do everything on the Mac and inside the user MCP config. The two are not rivals in the day-to-day, they are complements that happen to share a word.
TL;DR for a Notion AI user reading this in April 2026
Notion 3.4 part 2 made Custom Agents a lot more useful for anything that lives in Notion or the six cloud providers now in the integrations tab. The one item that is not a surface or an integration is Notion Agent Skills, which is the same abstraction Fazm shipped six days later as 17 plain .md files. Run both side by side: Notion Skills for Notion and cloud-API flows, Fazm skills for anything that touches your Mac. When a Markdown skill format becomes portable across hosts (likely by the next Notion release cycle), the choice of host stops mattering and the skill becomes the durable asset.
Want to pair Notion Skills with a desktop agent?
Book a 15-minute call and we will walk through a skill that starts in Notion and finishes in a Mac app Notion cannot reach.
FAQ about Notion AI features April 2026
What AI features did Notion ship in April 2026?
Notion 3.4 part 2 dropped on April 14, 2026 with eleven AI-adjacent changes. Custom Agents got easier fine-tuning plus access to new models (GPT-5.4 Mini and Nano, Haiku 4.5, MiniMax M2.5) at a 35 to 50 percent lower run cost. AI Autofill brought Custom Agents directly into databases so rows enrich, extract, and categorize on write. Notion Agent Skills let a user save a workflow (a weekly update, a doc reshape, a brief prep) as a reusable name the agent can re-run. Mail, Calendar, and Slack were added to the Custom Agent settings page as first-party integrations. Inline Doc Edits let the agent edit selected text in place. Voice Input added hold-to-speak to the microphone button for AI prompts (macOS and Windows). Custom AI Meeting Notes instructions exposed format control. Salesforce and Box shipped as new connectors. The AI Meeting Notes API opened transcripts and summaries to third-party integrations. And the n8n MCP integration lets Custom Agents run existing n8n workflows. On April 16 Anthropic's Opus 4.7 was swapped in as the default Notion AI model (Anthropic claims 3x fewer tool errors vs Opus 4.6).
What are Notion Agent Skills and why do they matter?
Notion Skills are saved prompt-plus-context bundles: 'that thing you always ask Notion Agent to do' captured once and callable by name. The release notes call out three concrete examples: drafting weekly updates, reshaping a doc in your team's format, and prepping briefs before a meeting. Skills live inside Notion and operate against Notion surfaces plus whatever is in the Custom Agent integration allowlist (Mail, Calendar, Slack, Salesforce, Box, n8n, and the connectors). They matter because the skill, not the prompt, becomes the unit of reuse. Every large agent host is converging on the same primitive in the same quarter. Claude Code skills landed earlier in 2026. Fazm v2.4.0 (April 20, 2026) bundles 17 .md skill files in the signed macOS .app. Cursor has a similar 'rules' abstraction. When every host treats skills as the reusable unit, the portability of your skill layer decides the rest.
How is Fazm's skill layer different from Notion Agent Skills?
Notion Skills are stored inside Notion and execute inside the Notion Agent against cloud APIs. You cannot read them as files, cannot diff them in git, cannot move them to another agent host, and cannot attach them to a local Mac app like Keynote or Xcode. Fazm ships skills as plain Markdown files with YAML frontmatter inside Contents/Resources/BundledSkills/ of the signed .app. The 17 files shipped in v2.4.0 are ai-browser-profile, canvas-design, deep-research, doc-coauthoring, docx, find-skills, frontend-design, google-workspace-setup, pdf, pptx, social-autoposter, social-autoposter-setup, telegram, travel-planner, video-edit, web-scraping, xlsx. Because they are Markdown, you can open one in any editor, fork it, copy it into your own project, and the Fazm Claude host will pick it up. Because Fazm's execution layer is the macOS accessibility API plus five built-in MCP servers (fazm_tools, playwright, macos-use, whatsapp, google-workspace) declared on acp-bridge/src/index.ts:1266, a skill can drive any Mac app on your machine, not only Notion.
Can the Notion Agent drive non-Notion apps on my Mac?
Only if those apps are in Notion's integration allowlist, which after April 14, 2026 covers Calendar, Mail, Slack, Salesforce, Box, and whatever the n8n MCP can reach. The Notion Agent cannot open a PDF in Preview and extract a figure, cannot run a formula in the Numbers window you already have open, cannot click 'Send' inside your Xcode Organizer release sheet, and cannot drag a layer in a local Figma file. Any Mac-app behavior outside Notion's allowlist needs a different execution layer. That is the wall a desktop agent (like Fazm) is designed to go past. Fazm's macos-use MCP server (a native Mach-O binary inside Contents/MacOS/mcp-server-macos-use) reads any visible Mac UI through AXUIElement calls and clicks it through accessibility events, no screenshot pipeline, no per-app integration.
What is Workers for Agents and is it generally available?
Workers for Agents is Notion's sandboxed code-execution layer for Custom Agents, shipped in 3.4 part 2 on April 14, 2026. The agent can run short code blocks in a Notion-controlled sandbox instead of having to chain tool calls through API connectors. It is scoped to Enterprise plans at launch, not available on Plus or Business. So if your team is on Plus, the skill-style workflows ship but the code-execution primitive is not on the menu. For most teams this is the single biggest 'what tier am I on' decision to redo after April.
Where do voice input, inline edits, and AI Meeting Notes custom instructions change the daily Notion loop?
Voice input, shipped in 3.4 part 2 for macOS and Windows, is a hold-to-speak microphone button on AI prompts. It is faster than typing for messy prompts but only applies to AI interactions (inline AI, sidebar chat, AI Meeting Notes), not block-level editing. Inline Doc Edits mean the agent now modifies selected text directly in the document instead of returning a response you have to paste. Custom instructions for AI Meeting Notes let you fix a house format (who decided what, action items with owners, risks, next meeting) once and have every summary follow it. The three together push Notion AI from 'a sidebar panel you sometimes open' toward 'the primary interaction with the doc.' The ceiling is still Notion surfaces: nothing about voice, inline edits, or meeting notes leaves Notion.
How do Mail, Calendar, and Slack integrations work after April 14, 2026?
In the Notion Agent settings there is a new integrations tab. Connect a Gmail or Outlook account, a Google or Outlook calendar, and a Slack workspace, and the Custom Agent can read, summarize, and act on those sources in the same turn. The agent can draft an email, schedule a meeting, or reply in a Slack thread without bouncing through Zapier. This is first-party auth, so secrets live in Notion, and the available actions are whatever Notion exposes. Compared to MCP, it is more reliable but less extensible. You cannot add a sixth provider by dropping in a server; you wait for Notion to expose it.
If I already use Notion AI heavily, should I bother installing Fazm?
The answer is a clean split. Everything that lives in Notion (docs, databases, meeting notes, the Custom Agent against Mail, Calendar, Slack, Salesforce, Box, n8n) is what Notion AI is designed for, and the April 2026 release makes that loop much faster. Everything that lives outside Notion (any Mac app you also use, any file that never touches Notion, any workflow that reads the current state of your desktop) is the Fazm surface. The two are complementary, not substitutes. A common working pattern this month: Notion Skills for knowledge-base and CRM-style flows, Fazm skills for anything that touches your Mac directly, and you let both run. Fazm's google-workspace MCP also reaches Gmail, Calendar, and Drive, so you can replicate Notion's Mail + Calendar agent on the desktop side if you need to operate outside Notion.