Use Claude Code + Notion to Build an AI Agent That Handles Repetitive Knowledge Work Requests

A written playbook and an agent that drafts requests on its own

On Thursday, we broke down why Microsoft just put $2.5 billion into embedding engineers inside customer teams, and why AWS put $1 billion into that same kind of offering three days earlier. Both companies came to the same conclusion that the rest of us have over the past 18 months: Having the tool isn’t enough. Someone has to redesign the task itself around it, using your team’s data and rules, before it can help.

Today, you’re going to be that someone. You’re going to build the thing Microsoft and AWS charge millions for, at your own desk.

What you’re building

By the end of this build, you’ll have a working, autonomous agent that watches your team’s support intake queue in Notion, reads a written playbook for how your team already answers common questions, drafts a response in your team’s voice, and hands that draft to a person for approval before anything goes out.

It checks the queue every 30 minutes on a set schedule; no one has to open a chat window and trigger it. I set mine to check only during work hours, since a person still needs to be around to review what it drafts, but you can widen that window to whatever hours your team covers.

I ran this against my own company’s queue, and every screenshot in this piece comes from that run. My team gets a handful of the same questions from new users, over and over. That’s the type of request this build is for.

You’ll use Claude Code to run the agent, and Notion to store incoming requests and the playbook that agent follows. If your team tracks requests somewhere else, the same setup works with whatever you’re already using.