Vercel Chat SDK gains Notion adapter so agents can join page comments

Vercel has released a Notion adapter for Chat SDK, its framework for building conversational agents that run across several platforms at once. According to the Vercel blog, an agent already deployed to Slack, Discord, GitHub, Teams or WhatsApp can now also take part in comment discussions on Notion pages, without the team maintaining a separate Notion-specific codebase.

The pitch is straightforward: teams that keep planning and documentation in Notion often debate decisions in page comments, and until now an agent had no way to join those conversations. With the adapter, the same bot that answers questions in a Slack channel can be mentioned directly inside a Notion thread.

How it works

The adapter plugs into the standard Chat SDK setup. A developer instantiates the Chat class, registers the Notion adapter alongside any other adapters, attaches shared state — the announcement's example uses a Redis-backed store — and handles events such as onNewMention. In Vercel's sample code, the bot responds to a mention by posting a message back into the same thread.

Conceptually, the adapter translates Notion into chat-platform terms. Every page is treated as a channel, and every comment thread on that page becomes a chat thread, so an agent's replies land in the correct discussion without extra bookkeeping on the developer's side.

Supported behaviour

According to the Vercel blog, the adapter handles mentions, message editing, conversation history and file attachments, with up to three attachments per message. By default the agent replies when it is @-mentioned. Where a workspace does not support mentions, Vercel says the bot can instead be configured to trigger on a keyword or to respond to every comment.

Notion-specific constraints

Commenting in Notion is narrower than a full chat interface, and the adapter inherits those limits. Vercel states that Notion offers no buttons, modals or reactions, and that card-style messages are rendered as plain markdown. Threads can be started at the level of a whole page or an individual block, but not against an inline span of text within a block. When the agent fetches conversation history, it receives only comments that are still open — resolved threads are excluded.

That last restriction is worth flagging: for agents that summarise or recall earlier discussions, anything a user marks as resolved disappears from the agent's view of the conversation.

Why it matters

Agent frameworks live or die by coverage. Chat SDK's value proposition is that one agent, written once, can meet users wherever they already are, and each new adapter widens that footprint. Notion is a useful addition because it is where context accumulates — the spec, the plan, the decision log. Questions about those artefacts naturally arise in the comments attached to them, so letting an agent answer in place removes the detour of pasting content into a chat client and hoping the bot has enough context.

The constraints are equally instructive. Buttons, modals and reactions are core interaction primitives on Slack and Discord but absent here, so agents that lean on interactive components will need markdown-based fallbacks when running in Notion. The adapter is therefore a strong fit for agents that answer questions, summarise material or take simple actions, and a weaker one for workflow-heavy bots built around rich controls.

Vercel points developers to its documentation to get started, and invites them to browse the wider adapter directory or build adapters of their own.