I Built a Notion AI Agent to Do My Work: An Honest Review
Notion has been moving deeper into AI agents, and I wanted to answer the practical question:
Are Notion’s custom AI agents actually useful, or are they just another expensive AI add-on?
I use Notion a lot already. It is where I store documents, databases, content ideas, and a bunch of working notes. So the pitch is pretty appealing: instead of copying information out of Notion, pasting it into ChatGPT, then pasting the result back into Notion, what if an agent could work directly inside the system?
That is the promise.
So I built one.
The Goal
The agent I wanted was simple: take a rough video idea and turn it into a more complete content brief.
For Stack Snacks, that means things like:
A clearer hook
Possible titles
A video description
Keyword ideas
Relevant news or context
A saved brief inside a Notion database
Maybe a follow-up task in Todoist
Basically, I wanted to see if a Notion agent could act like a mini content teammate.
Not a magic robot. Not a full creative director. Just a helper that can take a messy idea and move it one step closer to something usable.
Building the Agent
Quick clarification first, because Notion has two things called “agents” and the names are confusing.
There is the personal Notion Agent — the assistant in the bubble at the bottom of your screen. It works on demand, only when you prompt it, and it does not burn credits.
Then there are Custom Agents — the ones you configure to run on their own, triggered by schedules or database changes. These are the autonomous ones, and these are the ones that cost credits. That distinction matters a lot once we get to pricing, so keep it in mind.
What I built is a Custom Agent.
I started inside Notion’s agent area, where you can see existing agents and browse the marketplace. One of the more useful pieces I found was a Notion Agent Builder. Instead of writing the whole agent prompt from scratch, I used that builder to help create the first version of the instructions.
The prompt was roughly:
I want to build an agent that helps me take raw video ideas and turn them into a complete video brief.
The builder came back with proposed instructions and a few clarifying questions. From there, I created a new custom agent and started adding the pieces I wanted:
Save new briefs into a Notion database
Research useful keywords
Check for relevant news articles
Pull in live information where possible
Draft an email when finished
Create a related task in Todoist
That was the ideal version.
The actual version took a little more fiddling.
Where It Worked
The core workflow worked better than I expected.
I gave the agent a rough idea for a video about making AI videos with Gemini. It searched the web, started building a brief, and saved output into the database.
The result was not perfect, but it was useful. It pulled together a rough angle, gave some terminology guidance, and created a starting point I could edit. For example, it flagged that I shouldn’t conflate Veo — Google’s established video model — with Gemini Omni, the newer model that’s now replacing Veo inside the Gemini app. Those are genuinely two different things in mid-transition, and getting them mixed up in a video is exactly the kind of small error an AI-savvy audience notices. That is the kind of catch that can save you during planning.
It also successfully created a Todoist task after I connected Todoist through MCP.
That part is interesting. Notion agents can connect to external tools through custom MCP servers, which means the agent does not have to stay trapped inside Notion. It can potentially touch tasks, emails, APIs, and other systems if you wire them up correctly.
That is where the product starts to make more sense.
If your team’s work already lives in Notion, and you want an agent to operate on that shared context, this could become useful fast.
Where It Got Messy
The messy parts are exactly what you should expect if you have built any agent workflow before.
The agent created multiple database pages when I only wanted one.
It tried to draft an email, but I had not clearly told it who to send the email to, so that failed. Honestly, I was glad it stopped. That is better than an agent confidently sending something to the wrong person.
The Todoist MCP connection also had some issues before it worked. It eventually created the task, but it was not a perfectly smooth setup.
This is the real lesson: agents are not “set it and forget it” on the first try.
You have to watch what they do, tighten the instructions, remove risky actions, and build in constraints. In my case, I removed the email step because it added more risk and confusion than value for this specific workflow.
That is probably the right way to think about these tools:
Start with one safe action. Make it reliable. Then add more.
The Credit Problem
The biggest downside is cost — and this is the part where the details matter, because they changed recently.
First, Custom Agents are a Business/Enterprise feature. If you are on Free or Plus, you do not have them at all. Practically, that means the entry point is the Business plan at $20/user/month before you have run a single agent.
On top of that, Custom Agents run on Notion Credits, which are a separate add-on: $10 per 1,000 credits, pooled across your workspace, reset every month, no rollover. Notion ran a free exploration period through May 3, 2026, but billing started May 4 — so there is no free ride left.
How fast do credits burn? Each run costs anywhere from a fraction of a credit to a few dozen, depending on how much the agent reads, how many tools it touches, and which model it uses. For moderate use, most estimates land around $20–50/month on top of your Business seat.
That changes how I think about using it.
If I am already paying for Notion, ChatGPT, Claude, Gemini, or other AI tools, I do not want to accidentally create another $30 or $40 per month workflow unless it is clearly saving time.
The model picker helps. You can drop to a cheaper model for simpler tasks instead of running everything on the most expensive one. That is good. But it still means you need to pay attention to usage.
For a solo creator, I would not build twenty Notion agents right away. I would build one tight workflow and see if it actually earns its keep.
Who It’s For (and Who Should Skip It)
Notion Agents make the most sense for small teams or businesses already running work through Notion.
If you have shared databases, docs, project notes, meeting notes, content calendars, or client information in Notion, an agent sitting inside that context could be genuinely useful. Good use cases:
Turning meeting notes into project tasks
Summarizing client research into a one-page brief
Creating content briefs from raw ideas
Generating weekly updates from team databases
Checking a knowledge base before answering internal questions
The key is that Notion already has the data. If the agent has to leave Notion, search around, talk to other apps, and then come back, the workflow gets more fragile. But if the work is already sitting in Notion, the value is much clearer.
If you are a solo user who only uses Notion as a personal notes app, this may be overkill — especially now that the free period is over. You can get a lot of the same value by using Notion’s MCP inside another AI tool, or by copying a page into ChatGPT or Claude when you need help. Not as elegant, but cheaper and simpler.
The real risk is building a complicated agent because it feels cool, not because it saves you time. I would avoid workflows that:
Send emails automatically before you trust the system
Create lots of database entries without a review step
Touch multiple external tools at once
Use expensive models for simple formatting tasks
Run repeatedly without clear limits
Those are the places where small mistakes turn into annoying cleanup.
The Lean Version I’d Actually Build
If I started over, I would resist every urge to make it clever. Here is the actual instruction I would give the agent builder:
You help me turn a rough video idea into a single content brief.
When I give you an idea:
1. Ask me 2–3 clarifying questions max (audience, angle, what I already know).
2. Do light web research to check terminology and find one or two
relevant, current references.
3. Create ONE new page in the [Content Briefs] database with these fields:
- Hook (one sentence)
- 3 working titles
- Draft description (3–4 sentences)
- 5 keyword ideas
- Notes / things to fact-check
4. Stop there. Do not send emails. Do not create tasks in other tools yet.
Use a cheaper model unless I tell you the research quality isn't good enough.
That is it. One input, one output, one place. No external side effects until the brief format is reliable.
Once that is boring and dependable, then I would add the Todoist task. Then maybe a draft email — but only once I trust it. Start with one safe action, make it reliable, then earn the next one.
Set a monthly credit cap while you are at it, so a runaway agent cannot quietly drain your balance.
My Take
I like the direction. Working directly inside Notion is genuinely useful, the agent builder lowers the barrier, and MCP support means these agents do not have to stay trapped inside Notion.
But it is not a must-use for everyone. For solo creators, it is a “test one workflow with a tight credit cap” product. For small teams already running work through Notion, it is more compelling — the data is already there, so the agent has something real to act on.
Either way, the bar is not “can it do something impressive once?”
It is: can it quietly make your normal workflow easier every week?
Build one boring agent. Watch what breaks. That will tell you more than any demo.