Custom Agent

With Custom Agents, you build shared workflows that automate recurring work for your team — running exactly how you need them, behind the scenes 🤖
跳转到常见问题
Custom Agents are currently in beta and subject to the beta terms of your agreement.
Custom Agents automate recurring, manual workflows for your entire team. They run automatically in the background on set triggers using your existing docs and databases as context.
Set them up once — building a workflow for repetitive tasks like weekly reports or triaging feedback — and it becomes a shared resource the whole team relies on.
What are Custom Agents?
Custom Agents live inside Notion and run on your instructions. Once you set them up, they can:
Read from Notion pages and databases and certain connected apps.
Run on recurring triggers and workspace events.
Take actions such as posting reports, filing bugs, updating records, or sending messages.
Unlike Notion Agent, Custom Agents are designed to run automatically in the background based on triggers and schedules.
Use your existing docs and databases as context
Custom Agents are built directly into Notion. Agents use your existing docs and databases as context and connect across Slack, increasing productivity. Custom Agents can:
@mentionAgents in Notion pages, database properties, and comments.Attach them to database events (for example, when a page is created or updated).
Let them monitor your workspace and connected tools according to the triggers you configure.
Handle recurring work automatically with triggers
Use triggers for Custom Agents to run without you manually starting them each time. Set a trigger once, then the work happens continuously in the background.
Run on a schedule (daily, weekly, monthly, and more).
React to events in Notion and Slack.
Continue running in the background once you publish them.
This unlocks automated workflows like regular reports, triage queues, and knowledge maintenance, helping you reclaim your time.
Safe and transparent by design
Agents act only on the pages, databases, and external apps you explicitly grant access to. They never have full workspace access by default, reducing risk.
Control who can edit, run, or interact with each Agent.
View activity logs to see what an Agent did and when.
Use Version history to review or restore past configurations.
Keep runs reviewable and reversible so you can safely iterate.
You must be on Notion’s Business or Enterprise Plan.
To build or edit Custom Agents, use desktop or web. You can see or interact with Agents on desktop or web.
View and interact with any content Agents create in Notion pages and databases on mobile.
View Agent posts in Slack through the Slack mobile app.
You can build a Custom Agent from multiple locations. The primary entry point is the Agents section in the sidebar.
Go to the
Agentssection in the left sidebar and select+to create a new Custom Agent.Choose how you want to start:
Create from a template
Choose a template.
Review the draft instructions, triggers, and access that Notion AI generates and iterate.
Save.
Create with AI chat
In the chat, describe what you want the Agent to do using natural language.
Review the draft instructions, triggers, and access that Notion AI generates and iterate.
Save.
Create from scratch
Select
Create blank.Start from an empty instructions field or chat with you.
Craft your instructions manually, following best practices for clear, concrete instructions. Define what the Agent should do, how it should behave, and what work it should handle.
Set triggers, access, your AI model until they match your workflow.
Save.

To create clear instructions for your Agent, start with the job and outcome you want. Then add concrete steps, inputs, and outputs. Use examples when you have them.
Tip: Use our Custom Agent templates as a starting point.
Triggers determine when your Agent runs. You can combine multiple trigger types for a single Agent.
Automate workflows with recurring, time-based schedules
Use recurring schedules to run Agents on a cadence.
Open your Custom Agent's
Settings.Go to the
Triggerssection.Add a
Recurringtrigger.Choose when you want the Agent to run:
Select a frequency (every day, week, month, or year).
Set a specific time, including timezone (for example, "every day at midnight PST").
Review the next scheduled run time to confirm the schedule is correct.
Save your trigger.
Use Notion triggers
Notion triggers run your Agent based on events in your workspace. You can trigger Agents when:
A comment is added to a page.
A page is added to a database.
A page is updated in a database.
A page is removed from a database.
The Custom Agent is @mentioned in a page or comment.
To add a Notion trigger:
Open your Custom Agent's
Settingsand selectTriggers.Choose a
Notiontrigger type.Specify:
The page or database to watch.
The event (for example, "page created in database").
Any additional filters or conditions if available.
Save.
Use Slack triggers
Slack triggers allow Agents to watch for events in public Slack channels. Agents can be triggered by a message posted to a channel, an emoji reaction added to a message, a thread started in a channel, or a Custom Agent mention in a message.
To add a Slack trigger:
Connect Slack to your Agent during setup if you have not already.
In
Triggers, add aSlacktrigger.Select:
The event type.
The channel to monitor.
Any additional filters or conditions if available.
Save.

Saved or "Later" messages in Slack are not supported.
Custom Agents only use content you explicitly grant them access to for their work. You configure this in each Agent's access settings.
Give a Custom Agent access to content in your workspace
To control what an Agent can see in Notion:
Open the Custom Agent's
Settings.Go to the
Tools and accesssection.Add specific pages or databases the Agent should use as context:
Grant access to Help Center for coverage that includes Notion’s help content.
Grant access to
Pages shared with everyone in Notionif you want broad coverage that includes content throughout the workspace.Add focused pages and databases for targeted workflows (for example, "Customer tickets," "Bugs," "Incidents").
Keep access restricted to "
none" or a small set of pages if you want a narrower scope.

