Automated OneNote Client Notebook Setup
Whenever a new client is added, WebRun opens OneNote, creates their notebook using your standard structure, adds every section and starter page you use on an account, posts the link to Slack for the account lead, and records the setup in Notion so nothing is built twice.
How do I set up the same OneNote notebook for every new client?
WebRun builds a full OneNote notebook the moment a new client is added. It creates the sections and starter pages you use on every account, posts the link to Slack for the account lead, and logs the new client in Notion, so notes land in the same place from the first meeting.
- Every client notebook is built before the first meeting
- Notes land in the same section for every account, not wherever someone put them
- A re-added contact never triggers a duplicate notebook
Built for account managers · agencies · consultancies · professional services firms
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.onenote.comin a real browser with your saved login - no setup, no API keys. -
1
OneNote - build the client notebook
onenote.com
WebRun opens OneNote to build the client notebook. - Open OneNote and create a notebook named for the new client
- Add the sections you use on every account, such as meetings, scope, decisions, and billing
- Copy in your page templates so each section opens with the starter page already there, not an empty canvas
- Fill the header of the first page with the client name, the start date, and the account lead
- Generate the share link but leave inviting the client to you. WebRun never sends an invitation on its own
Done when The client notebook exists with every section and starter page in place.
-
2
Slack - hand the link to the account lead
slack.com
WebRun opens Slack to hand the link to the account lead. - Post the account channel a note that the notebook is ready, with the link
- Name the account lead so the handover has an owner
- List the sections created so anyone can see what is already set up
Done when The account lead has the notebook link in Slack.
-
3
Notion - log the account setup
notion.so
WebRun opens Notion to log the account setup. - Add the client to the accounts database in Notion with the notebook link and the setup date
- Record which template version was used, so a later change to the structure is traceable
- Check the client is not already listed before creating a row, so a re-added contact does not get a second notebook
Done when The new client is logged in Notion with a link to their notebook.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it share the notebook with the client?
No. WebRun creates the notebook and the share link, then posts it internally to Slack. Inviting the client is left to you, because an invitation reaches someone outside the company.
What if the same client gets added twice?
It checks the Notion accounts database first. A client already listed is skipped, so a duplicate or re-added contact never ends up with two notebooks and two sets of notes.
Can I change the structure it builds?
Yes. It copies whatever sections and page templates you set as the standard. Update the template once and every notebook built after that follows the new structure.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.