Stop doing the same work twice. Let an agent handle it while you focus on what actually needs you.
You already use Notion AI to ask questions, draft content, and summarize pages. Custom Agents take that further — they handle recurring work on their own, without you asking every time. Status updates, Slack triage, meeting recaps, deadline reminders — if it follows a pattern, an agent can run it.
What teams typically save:
| Task | Manual time | With an agent |
|---|---|---|
| Weekly status report (pulling from 3 databases) | 45–60 min/week | Runs automatically every Monday |
| Triaging incoming Slack questions against your wiki | 15–30 min per question | Instant reply, escalates what it can’t answer |
| Meeting recap + action items to Slack | 20 min per meeting | Posted within minutes of notes being added |
| Chasing content deadlines across the team | 30 min/day of Slack messages | Daily digest posted at 9am |
This guide walks you through how to identify what to automate, how to set it up properly, and how to avoid the common mistakes that waste credits or produce bad output.
Before diving in, here’s what the key terms mean in practice:
| Term | What it means |
|---|---|
| Custom Agent | A background worker in Notion that does a specific job automatically — like having a team member who only does one task, perfectly, every time. |
| Trigger | The event that tells the agent to start working. Could be “a new bug was logged,” “someone @mentioned you in Slack,” or “it’s Monday at 9am.” |
| Schedule | A type of trigger based on time — “every day at 9am” or “every Friday at 4pm.” |
| Skill | A saved prompt (stored as a Notion page) that you or an agent can reuse. Like a recipe card for a specific AI task — “turn these notes into action items” or “rewrite this for an executive audience.” |
| Instructions | The rules that tell an agent how to behave — what tone to use, what to reference, and what format to follow. Your personal Notion Agent has its own instructions (in Settings). Each Custom Agent has separate instructions that you write when you create it. |
| Credits | What Custom Agents consume each time they run. More complex tasks (more data, more steps) use more credits. Credits reset monthly and don't roll over. Your regular Notion AI chat is included in your plan at no extra cost. |
| Scope | What the agent is allowed to look at — which specific pages, databases, or Slack channels. Tighter scope = faster runs and fewer credits. |
| Edge case | What should happen when things aren’t normal — no data to report, a question the agent can’t answer, a bug it can’t classify. |
Not every task needs an agent. Use this decision flow to check whether a Custom Agent is the right fit.
| ✅ Good candidates | ❌ Not ideal (yet) |
|---|---|
| Weekly status reports from project databases | One-time workspace reorganisation |
| Triaging incoming Slack support requests | Complex strategic analysis |
| Compiling meeting action items | Tasks requiring subjective judgement |
| Answering FAQs in a Slack channel | Processes that change shape every time |
| Daily content deadline reminders | Work that requires reading attached files |
<aside> <img src="/icons/light-bulb_blue.svg" alt="/icons/light-bulb_blue.svg" width="40px" />
Start with one. Don't try to automate five things at once. Pick the task that's most repetitive and easiest to verify, get it running well, then move to the next one.
</aside>