Linking to Notion pages in your Instructions doesn’t add them to the connected Tools and Access.
Allow or block web access
Agents can optionally browse the web when needed. Use web access when your workflow depends on external information. Keep it off for strictly internal workflows or when you want stricter control over sources. To control web access:
Open
Settingsfor your Agent.Find the
Web accesstoggle.Turn web access
onto let the Agent retrieve information from the internet.Turn web access
offto restrict the Agent to Notion and configured apps only.
Give Custom Agents access to Slack
Custom Agents can read and write to Slack through a dedicated integration. Before connecting Slack to your Custom Agent, an admin must first connect the Slack AI connector to your workspace via the Notion AI Settings. Agents can do the following:
Read from public channels.
Post messages, replies, and updates to channels.
React to threads and use information from Slack as context.

Private messages and Slack grid are currently unsupported.
To connect Slack:
When setting up the Agent, follow the prompt to connect Slack.
Make sure the Slack account uses the same email as your Notion account.
Approve the requested scopes in Slack's authorization flow.
Choose which channels the agent can access.
Custom Agents can run on different large language models. This lets you balance speed, cost, and quality. You can adjust the model over time if your workflow changes or you see different performance needs. Supported models include Claude, GPT, and Gemini. Auto is the recommended default.
To choose a model:
Open your agent's
Settings.Go to the
Modelsection.Select a specific model if you want consistent behavior, or select Auto to let Notion choose the best model per request.
Save.
Custom Agents behave like Notion pages when it comes to sharing with others in your workspace, with a few differences.
Share agents with your team
When shared, Agents can appear in the sidebar under an Agents section, in search results, and in any workspace area that lists or references agents.
To share an agent:
Open the Custom Agent page.
Click
Share.Add people, groups, or the entire workspace.
Permission levels
Agents use a simplified set of permission levels:
Full AccessUsers withFull Accesspermissions to an Agent can configure instructions, triggers, access, and models, view and manage activity logs, and run or interact with the Agent.Can EditUsers withCan Editpermissions to an Agent can modify instructions and configuration and review activity.Can View and InteractUsers withCan View and Interactpermissions to an Agent can run the agent and chat with it and view the Settings page (Triggers, Instructions, Tools & Access) in read-only mode. They cannot edit or share the Agent.

Users without access may still trigger or interact with agents configured to respond to events like Slack messages in accessible channels.
Once your Custom Agent is built, it will appear in the sidebar. Every Custom Agent page has three core tabs. Use these tabs together to design, test, and maintain an agent over time.
ChatA private or shared 1:1 conversation area for that specific agent.Useful for testing new instructions, asking the agent to run one-off tasks, and iterating on behavior.
ActivityA log of every agent run visible for users withFull Access.Logs include what triggered the run, actions taken, and any errors or failures.
SettingsThe control center for the agent.The Settings panel includes Agent
Instructions,Triggers, access permissions, and model selection.

Treat configuration as a conversation. Use Custom Agent Chat to test, debug, and iterate on your instructions. Ask the agent to run one-off tasks, provide context on errors, and test different scenarios saving.
Use the Settings tab to edit an agent
Open the
Agentpage.Go to the
Settingstab.Update
Instructions,Triggers, access to pages, databases, and external tools, or model selection.Save and publish your changes.
Use the
Chattab and theActivitytab to verify that the agent behaves as expected after edits.
Undo a change with version history
To restore a previous version of your Custom Agent:
Open the
Agentpage.Access
Version history.Review past versions to see:
Who made changes.
When they were made.
What changed in each version.
Select a version you want to restore.
Confirm to revert the agent to that version.
常见问题
How is this different from Notion Agent in the bottom right corner?
How is this different from Notion Agent in the bottom right corner?
Notion Agent helps you:
Draft, edit, and summarize content.
Answer questions about pages and databases.
Perform one-off tasks while you work.
Custom Agents:
They follow precise instructions you define.
They can run autonomously in the background via triggers and schedules.
They operate only on the pages, databases, and external tools you explicitly grant.
Notion Agent is on-demand, whereas Custom Agents are autonomous.
If a run fails, how can I debug it?
If a run fails, how can I debug it?
To debug a run:
Open the agent page.
Go to the
Activitytab in the agent'sSettingsor from the agent chat view.Find the failing run in the list.
Open it to see:
What triggered the run.
What the agent "thought" and did at each step.
Any error messages or explanations.
If the agent behaved incorrectly:
Adjust its instructions or triggers.
Re-run with updated configuration.
If something looks wrong or suspicious, provide a thumbs-down and a detailed description where available so the team can improve the system.
What Slack app do I need to connect?
What Slack app do I need to connect?
To use Slack with Custom Agents:
Make sure Slack is connected with the same email address you use for Notion.
When prompted during agent setup, connect the Slack app even if you already use Slack elsewhere in Notion.
Approve access and configure which channels the agent can read or write to.
Who can create and see Custom Agents?
Who can create and see Custom Agents?
Custom Agents are available to everyone in the workspace by default.
Enterprise plan Admins can restrict access by going to
Settings>Notion AI>Agents>Control who can create agents.
For each agent:
The creator decides who can access it and at what level (
Full access,Can edit,Can interact).In Slack, anyone in a channel can see messages posted by that channel's agents.
How will I know where this agent is going to run?
How will I know where this agent is going to run?
While configuring an agent, check:
Triggers to see:
Which schedules are active.
Which Notion databases or pages are watched.
Which Slack channels or other apps are connected.
Access / Permissions to see:
Which pages, databases, and external sources the agent can use.
Activity to see:
Where the agent has already run and what it did.
After you publish:
Use the Activity tab and logs to confirm agents are running only where expected.
Review runs regularly to keep behavior aligned with your workflows.
