How to Verify Emails in a Notion Database (Export, Check, Re-Import)

To verify emails in a Notion database, export the database as a CSV, upload the file to an email verifier, and bring the valid, risky or invalid result back into Notion as a new property. Notion can store an address, but it cannot ask the recipient's mail server whether that mailbox exists. SimpleVerifier does that check: upload the CSV on the verify page, download the results, and filter your outreach view to valid only. Pro is $39 a month, and 100 checks are free.

The Notion steps below come from Notion's own help page on exporting content, read on 10 November 2026. Menu names change, so check them in your workspace.

Why verify a Notion contact list

Notion is a common place to keep a small lead list, a waitlist, a speaker list or a partner tracker. Those lists are typed by hand, pasted from a form or copied from a website, and they sit untouched for months. Three problems build up quietly:

• Typos. A pasted address with gmial.com or a stray space looks fine in an Email property and bounces every time.
• Dead mailboxes. People leave companies. An address that worked in spring may be closed by autumn.
• Made-up and disposable addresses. If any rows came from a public sign-up form, some will be throwaway or invented.

Every hard bounce counts against your sending domain. Mailbox providers watch how many of your messages are rejected, and a run of bounces from one batch can push future mail towards spam. Checking the list before you send is cheaper than repairing a domain afterward. Our guide to why cold emails bounce goes through the causes in more detail.

Step 1: Export the database from Notion

Per Notion's help page:

1. Open the database and click the three-dot icon at the top right, then click Export.
2. In the export window, choose Markdown & CSV from the format dropdown.
3. Switch on Include subpages only if the data you need lives inside sub-pages.
4. Click Export and save the file.

The download is a zip file containing a CSV for each database. Unzip it first. Notion's page says you can export the current view or the default view, but not all views at once, and that form views cannot be exported, so switch to a Table view if you built the list in a form. For very large exports Notion may email a download link instead of starting the download.

One thing the help page does not say is exactly how every property type is written into the CSV, so open the file and look before you upload. Find the column holding the email addresses. If your database has a relation to a separate people or companies table, the address may sit in that other database, and you would export that one instead.

Step 2: Tidy the file before you pay to check it

Removing junk first means you spend checks only on addresses worth checking.

• Remove duplicates. The same person pasted twice is two checks and, later, two emails. The duplicate email remover handles this.
• Fix obvious typos. The email typo corrector catches common domain misspellings such as gmial.com.
• Split cells with several addresses. If someone typed two addresses in one cell, the multiple-emails splitter separates them.
• Pull addresses out of mixed text. If the column holds names and notes together, use the Notion database to email list tool to produce a clean list of addresses.

Step 3: Verify the CSV

1. Go to the verify page and sign in with Google. Your first 100 checks are free, no card.
2. Upload the CSV. If the file has more than one column that looks like an email, the page asks which one to use.
3. Wait for the list to finish. Large lists take longer; our post on how long bulk verification takes explains what drives it.
4. Download the results. Each row carries a status of valid, risky or invalid, a reason, and a send-advice column.

What the three statuses mean:

Status	Meaning	What to do
valid	The mail server confirmed the mailbox exists.	Safe to send.
risky	Delivery is not confirmed: catch-all domain, role address such as info@, or a provider that will not say.	Keep out of large cold sends. Test in a small batch.
invalid	Bad format, no mail server, disposable address or mailbox not found.	Do not send.

Risky is not a polite word for bad. A catch-all domain accepts every address at the door, so nobody outside the company can say whether one particular mailbox is real. Treat those rows as a separate, smaller group. The catch-all send limit calculator helps size that batch.

Step 4: Bring the results back into Notion

Notion does not have a live link to SimpleVerifier, so this step is a CSV round trip:

1. In your Notion database, add a Select property called Email status with options valid, risky and invalid. Add a Text property called Email reason.
2. Open the downloaded results file and keep the email, status and reason columns.
3. Match each result to its row by the email address. For a small list, pasting the status column into the matching property works if you keep the original row order. For a larger one, use whatever Notion import and relation features suit you, matching on the email address.
4. Create a view of the database with the filter Email status is valid. Use that view as your mail-merge source.

Keep the original export. If a row looks wrong later, the file shows what you checked and when.

Step 5 (optional): Automate it with the API

If your Notion list grows daily, for example from a sign-up form feeding the database, a one-off CSV round trip gets tedious. The REST API checks one address per call: GET https://simpleverifier.com/api/v1/verify?email=... with a bearer key from the API keys page, returning status, reason and a send_advice field. Pro includes 10,000 API calls a month. Any automation tool that can read a Notion page and make an HTTP request can call it; see the Zapier, Make and n8n pages, and the API docs. There is no native Notion integration, so you build the read and write steps yourself in that tool. Keep keys on a server or automation platform, never in a public page.

What to do with each result

• Valid: use in your outreach or mail merge.
• Invalid: delete, or move to an archive view so nobody re-adds it. Keeping a record of dead addresses stops them returning on the next import. See cold email suppression lists.
• Risky: send small, watch bounces, and never mix with a large valid-only send.

Then verify again before each new campaign. Lists decay, so a result from six months ago should not be trusted. See how often to verify an email list.

Common mistakes with a Notion list

• Checking the wrong column. If the export has both a work and a personal address, make sure you upload the one you will actually mail.
• Losing the link between rows and results. Keep an ID or the address itself in the results so each status can be matched back.
• Marking risky as invalid. Risky rows are not dead; they need a gentler send, not deletion.

What it costs

SimpleVerifier Pro is $39 a month. The first 100,000 checks a month run at full speed, then they run slower, and you are never cut off. You can try 100 free checks first by signing in with Google, no card. See pricing for the other plans.

Bottom line

Notion stores addresses but cannot confirm them. Export the database as CSV, check the file, add a status property and filter to valid. For a hand-built list of a few hundred contacts this takes a few minutes. Try the 100 free checks on a slice of your real list and see how many rows come back risky or invalid before you send.