Blog · · Benatar Brands
How to get a Friday project recap from Notion with AI
If your projects live in a Notion board, the information for a weekly status update is already there. What is missing is the half hour it takes to click through every card, remember what it looked like on Monday, and write it up. An AI assistant connected to Notion can do that reading on Friday afternoon and leave you a recap you can check in two minutes.
This post shows how to set it up with Grok Bot and the Notion connector, and how to keep it from changing anything.
What the assistant can actually do
With the Notion connector added, Grok Bot can:
- Query a database, such as a task or project board, with filters on status, owner and dates, or run one of your saved views
- List what changed in a page or database between two times and who changed it
- Read the comments and discussions on a page
- Search your workspace and open a page to read it
The same connector can also write. It can create and edit pages, add comments and delete pages. Notion's own guide to Notion MCP puts it plainly: connected tools act with your full Notion permissions and can access everything you can access. For a recap, none of that is needed. Tell the assistant, in the routine's instructions, that it may read only and must not create, edit, comment on or delete anything. If your workspace allows it, connect with an account that can see only the boards you want summarized.
Step 1: Point it at one board
Start with the board that matters most this quarter, not the whole workspace. Give the assistant the link and ask it to read the board's properties and describe them back to you: which property is status, which is owner, which is the due date. Correct anything it gets wrong now, so the recap does not have to guess every week.
If you already have a saved view that shows only active work, use it. Notion's help page on views, filters and sorts explains how to build one with filters on any property. Pointing the assistant at a view you control keeps its scope the same as what you look at yourself.
Step 2: Define the recap
Ask for the same five sections every week, in this order:
- Done this week: cards that moved to a done status since last Friday
- Moved: cards whose status, owner or due date changed, with before and after
- Overdue: open cards with a due date in the past
- Stuck: open cards that nobody has edited in two weeks or more
- Open questions: unresolved comments on active cards, quoted, with the card they are on
Two weeks is an example threshold, not a rule. Pick a number that fits how fast your projects move.
Add one instruction that keeps the recap honest: "Only report what the board shows. If a section is empty, say so. Do not guess why something is late."
Step 3: Get the time window right
The "moved" section depends on page history. Notion's help article on version history says you can view past versions going back 7 days on the Free plan, 30 days on Plus, 90 days on Business and with no limit on Enterprise. A one-week window fits inside the shortest of those. If you skip a week, ask for the "done" and "overdue" sections only, since those come from the board's current state rather than its history.
The connector lists each changed card once, with how it looked at the start and at the end of the window, so the recap shows the net change for the week rather than every edit in between.
Step 4: Schedule it
Grok Bot can run this as a scheduled routine, for example every Friday at 3 PM in your time zone. It reads the board, writes the five sections and leaves the recap in your chat. Nothing is posted in Notion and nothing is sent to your team. If you want to share it, copy the parts you want into your own update.
An example
Picture a small landscaping company that runs its spring job list in Notion: one card per client job, with a status, a crew lead and a start date. On Friday the recap might show three jobs moved to done, one job whose start date slipped a week, two jobs with no crew lead assigned, and a comment from the office manager asking whether a client approved the planting plan. The owner reads it, makes two phone calls, and assigns the crew leads in Notion themselves. The assistant did the reading; the owner did the deciding.
Limits
The recap is only as good as the board. If people update cards late, or keep status in their heads, the recap will be wrong in the same way the board is. Changes inside inline databases may need their own link, and comments are read separately from page changes, so check the first few recaps against the board before relying on them.
If your week also starts with meetings, our calendar meeting prep brief pairs well with this one.
Setting up read-only routines like this is part of our embedded AI partnership. Book a free session and we will set up your first Friday recap with you.
Related service: embedded AI partnership.
Get our notes on AI and how businesses run in your inbox: subscribe to The Beyond Brief.