Notion AI Autofill can run when a database page is created; it is not limited to manually filling one selected cell. If a new row remains empty, inspect the destination property’s Autofill configuration, run timing, source content, and workspace access. Creating an empty page is not enough to generate a meaningful summary.
Official documentation checked October 14, 2026. Notion distinguishes Basic and Custom Agent Autofill. Actual controls and access should be checked in your workspace; no customer database was modified for this article.
Why Autofill May Leave a New Row Empty
A database row is a page. The AI property needs an enabled configuration and an appropriate run event. A property set to manual execution will not behave like one set to page creation. If content is entered after the creation event, the earlier run may have little material to use. Check whether page edits is a better timing for a database where people write notes after creating the row.
Notion’s current documentation says Basic Autofill uses the content of the specific row/page; it does not browse the web or automatically learn the desired answer from every other row. Custom Agent Autofill can use workspace or web search when enabled. Do not solve a missing page summary by granting broad workspace access without a need for it.
Basic Autofill is included in Business and Enterprise plans. Custom Agent Autofill uses credits. If the property does not offer AI Autofill, check your supported property configuration and workspace entitlement with the owner. Do not convert a formula, rollup, or relation property into text as a first troubleshooting step; that can change how the database works.
Set Up and Test Autofill for Newly Created Pages
- Choose a test item. Use non-sensitive sample content in the same database. Preserve any existing manual output before changing an AI configuration.
- Inspect the destination property. Click its name and open AI Autofill or Set up AI Autofill if offered. This is a property-level configuration, not a general Ctrl+J/Cmd+J cell shortcut.
- Choose the appropriate mode. Basic suits page summaries or extracting information already present on that page. Custom Agent suits a task needing richer instructions or approved search sources.
- Specify the output. Select the desired task or enter clear instructions. For a test summary, name the page content to summarize and the intended length rather than relying on a vague column heading.
- Check when it runs. Choose page creation for items whose input is available at creation, or page edits for items that receive their source content later. Save the configuration and inspect the actual options offered by your workspace.
- Create and review a test page. Use your normal database New control and provide the relevant input. Inspect the generated property; compare it with the source rather than assuming a populated cell is correct.
If a manual-run control is offered, use it on the test item to separate a content/configuration problem from an event-timing problem. Then repeat the creation test. No fixed completion time is guaranteed here, and web, desktop, and mobile interfaces need not present the controls identically.
For a workflow that should preserve human-written output, specify the intended overwrite behavior in the instructions and test it with both blank and already filled outputs. For Custom Agent Autofill, Notion explicitly suggests an empty-cell condition when only blank cells should be filled. Treat the observed behavior as the verification, not the wording of the prompt alone.
If a New Page Still Does Not Fill
- Nothing runs: reopen the destination property’s setup and verify it is enabled with the intended timing. Check credit/access availability for the selected mode.
- The output is empty or unhelpful: add relevant source text to that same test page and rerun through the available control or selected edit event. Data in unrelated rows is not a substitute for the page’s input.
- It works manually but not on creation: compare how the test page was created and when its input became available. Do not claim that templates, imports, integrations, and direct creation have identical behavior without testing your path.
- It needs information from another page: Basic does not perform workspace search. Consider Custom Agent only if that source is required and permitted; confirm its access instead of making pages public.
- The generated value is wrong: tighten the instructions, inspect the source page, and test ambiguous or missing information. Keep a human review step for consequential outputs.
For persistent failures, provide support with the property mode, run timing, plan, platform/version, creation method, and a non-sensitive reproduction. Use the support link in the official Autofill help page. Avoid deleting the database or recreating all its properties to fix one failing column.
Autofill and Database Automation Serve Different Tasks
| Task | Feature | What to verify |
|---|---|---|
| Generate a summary from the new page | Basic Autofill | AI property, source content, and page-create/edit timing. |
| Use richer instructions or approved search | Custom Agent Autofill | Search scope, run timing, credits, and output quality. |
| Set a fixed value or assign an owner | Database automation | A supported trigger and action. |
Database automations have their own Page added and Property edited triggers and supported actions. Their documentation does not establish a universal “Run AI Autofill” action. You do not need a third-party integration merely to make an AI property run on page creation. Configure the native feature first, test the actual creation path, and retain only the behavior you have verified.