Notion Release Notes

📅 Released September 28, 2026 (macOS, Windows, and Linux)

• Improved application stability by preventing the launch of a second instance while the first is still starting.
• Resolved an issue where speaker and microphone status would appear blank during device testing.
• Enhanced recovery processes for crash scenarios and blank screens.
• Fixed issues with Linux audio support, including meeting notes audio capture and diagnostics.
• Added device audio test buttons to the speaker and microphone settings for easier troubleshooting.
• Enhanced meeting notes notifications with better sizing and standalone pill alerts for improved visibility.
• Introduced a Google Meet add-on install banner for easier integration with meetings.
• Smoothed application visuals with experimental corner styling.
• Resolved miscellaneous bugs and made various optimizations to improve user experience across devices and platforms.

Custom blocks in markdown

The markdown content API and Notion MCP now read custom blocks with inherited bindings as <custom-block definition-id="…" url="…" /> instead of <unknown>. You can place existing definitions and preserve unchanged instances during page edits; see Working with markdown content. Definition creation remains in private alpha.

New SIEM event for the AI meeting notes consent setting

The SIEM and DLP event stream now sends workspace.settings.meeting_notes_consent_setting_updated when an admin changes whether a workspace requires consent before AI meeting notes transcription. The payload carries the final state, either enabled or disabled. See SIEM events.

This is separate from the existing audit log entry for a person confirming consent in a meeting. The new event records a change to the requirement, not an instance of consent.

Rate limit waits in the response body

Any 429 or 529 response that includes a Retry-After header now repeats the wait in the body as additional_data.retry_after, so clients that can't read headers, such as MCP clients, can still see how long to wait. Two new rate_limit_reason values identify an endpoint's own limit (public_api_endpoint_rate_limit) and a connection whose API access has been restricted (public_api_request_blocked). A workspace-limit 429 now says that the limit is shared by all of the workspace's connections. See Request limits.

Page writes return 504 when a request times out

Update a page's content as markdown and the notion-update-page MCP tool now return HTTP 504 gateway_timeout when a request runs past its deadline. Before, they returned HTTP 500 internal_server_error. The notion-create-pages and notion-convert-page-to-skill MCP tools already returned 504 in this case. A 504 does not mean the write was undone, so check whether the change was saved before you retry it. A write that runs out of its time budget still returns 503 service_unavailable, with additional_data.retry_guidance. See Request limits for when to retry each status.

File uploads accept CAD and 3D model formats

The File Upload API now accepts common CAD and 3D model formats, including .dwg, .dxf, .dwf, .rvt, .rfa, .3dm, .step, .stl, .obj, and .glb. They attach to pages as file blocks.

application/octet-stream resolves from the file extension

Many HTTP clients label files with application/octet-stream when they can't infer a MIME type from the extension. Create a file upload and Send a file upload now treat that generic type as unspecified and resolve the real type from the filename extension, or from the content type set at creation. Files with unsupported extensions are still rejected.

Check tool access with notion-get-tool-access

Notion MCP has a new notion-get-tool-access tool. Call it with {} to get the full connection-scoped current_tool_access map. It takes an optional tool_names array such as ["search", "ai_search"] to narrow the result. Call it before you use a tool whose availability depends on the plan: to choose between notion-search and notion-ai-search, for example, or to see which parameters the workspace's plan restricts. Those tools now say so in their descriptions, and each points to one call for the whole map that you can reuse across them. It doesn't grant access or change the workspace.

Entries in the map can now include restricted_parameters, which maps a parameter path such as filters.title_only to the reason it's unavailable. A restriction applies even when the entry's status is available, so check it before sending the parameter. Read the reason against your requested value: a single teamspace remains supported even when filters.teamspace_ids lists a restriction on multiple teamspaces. …

AI search accepts filters, and notion-search routes content queries to it

