Provision a secure Notion Client Portal — the moment they sign
Import the blueprint into Make, point it at your Clients and Client Portals Notion databases, and every new client automatically gets a fully provisioned portal — Landing, Brief, Files, Decisions, and Status Board sub-pages ready to scan — and a portal-link email in their inbox, without a single workspace stand-up.
Secure checkout via Stripe · Instant delivery · Built for Make + Notion
Everything in the bundle
What you get when you buy
- Make (Integromat) scenario blueprint — JSON file you import in one click
- Two pre-mapped Notion database schemas — Clients + Client Portals (with field IDs prepared)
- Notion sub-page template — Landing, Brief, Files, Decisions, Status Board ready to clone
- Notion blocks layout — H2 headers + to-do / numbered-list / callout blocks pre-baked
- Conditional portal-link email — fires based on a Notion checkbox per Client row
- One-time purchase · Instant delivery · No subscription
One-time purchase
$27
The automation
Five Make modules. One client portal.
Each module runs automatically. Together they turn a raw new-client row in your Clients database into a fully provisioned Notion workspace — with structured Landing, Brief, Files, Decisions, and Status Board sub-pages — and a portal-link email sitting in the client's inbox.
Your team drops every new client into a Clients database — a few structured properties for name, contact, engagement, status, and start date. The moment a Client row is marked "Portal Ready", the scenario triggers automatically.
⏱ Triggers when Status → "Portal Ready"
Make clones your Client Portal template page, populating client name, engagement name, start date, and owner. The cloned tree includes Landing, Brief, Files, Decisions, and Status Board sub-pages — every page already wired with the engagement fields you forwarded from the source Client row.
⏱ Runs immediately after the trigger
The scenario writes four structured H2 sections into the Status Board sub-page using Notion blocks: Brief Summary (paragraph), Key Milestones (to-dos the client can tick off), Decisions Log (timestamped numbered list), and Next Steps (callout blocks everyone sees at a glance).
⏱ Happens in the same cycle as the sub-page creation
Back on the original Clients row, the Status flips to "Active" and the provisioned portal URL is recorded on the row itself. Now anyone scanning the Clients database can see at a glance which engagements have a live portal and follow the link to the workspace.
⏱ Marks immediately after blocks are appended
The scenario fans out a short transactional-style email to the client with their portal URL, the engagement name, and a one-line welcome. If the Client row has the "Skip portal email" box checked, this step is skipped silently and the rest of the chain runs unchanged.
⏱ Fires conditionally based on the Skip portal email checkbox
Setup in three steps
From purchase to live in under an hour
Buy & download
Complete checkout and receive the Make blueprint JSON, two pre-mapped Notion database schemas, and the setup guide instantly.
Import the blueprint
In Make, create a new scenario and click Import Blueprint. Create (or import) the Clients and Client Portals databases in Notion, then drop your portal template ID into the placeholder field. About ten minutes.
Connect & go live
Connect your Notion workspace, activate the scenario, and the next time a Client row is marked "Portal Ready" a fully provisioned portal sub-page tree appears in Notion and the client gets the welcome email.
From client-heavy teams
Set the structure. Let the portal appear.
Operators who wired this template into their stack and stopped building client workspaces by hand.
Buyer questions
Before you buy — quick answers
Frequently asked questions
Questions before you buy
Setup & delivery questions
Frequently asked questions
More from the lineup
Pairs well with…
Every Purrly template ships as the same Make + Notion pattern. Build the rest of your stack with the same one-time-purchase blueprint model.
The natural teammate: turn every project brief into a row on a Status Board database with Summary, Decisions, Milestones, and Risks blocks ready to scan.
Pair the Client Portal with the wiki pattern — same Notion + Make combo, publishes a polished wiki entry per meeting transcript.
Run a new client from first form to signed contract — with a Notion workspace and the brief, files, and decisions structure ready to go.
A 4-email onboarding automation that turns new subscribers into buyers — same Notion + Make combo with an email arm.
Capture leads from a form, structure them in a Notion database, and notify Slack — the publishing pattern ready for CRM-style pages.
A Slack-native counterpart for stand-ups: collect daily updates, roll them up per author, and ship a Friday recap.
Stop building client portals by hand. Let Make provision them.
One-time purchase. Instant delivery. Your next signed contract is the start of a tidy, current, fully provisioned Notion Client Portal — with a status board visible the moment their invoice clears.
One-time purchase · Instant delivery · Built for Make + Notion · Works for any client-heavy team