How to Set Up a Notion Custom Agent: Three Ways to Create One, Four Trigger Types, and What to Throttle Before Credits Start on 15 October

Notion’s Custom Agents are not the Notion Agent in your sidebar. The help centre is explicit: Custom Agents are designed to run automatically in the background based on triggers and schedules. You configure them once and they keep going.

And from 15 October 2026 they start consuming Notion credits (see the price and the deadline), which means how well you configure them turns into how much they cost. Here is the setup flow from the official documentation, verified 2026-09-08.

1. What they can do (official definition)

Once configured, per the help centre, an agent can:

• Read from Notion pages and databases, and from certain connected apps
• Run on recurring triggers and workspace events
• Take actions such as posting reports, filing bugs, updating records or sending messages

The intended use is recurring, manual workflows. On eligibility the help article states you must be on the Business or Enterprise plan (note: the pricing page’s comparison table words this differently — see the pricing piece above). Building and editing is desktop or web only.

2. Three ways to create one — pick the right one

1. Describe it in chat (fastest). Say what you want in natural language, let Notion AI draft the instructions, triggers and access, then review, iterate, save.
2. From a template. Start from an official Custom Agent template and adapt it. Best route for a first agent.
3. Manually. Define behaviour and scope of work yourself, then set triggers, access and model.

Notion’s own advice on instructions: state what the agent should do, how it should behave and what work it should handle, with examples where you have them. This is prompt writing by another name — vague instructions get you actions on the wrong pages.

3. Four trigger types (this is where cost is decided)

1. Recurring schedules

• Daily, weekly, monthly, weekends only, and more
• Path: the agent’s Settings → Triggers, then a specific time including timezone (e.g. “every day at midnight PST”)
• Check the next scheduled run before saving — the documentation calls this out explicitly

2. Notion events

• Page created in a database, page updated, page removed from a database, an AI Meeting Note finished
• Some events accept filters: matching property values, or limiting runs to a particular database view

3. Slack events

• New message in a channel, an emoji reaction added, the agent @-mentioned
• Prerequisite: to trigger by @-mention, your Slack workspace admin must first allow members to create these integrations
• Keyword or phrase filters are available to reduce noise in high-traffic channels

4. Combinations

• Multiple trigger types can be combined on one agent. Convenient — and the easiest way to lose control of credit spend.

4. Access scope: do not start with the whole workspace

Control what the agent can see under Settings → Tools and access, adding the specific content it needs.

Our own recommendation: give version one a single database. Agent failures are rarely “it could not do the task”; they are “it acted somewhere it should not have”. A small scope keeps mistakes cheap. Widen it once behaviour is stable.

5. Throttling to do before 15 October

Once the free window closes, trigger count equals spend. Three adjustments available today:

1. Add keyword filters to any Slack trigger that could fire on every message. Notion frames this as noise reduction; after the 15th it is also credit control.
2. Prefer weekly over daily. Reporting agents get set to daily by reflex, and nobody reads them daily.
3. Turn off the typing indicator where it is not wanted. Slack-triggered agents show one, and the documentation notes this does not always mean the agent will reply; it can be switched off in trigger settings.

6. Pre-launch checklist

• Do the instructions say what not to do? (Given only goals, agents expand their own remit.)
• Is the access scope the smallest one that works?
• Does the trigger frequency match how often the work is genuinely needed?
• Does the next run time look right — is the timezone correct?
• Do Slack triggers have keyword filters?
• Roughly how many times a month will this fire after 15 October? (Credits per run are unpublished, so log the count now; the cost conversion comes later.)

Plan prices and data retention terms: Notion AI pricing.

Sources read directly on 2026-09-08: the Custom Agents help article and the official pricing page. “You must be on Notion’s Business or Enterprise Plan”, the 15 October credit start and the US$10 per 1,000 credits rate are official wording; credits consumed per run are not published and remain unverified. The recommendations in sections 4 and 5 are ours, not vendor guidance.