Notion AI buttons let you launch an AI workflow from the page or database where you need it. Instead of opening a chat, remembering the right Skill and explaining the context again, you click a button with a prepared prompt. It sounds like a tiny update. But if you’ve built useful AI workflows that your team keeps forgetting to use, this is worth your attention.
Last updated: 27 October 2026
What Are Notion AI Buttons?
A Notion AI button is a page button or database button that uses the Send message to agent action. You give it a prompt and relevant context, then choose your personal Notion AI or a Custom Agent as the recipient.
For example, your meetings database could have a Process Meeting button. Clicking it launches a request to review that meeting using your meeting-processing Skill.
The button is the entry point. The Skill holds the reusable instructions. The agent does the work.
That distinction matters: you don’t need to squeeze your entire process into a button prompt. You can keep the process in a Skill and use the button to call it in the right context.
How Do You Trigger Notion AI With A Button?
Add a button, choose Send message to agent, select the recipient and write your prompt. Include the page and Skill references the agent needs before testing the workflow.
How Do You Set Up A Page Button?
- Open the Notion page where you want the workflow to start.
- Type
/buttonand select Button. - Give it a clear name, such as Process Meeting or Start Daily Wrap-Up.
- Add the Send message to agent action.
- Choose your personal Notion AI or a Custom Agent.
- Write the prompt and use
@mentions to add relevant pages or Skills. - Save the button and click it to test.
In my demo, sending a prompt to personal Notion AI opened the sidebar and started the conversation.
Notion’s button guide explains the general setup and how mentions and variables work. Its action list does not yet include Send message to agent, so the AI-specific steps here follow my hands-on demo.
How Do You Set Up A Database Button?
Add a Button property to your database, then configure its Send message to agent action. Include a reference to the current database page so the prompt points to the entry you clicked.
This is useful when you want the same workflow available for every meeting, lead, project or task.
A meeting-processing prompt could look like this:
Use [meeting-processing Skill] to review [this meeting].
Read the meeting and relevant project context.
Propose follow-up tasks and any client communication needed.
Stop for my approval before creating or updating anything.Replace the bracketed placeholders with native references in the button editor. Simply typing a Skill’s name is not the same as selecting its page reference.
You can also pass values from the database page into the prompt. In the demo, I show how earlier button steps can define variables whose values can then be included in the AI request.
What Are The Current Limitations?
In the version I demonstrated, personal Notion AI launched in Auto mode, and the button didn’t offer a way to preselect a particular model. I’d like more control here, especially for workflows where I already know which model I want.
Skills also needed to be added through @ mentions in the button prompt. The slash-command Skill picker wasn’t available there in my demo.
These are observations from the demonstrated interface, not guarantees about every future version. Notion’s general Agent documentation describes model selection in chat, but that does not establish whether a button can preset a model.
Why Do Buttons Make AI Workflows Easier To Adopt?
Buttons put an AI workflow where someone is likely to need it. That removes the need to remember which Skill to use, where to find it and what context to supply.
I think of this as the human context window.
AI models can handle more and more context. Your ability to remember every useful workflow you’ve built doesn’t grow at the same speed.
You might have a Skill for processing meetings, another for reviewing leads and another for planning projects. They can all work brilliantly—and still sit unused because nobody remembers them at the right moment.
A button on the relevant page acts as a small nudge: here’s what you can do next.
This is especially useful in a team. Your power users can build the process without asking everyone else to become experts in prompting or Skill selection.
It’s also an extension of what makes a well-built Notion workspace useful: relevant information finds you through connected projects, tasks and meetings. Now the relevant AI workflow can find you there too.
For a deeper look at how agents hand off work across your workspace, see how to build multi-agent orchestration in Notion.
What Can You Do With Notion AI Buttons?
Start with a repeated workflow that already has a clear home in your workspace. Meetings, CRM records, tasks and team dashboards are all useful places to put a button.
Here are six practical options:
| Use Case | Where To Put The Button | What The Workflow Does | Where Human Judgment Helps |
|---|---|---|---|
| Process Meetings | Meetings database | Proposes follow-ups, tasks and client communication | Deciding which actions deserve to become tasks |
| Schedule CRM Conversations | Lead or contact record | Uses connected calendar tools to find options or create a booking link, then drafts a message | Checking timing and reviewing the outreach |
| Assess AI Task Readiness | Tasks database | Identifies whether AI can do the task and what is missing | Choosing which gaps are worth closing |
| Run A Daily Briefing Or Wrap-Up | Personal or team dashboard | Coordinates reviews of relevant work and connected sources | Setting priorities and resolving loose ends |
| Guide An SOP | Onboarding or process dashboard | Walks someone through questions and required steps | Providing inputs and making process decisions |
| Triage Internal Requests | Internal support page | Clarifies the issue and prepares a ticket when needed | Reviewing ambiguous requests and escalations |
1. How Can You Process Meeting Follow-Ups?
Put a Process Meeting button in your meetings database and connect it to a Skill that reviews the meeting before proposing next steps.
The useful part isn’t just extracting a list of things people mentioned. It’s reviewing those items in context.
Based on my experience with our own tasks and client workflows, I usually want a human gate here. Three actions might have been discussed, but that doesn’t mean all three belong on a to-do list.
Your workflow can propose tasks, draft client communication and identify project-context updates. You then decide what should actually be saved.
2. How Can You Schedule Meetings From Your CRM?
Add a scheduling button to a lead or contact record. With Notion Calendar connected and the relevant tools available, a scheduling Skill can find suitable times or create a booking link.
A second Skill can draft the outreach message using your communication guidelines.
For example, the button could ask the agent to find options in the next two weeks, then draft a short invitation for that contact.
The button doesn’t supply calendar access by itself. It launches a workflow that relies on your connected tools and scheduling instructions.
3. How Can You Find More Tasks To Hand Over To AI?
Add a Can AI Do This? button to your tasks database. Have it assess whether the agent could complete the task and explain what’s missing if it can’t.
This is the idea behind my “Help Me Help You” Skill.
Rather than asking a vague question about what AI can do, you assess a real task:
- Can the agent do it now?
- Does it need another tool or access to a source?
- Have you explained the process clearly enough?
- Is the missing piece information—or human judgment?
The most interesting answer is often “yes, if…”. It points to a specific gap you might be able to close.
4. How Can You Run A Daily Briefing Or Wrap-Up?
Put a briefing or wrap-up button on your daily dashboard. Use it to launch a coordinating Skill that reviews the relevant work and brings loose ends into one conversation.
A coordinating Skill calls on other Skills rather than trying to do every job itself.
For example, an end-of-day workflow could review meetings, check connected messages and help you decide what needs attention before you finish.
Keep its scope clear. The agent can only review sources it can access, and you still need to decide what matters.
5. How Can You Turn An SOP Into A Guided Process?
Use a button to launch an AI-guided version of your standard operating procedure. Instead of asking someone to read the instructions and remember them, the agent walks them through the process.
This works well when AI can help but shouldn’t do everything independently.
In an onboarding project, for example, we helped an HR team turn the process of creating an onboarding plan into a guided workflow. The agent asks for the information needed at each stage.
The same pattern can support workspace onboarding, sales reviews or drafting a landing page with the right templates and brand guidance.
The aim isn’t to remove the human. It’s to make following the process easier than forgetting it.
6. How Can You Improve Internal Ticket Intake?
Put a Get Help or Submit A Request button on your internal support page. Launch a short AI interview that clarifies the issue before creating a ticket.
A form is already better than requests scattered across every channel. A conversation can go further when requests need clarification.
For common questions, the agent may be able to help immediately using approved guidance.
For more complex issues, it can ask about impact and apply your triage criteria. That’s more useful than asking everyone to select an urgency level and hoping they interpret it consistently.
The criteria still need to exist. A button won’t invent a sensible support policy for you.
When Should You Use A Button Instead Of An Autonomous Agent?
Use a button when a person should deliberately start the workflow or contribute judgment along the way. Use an autonomous agent when the trigger, instructions and acceptable actions are clear enough for background execution.
These aren’t opposing tools. A button can also send a message to a Custom Agent.
The real decision is whether the work should happen with you or without you.
Meeting follow-ups are a good example of co-driving: the agent proposes, you add context and approve the useful actions.
For a predictable background process, making someone remember to click a button may simply add friction.
Pro Tip: Start by putting one well-tested workflow where people already work. A clear button calling a useful Skill is a better starting point than a dashboard full of AI actions nobody understands.
Want to make Notion AI part of how your whole team works? The Notion for Teams free course walks you through the frameworks that matter most.
💼 Need the support of certified Notion Consultants? My team and I are here to help!
Frequently Asked Questions
Can Notion Buttons Trigger AI Workflows?
Yes. The Send message to agent action lets a page button or database button send a prepared prompt to personal Notion AI or a Custom Agent. The workflow’s results depend on the instructions, context and tools available to that agent.
Can You Use A Notion Skill In A Button Prompt?
Yes. In the interface I demonstrated, you could reference the Skill’s page using an @ mention in the button prompt. The slash-command Skill picker wasn’t available in that editor, so use a native page reference rather than just typing the Skill’s name.
Can You Choose The AI Model For A Notion Button?
In my demo, the button launched personal Notion AI in Auto mode and didn’t provide a way to preset a model. This is a button-specific observation; model selection in a normal agent chat is a separate capability.
Does Clicking An AI Button Mean Everything Runs Automatically?
No. The prompt and Skill can instruct the agent to propose changes and wait for approval. That makes buttons useful for human-in-the-loop workflows, not just hands-off execution.
