To have Notion AI prepare a status update every week without someone opening a prompt, use a scheduled Custom Agent. A reminder merely tells a person to do something; it does not execute an AI task. Notion’s reminder documentation also says recurring reminders are not currently supported.
The setup below creates a draft in a reports database. Keep distribution separate until you have checked that the source selection, dates and summaries are reliable.
Prepare the Source Data and Reporting Rules
Custom Agents require a Business or Enterprise workspace and are configured on desktop or web. They use Notion credits; included access to ordinary Notion AI is not a promise of unlimited background runs.
Choose one project database for the first version. Useful fields include task name, owner, status, due date and completion date. Create a separate Updates database with reporting-period dates and a Draft/Reviewed status. The exact property names are your design choices, not mandatory Notion fields.
Define the report before scheduling it. “Completed last week” needs a completion date or another reliable completion record. A due date means when work was expected, not when it finished. A last-edited timestamp can reflect an unrelated spelling correction. If your database does not record the required event, report the current snapshot and label the historical information unavailable.
Create a Focused Reporting Agent
Open Agents in the sidebar and create an agent. Describe the job and inspect its proposed instructions. Under Settings → Tools and access, connect the specific source database and the destination for reports. Merely linking a page in the instructions does not grant access.
A starting instruction you can adapt is:
Prepare a draft project update in Updates. Use Tasks as the source. Cover the previous Monday 00:00 up to, but not including, this Monday 00:00 in Europe/London. Identify completed items using Completed date. Separately list current blockers and overdue unfinished items as of the run time. Include source-page links. Do not invent owners, dates or progress. State missing evidence. Do not modify Tasks or send messages. If a report already exists for this period, stop and report that instead of creating a duplicate.
Replace the database names, timezone and period with your actual choices. These are instructions to test, not a guaranteed transaction or permission boundary. Limit the agent’s access independently, and use a restricted or sanitized reporting source when the original database contains information it should not read.
Schedule, Test and Publish the Workflow
In the agent’s Settings → Triggers, add a Recurring trigger. Choose the frequency, time and timezone, then check the next scheduled run. Save the configuration and test with a small, non-sensitive source before enabling unattended work.
Check a sample run in the agent’s chat and Activity view. Compare each completed task with its recorded completion date. Confirm that an empty week produces an honest “no matching items” report, not recycled text. Test a second run for the same period to see whether it creates a duplicate.
Save and publish the tested configuration. Publishing the agent enables its configured workflow; it is different from approving a generated report for readers. Notion’s project reporting guide demonstrates drafting updates separately from subsequent distribution. Initially, leave external sending disconnected and have a person review the draft.
Keep Recurring Updates Accurate and Affordable
- No report appeared: inspect the active trigger, timezone, publication state, source access and Activity history. Check credit availability before repeatedly rerunning.
- The wrong week was included: use explicit period boundaries and verify the relevant date property. Do not assume a view labelled “last week” means the same period as a prompt.
- Sensitive content appeared: hiding a column is not access control. Restrict the connected source or use an approved reporting copy.
- Costs rose: compare actual credits per run and run frequency. Narrow the source and remove unnecessary actions instead of assuming a fixed price per report.
Assign an owner to review failures and changes to database fields. Start with one weekly draft; add extra databases or distribution channels only after that workflow has been checked.
Official documentation checked: October 14, 2026.