Extract tasks from Notion AI meeting transcripts (no dupes)
Notion AI agents extract tasks from meeting transcripts without duplicates. Set up your databases, trigger, and upsert logic with this step-by-step guide.
Notion setup for multi-client email campaigns
Notion email campaign management: build a Clients → Campaigns → Emails database with rollups and a lightweight review workflow for multi-client teams.
TABLE OF CONTENTS
If you manage email campaigns across multiple clients, you know the problem with shared documents: too many files, too many versions, and no simple way to see what is approved, what is live, and what is pending. Notion email campaign management solves this with a relational database structure that replaces the folder chaos.
Why Google Docs breaks down for multi-client campaigns
When email lives in shared documents, teams typically run into a few predictable problems:
- Finding the “right” doc becomes slower as campaigns and clients grow.
- Version control becomes unclear when multiple people edit or copy templates.
- It is hard to answer basic questions like “How many emails are in this campaign?” without manual counting.
- Review and approval happens in scattered comments instead of a consistent workflow.
The simple Notion database schema (Clients ↔ Campaigns ↔ Emails)
At a high level, you will create three databases:
- Clients (one row per client)
- Campaigns (one row per campaign, related to a client)
- Emails (one row per email template, related to a campaign)
This relational structure is the key difference between Notion and a folder of documents.
Database 1: Clients
Purpose: a single source of truth for each client.
Recommended properties:
- Client name (title)
- Primary contact (text)
- Status (select)
- Notes (text)
Relations:
- Campaigns (relation to Campaigns)
Rollups:
- Campaign count (rollup: count Campaigns)
- Email count (rollup: count Emails via Campaigns, if you add a second relation or a rollup chain)
Database 2: Campaigns
Purpose: a container that groups emails for a specific launch or initiative.
Recommended properties:
- Campaign name (title)
- Client (relation to Clients)
- Goal (text)
- Launch date (date)
- Owner (person)
Relations:
- Emails (relation to Emails)
Rollups:
- Email count (rollup: count Emails)
- Approval progress (rollup: count Approved vs Needs changes, if you add a Status on Emails)
Database 3: Emails (templates)
Purpose: store each email as a page, with structured metadata.
Recommended properties:
- Email name (title)
- Campaign (relation to Campaigns)
- Email type (select: welcome, follow-up, reminder, etc.)
- Send order (number)
- Status (select: Draft, Needs review, Approved, Sent)
Page body (the email content):
- Subject line
- Preheader (optional)
- Email body
- Notes for reviewers
Add rollups so you can see counts at a glance
One of the fastest wins in Notion email campaign management is using rollups to answer questions instantly:
- “How many emails are in this campaign?”
- “How many campaigns are active for this client?”
- “How many emails are waiting for approval this week?”
This replaces manual counting and helps you spot bottlenecks.
Build a simple review workflow (without over-engineering)
A lightweight review workflow usually looks like this:
- Email status starts as Draft.
- When ready, it moves to Needs review.
- Reviewer updates to Approved or Needs changes.
Two practical tips:
- Keep the workflow on the Email database, not in a separate task system.
- Use saved views for each person:
- “Needs review (mine)”
- “Approved, ready to schedule”
- “Needs changes”
Client-facing review (two options)
Teams running a multi-client marketing workflow often want clients to review emails without seeing other clients' data.
Option 1: Share individual email pages
This is the simplest approach:
- Share only the specific email page(s) a client needs to review.
- The client cannot browse your full database.
This works well when you have fewer emails, or when you want tight control.
Option 2: Page-level access + a filtered client portal
If your Notion plan supports it, you can use page-level access to:
- create a “client portal” page
- embed a linked view of the Emails database
- show each client only the emails they are allowed to see
This is more scalable when clients routinely review many templates.
Common mistake: trying to make emails “fit” in a table view
If email names get long, table cells become hard to scan.
Two fixes:
- Open the record page to view the full list of related emails cleanly.
- Use a short naming convention (for example: “01”, “02”, “03”) plus a separate “Email title” property for readability.
Where Notion AI fits (optional)
Once your email templates and campaign metadata are inside Notion, teams can use Notion AI for things like:
- rewriting for tone
- drafting variants
- summarizing review notes
- generating subject line alternatives
The biggest win is not the AI feature itself. It is that your email knowledge base is structured and searchable.
Get help building this Notion setup
Building a Clients → Campaigns → Emails structure in Notion usually breaks at the rollup configuration — specifically when chaining rollups across two relations to get an email count on the client record. If you've hit that wall, book a ZoomFlow session — one of our consultants can build the database structure with you live and get your review workflow running in the same call.
Related Posts
Auto-update Hive project status from phase dates
Stop updating Hive project statuses by hand. This guide shows you how to automate status updates by phase date ranges — with guardrails and sandbox testing.
How to consolidate Asana and Slack tasks into one Notion to-do list
Learn a simple system to pull tasks and messages from client tools like Asana and Slack into one Notion to-do list, so you can work from a single dashboard.
