The client status report that drafts itself by Friday

Why now

• Notion Custom Agents run on a schedule and on database changes. You can give one agent a weekly recurring trigger and a "property updated in database" trigger, so it drafts on Friday and only posts once you've approved. Custom Agents are on Notion's Business and Enterprise plans. (Notion help)
• Notion published a guide for almost exactly this job. It builds an agent that drafts a weekly project update into a Weekly Updates database and posts a Slack summary when the status changes to Published. This drop points that pattern at client work and feeds it your call notes. (Notion guide)
• Granola can send each call's notes into a Notion database. On the Business plan, one click from a note files it in a database Granola creates for you. (Granola docs)

The report stays a draft until a person reads it. Nothing goes to the client without you.

Who it's for

The person on the account who spends Friday afternoon rebuilding the week from memory, three call recaps and a tracker. If you already ran Drop 002, this is its weekly, client-facing sibling. Drop 002 turns each day's calls into internal tickets. This one turns the week's calls plus the tracker into the update your client reads.

What you get

• Every Friday, a new page in a Weekly Updates database for each client, drafted from that week's call notes and the client's project database.
• The same six sections every week: Status, Done this week, Open items, Blockers and risks, Next milestones and What we need from you.
• When you set the page's status to Published, a 2–3 line summary with a link posts to your internal Slack channel for the account.
• You paste the final version into your own email or Slack Connect thread to the client.

You'll need

Setup

1. Connect Granola to Notion (Granola, 5 min)

In Granola: Settings → Connectors → Notion → Connect Notion. In the Notion authorization screen choose Use a template provided by the developer. Granola creates its own notes database in your workspace. You can add columns to it and sort it, but you can't point Granola at a different database.

Add one column to that database yourself: Client (a select or relation to your clients). It's how the agent knows which calls belong to which account.

2. Send each client call to Notion (Granola, 10 seconds per call)

After a client call, open the note, check the summary is right, and use the ⋯ menu → Notion to share it. Then set the Client column on the new row in Notion.

This is a click per call on purpose. Granola's Notion integration doesn't sync automatically or in bulk. If you'd rather not click, Granola's Zapier trigger Note Added to Granola Folder can create the Notion row for you whenever you drop a note into a client folder (Zapier also needs Granola Business).

3. Make the Weekly Updates database (Notion, 10 min)

Create a database called Weekly Updates with these properties:

• Client (same select or relation as above)
• Week of (date)
• Status (select: Draft, Published)
• Owner (person)

Make sure each client has a project database or view the agent can read: tasks with owner, due date and status is enough.

4. Build the agent (Notion, 20 min)

In the sidebar open Agents → New agent. Paste the brief below, @-mention the Granola notes database, your project database and the Weekly Updates database, and answer the agent's follow-up questions. It drafts its own Instructions, Triggers and Tools and access. Check each one before you save.

You draft weekly client status reports. You never contact clients.

Every Friday at 1pm (our timezone), for each active client:
1. Read that client's call notes from the Granola notes database dated Monday-Friday this week,
   and that client's tasks in the project database.
2. Create one page in Weekly Updates with Client, Week of (this Monday), Owner (the account lead)
   and Status = Draft.
3. Write the page with exactly these sections:
   - Status: one line, on track / at risk / off track, and why.
   - Done this week: finished work, with dates where the tracker has them.
   - Open items: what's in flight, with owner and due date.
   - Blockers and risks: anything late, waiting or unclear. Say what's needed to clear it.
   - Next milestones: the next two or three dates from the tracker.
   - What we need from you: decisions, approvals or assets the client owes us, from the calls.
4. Only use facts from the notes and the tracker. If something is unclear or conflicting,
   add it under "Questions for the lead" at the bottom instead of guessing.
5. Leave out internal-only remarks from calls (pricing, staffing, opinions about the client).

When a Weekly Updates page's Status changes to Published:
post a 2-3 line summary with a link to the page in that client's internal Slack channel.
Don't post anything for pages that are still Draft.

5. Set the two triggers and Slack access (Notion, 10 min)

In the agent's Settings → Triggers:

• Add a Recurring trigger: weekly, Friday, 1:00 PM, your timezone.
• Add a Notion trigger: property updated in database, database Weekly Updates, filtered to Status is Published.

In Tools and access, give read access to the Granola notes database and project databases, write access to Weekly Updates, and connect Slack with write access to each client's internal channel. A Slack workspace admin has to connect Slack to Notion first, and your Slack account needs the same email as your Notion account.

6. Edit, publish, send (you, 10 min every Friday)

Read the draft. Fix what's wrong and answer any "Questions for the lead". Delete anything the client shouldn't see. Set Status to Published, which posts the internal Slack summary. Then copy the page into your email or Slack Connect thread to the client and send it yourself.

For the first two Fridays, ask the agent in chat to generate the draft early so you can compare it with the update you would have written.

Time to set up

About an hour (an estimate, not timed), assuming your tracker already lives in Notion. Add a few minutes per client if you need to tag past call notes.

Cost

• Minimum: Granola Business $14/user/mo plus Notion Business $20/member/mo, with Slack Free. Custom Agents are free to try, then $10 per 1,000 monthly Notion credits.
• What one run costs: we couldn't find this. Every trigger uses credits even when the agent does nothing, and the number depends on how many notes and tasks it reads. Check the Notion credits dashboard after the first two Fridays.
• Optional: Zapier, if you want notes filed in Notion automatically (see step 2).

Prices are list prices as checked on Oct 19–20, 2026.

Gotchas

• Notes only arrive if someone shares them. No click (or no Zap), no notes, and the report will look thin. If a draft seems light, check that this week's calls are in the database before blaming the agent.
• Keep the trigger narrow. "Status is Published" is a high-signal trigger. Triggering on any edit to Weekly Updates would run the agent, and spend credits, every time you fix a typo.
• Credits are per run, not per useful run. Notion's own best-practice page says to start weekly and scale up only once the output is reliable.
• Internal talk leaks easily. Calls include things clients shouldn't read. The brief tells the agent to leave them out, but your read-through on Friday is the real filter.
• Renamed properties break things quietly. If you rename a Status option or a column, run a test before the next Friday.

Remix

• Skip Granola: Notion's own AI Meeting Notes (Business plan) can be the source, and Custom Agents can trigger when an AI Meeting Note is finished.
• Monday kickoff: add a second recurring trigger on Monday morning that drafts the week's plan from the same tracker.
• Internal version too: have the agent write a second, franker page for your team with the internal-only notes it left out of the client one.

Freshness log

• Oct 20, 2026: First published. Desk-checked against Notion's Custom Agents help page, its project-updates guide and pricing page, Granola's Notion and Zapier help pages and pricing page, and Slack's pricing page.

Last verified: Oct 2026 (desk-checked, not run end-to-end). We checked every step, setting and price against the vendors' current docs. We have not yet run this chain live. If a step doesn't match what you see, reply and tell us. It'll be fixed in the next refresh.