notion-ai-search now accepts the exact filters and sort options that notion-search accepts, and it accepts an empty query for filter-only browsing. These options return Notion-only workspace results so the constraints are enforced exactly, and the response still reports type: "ai_search". Omit them to search Notion and connected sources together. Filtering by editor, last-edited date, multiple teamspaces, title only, or content status, and sorting by date, still require Business or Enterprise. User lookup remains on notion-search with query_type: "user".

Content searches sent to notion-search now run AI search when the connection can use it. When notion-fetch with the id self reports current_tool_access.ai_search.status as available, a keyword content query sent to notion-search searches Notion and connected sources and reports type: "ai_search", so clients that haven't adopted notion-ai-search keep getting unified results. A call that passes an exact filter, an empty query, or a sort other than relevance stays on Notion workspace search. Routing respects the connection's tool list: a connection that can't use notion-ai-search keeps its content searches on workspace search, and the legacy content_search_mode: "ai_search" parameter returns a permission error for that connection. The 30-requests-per-minute limit on `notion-sear…

Notion MCP splits keyword search and AI search

notion-search is now keyword-only. It matches short, specific terms in Notion and no longer searches connected apps like Slack, Google Drive, and Jira. Use it for content search only when notion-fetch with the id self reports that current_tool_access.ai_search.status is not available. It remains the tool for user lookup by name or email.

Semantic search moved to a new notion-ai-search tool. Use it for every content search when current_tool_access.ai_search.status is available, including searches that include specific terms. It takes one concise natural-language query and searches sources connected to the workspace, such as Slack, Mail, and Calendar, when they are available to the caller. Using it requires Notion AI; without it, calls return a prompt with a recovery link, and notion-fetch with the id self reports ai_search in current_tool_access so clients can route to notion-search. notion-ai-search does not accept the exact filters, the sort options, or the user lookup that notion-search accepts.

Clients that still send the old content_search_mode parameter on notion-search keep working: workspace_search behaves like notion-search, and ai_search behaves like notion-ai-search. The parameter is no longer advertised, so call the tool you want directly.

Page covers and icons in notion-fetch responses …

Free workspace block limits now apply to the REST API

Starting today, the REST API enforces the existing Free workspace block limit for internal connections and OAuth connections restricted to selected workspaces. This is not a new workspace limit. See Workspace block limits for the grace period, HTTP 403 response, and background template behavior.

Upgrade prompts for Custom Agent tools in Notion MCP

Notion MCP's Custom Agent tools — notion-list-agents, notion-search-agents, and the session tools — now return a prompt with a recovery link when the workspace doesn't have access to Notion AI and Custom Agents. They previously returned a generic permission error with no recovery link. notion-fetch with the id self also reports these tools as upgrade_required with an upgrade_url, or as plan_required with a landing_page_url and landing_page_action when Notion routes the user through a plan landing page. Clients can use this status to route around unavailable tools before calling.

Workspaces with a billing restriction, such as an unpaid invoice, are treated separately: the tools return a permission error that asks a workspace owner to manage billing, and current_tool_access reports them as not_enabled rather than upgrade_required. …

Capture ideas and draft content in Notion

Your agent can now capture ideas and draft content in Notion without choosing where the page belongs first. The page starts as a private draft, so you can review it and organize it later.

Save and reuse your preferred workflows with Notion Skills

When you ask your AI to save a workflow you want to reuse, it can now create a Notion Skill or turn an existing page into one. Skills are reusable instructions stored as Notion pages that you own and can edit.

When you ask for that workflow later, your AI can find the right Skill and read its instructions before starting.

Find the right page more easily

Your AI can now narrow Notion searches by where a page lives, who created or edited it, when it changed, whether the title matches, and the page's status. It can also sort results and look through up to 50 matches.

Search results now show more context, including where a page lives and whether Notion has verified it. This helps your AI choose between similar or conflicting pages before reading the full content.

Every plan includes filters for creator, creation date, and a single page, data source, or teamspace. On Business and Enterprise plans, your AI can also filter by editor, last-edited date, multiple teamspaces, title, or content status, and sort by date.