What the agent does
Notion's remote MCP server, https://mcp.notion.com/mcp, is the Notion entry in the Rush connector catalog; it can search, create and update pages and databases. Connect it once with POST /me/connections {"type": "mcp", "name": "notion", "url": "https://mcp.notion.com/mcp", "auth": {"mode": "oauth"}} and approve the Notion sign-in. The agent can then read the pages that account can open.
The agent searches the workspace for pages and database rows last edited in the past 7 days, and keeps the ones that are project pages or meeting notes: pages under the projects area, rows in the projects or tasks database, and pages whose title or template marks them as notes. For each project it reads the page, the task database rows linked to it whose status changed that week, and any meeting notes that mention it.
From that it writes four things per project. Progress is what moved: tasks that changed status, milestones the page marks as reached. Risks are what people wrote down as blocked, late or uncertain. Decisions are statements in the notes that settle a question ("we will ship without SSO"). Open questions are the ones raised and not answered. Every line links to the page or note it came from, so nobody has to trust the summary.
The only write is the new page: Status <date> created under the Status page. The prompt says to change no existing page, so the agent edits no project page, task or note, and adds no comment.
Start it with one API call
POST https://api.prix.dev/o/{org}/sessions with this body:
{
"agent": "claude",
"input": "Use the Notion connection to find project pages, project and task database rows, and meeting notes edited in the last 7 days. Create one new page titled Status followed by today's date under the page named Status. In it, for each project: progress (tasks that changed status, milestones reached), risks, decisions made and open questions, each line linking to the page or note it came from. End with a list of the pages you read. Change no existing page, row or comment.",
"connections": [
"notion"
]
}- Get an API key. In the console, open Settings, then API keys, and create a key for your org. Send it in the Authorization header as a Bearer token.
- Send the request. POST the body in request.json to https://api.prix.dev/o/{org}/sessions, with your repository as the resources URL. The run starts in its own cloud sandbox.
- Read what came back. Follow the run on its live stream or wait for the run.completed webhook, then read the result and its trajectory.
What comes back
What comes back is a new Notion page, Status <date> under Status, with one section per project and four short lists in each, every line a link to its source. The session's result names the page, and the end of the page lists every page the agent read, so it is clear what was in scope.
The session's transcript records each search and page read and the one page create, so it is easy to confirm that nothing else was touched. Before sending the page around, a lead reads the decisions list closely: a decision is the agent's reading of a sentence in a note, and one that was only proposed should be moved to open questions.
Run it on every Friday at noon
An automation with a schedule trigger in a Project creates the page every Friday, with a cron such as 0 12 * * 5 and your timezone. Each run reads only that week's edits, so the status pages form a dated series under Status that anyone can scroll back through.
With a webhook URL on the key, Rush POSTs run.completed when the turn ends. Your server can read the session's result for the new page's link and post it to the team channel or email it to stakeholders.
The use case this job follows, with its automation and trigger: Produce a report or file, no repo.
Why run it on Rush?
Status updates are copied from the pages where the work is already written down, by someone who has to open each page and remember what changed. The agent does the reading through the connection from its own sandbox, and because every line links back, the summary never drifts from the source.
Its one write is a new page, and the session's transcript shows every read and that single create, which is what makes it safe to point at a shared workspace. Separate teams or workspaces can each have their rollup run at the same time, up to the key's concurrent run limit.
Frequently asked questions
Will it edit our project pages?
No. The prompt allows one write, the new status page, and says to change no existing page, row or comment. The transcript lists every tool call, so you can check.
Our workspace is organized differently. Does it still work?
Tell it in the prompt where projects and notes live, such as the database name or the parent page. Without that it finds them by what was edited and how the pages are titled, and lists what it read at the end so you can correct it.
Can it see private pages?
Only the pages the connected Notion account can open. Pages that account cannot see never appear in its search results, which is why the page ends with the list of pages it did read.
Can it also post the status to Slack?
Yes. Name your Slack sign-in on the run as well and add a step to the prompt; Slack reaches the agent as the slack CLI signed in as you. Or let your webhook handler post the link.