Notion AI Autofill is configured on a database property. It is not Excel’s pattern-fill handle, and you do not need to type an example in the first cell and drag it down. Use it to produce a summary, classification, translation or extracted information for each record, then check the actual saved values.
Start on a copy or a small test database. Keep the original text and use a separate output property so a bad fill does not replace your only source.
Choose Basic or Custom Agent Autofill
Basic Autofill handles straightforward work using the current row/page’s content. It does not search all workspace pages or browse the web. Custom Agent Autofill can handle more complex instructions and, when enabled, workspace or web search. Its trigger options can also include a schedule. See Notion’s Autofill guide.
Basic Autofill is included on Business and Enterprise without using Notion credits. Custom Agent Autofill uses credits. Do not purchase an assumed $10-per-person legacy add-on to follow this guide; verify the workspace’s current plan and credit settings. Notion’s credit documentation explains the distinction.
Set Up a Basic Fill on a Property
- Open the database and choose a suitable output property, such as a text summary.
- Click the property’s name, then choose AI Autofill or Set up AI Autofill.
- Select Basic and choose the task, such as Summary, Translate, Key info or Custom autofill.
- Choose when it runs. Begin with manual execution for your test rather than immediately enabling every page-creation or edit trigger.
- Save the configuration, run it on a small sample, and inspect the resulting property values alongside each source page.
A useful original test instruction is: “Summarize this record’s notes in one sentence. Keep any stated deadline exactly as written. If there is no deadline, do not invent one.” Include enough source material in each record; one example row does not supply factual content for all other rows.
Use Custom Agent Autofill for Broader Context
Choose Custom Agent in the property’s Autofill setup when the task needs richer context or multiple steps. State which property to write, what source to use, how to handle missing information and whether existing values may be changed. Enable workspace or web search only if the task needs it.
For example: “For records whose Review summary is empty, summarize the attached notes into Review summary. Preserve all other properties. If the source is insufficient, say ‘Needs review’ instead of guessing.” Use only an approved source scope.
Run one representative record, inspect its changes and credit usage, then expand gradually. An instruction to fill only empty cells is a constraint to test, not a substitute for backups or verification. Automatic runs can update data without a universal per-cell preview.
Troubleshoot Missing, Repetitive or Incorrect Values
- Nothing fills: confirm Autofill is enabled on the intended property, that the record contains usable source information, and that the configured trigger actually ran.
- It cannot see another page or website: Basic only uses the current row/page. A task requiring broader search needs the appropriate Custom Agent setup, source access and search permission.
- Every result looks the same: inspect the records’ individual content and narrow the prompt. A more elaborate example cannot compensate for missing facts.
- Important values changed: stop the trigger, inspect the affected records and restore from your retained copy or available history. Do not rerun the whole database before understanding the change.
For exact arithmetic, fixed date logic or related-record aggregation, use a formula or rollup where appropriate rather than asking a language model to improvise values. Review the property types before changing a production database.
Do not rely on a claimed two-second completion time or a sparkle icon as evidence of correctness. Check names, dates, categories and source alignment before using generated fields in reports or downstream automation.
Official documentation checked: October 14, 2026.