The Scenario
You're a data engineer and you've inherited a migration script that needs Notion page IDs as inputs. Your colleague left you a Excel workbook with 50 Notion page titles in column A — no IDs, just names. The script won't run without UUIDs and manual lookup through the Notion search bar is going to take the better part of an afternoon. The migration is supposed to start tomorrow.
The bad version:
- Open Notion search, type the first page title from column A, find the result, click into it, copy the page ID from the URL bar, paste it into column B of the workbook, go back to the search bar, repeat.
- Realize after fifteen searches that Notion's search returns multiple results for ambiguous titles — "Product Spec" matches six pages — so you have to open each result, check the breadcrumb to confirm which one is correct, and pick the right UUID.
- After an hour you have 35 of 50 IDs. The remaining 15 have titles that either don't search cleanly or return too many results to confidently pick from.
Manual UUID lookup for 50 pages is reconnaissance work in a system that was designed for humans, not for piping IDs into scripts.
The Easy Way: One Prompt in SheetXAI
SheetXAI reads the page titles from column A, searches Notion for each one, and writes the matching page UUID back into column B — flagging any titles with multiple matches so you can resolve them.
Column A has Notion page titles — search for each one and write the matching page ID into column B — if multiple matches are found, write all matching IDs separated by commas and flag in column C as "multiple matches"
What You Get
- Column B fills with a UUID for each title in column A where a single unambiguous match is found.
- Titles that match multiple pages get all matching IDs listed in column B, comma-separated, and "multiple matches" written to column C for manual resolution.
- Titles with no Notion match are flagged in column C as "not found."
What If the Data Is Not Quite Ready
Some titles in column A have slight variations from the actual Notion page title — use fuzzy matching
Column A has Notion page titles — search for each using fuzzy matching and write the best-match page ID to column B — write the actual matched page title to column C so I can verify
Fuzzy matching catches "Product Spec v2" when the workbook says "Product Spec V2" and confirms what was actually matched.
You need to scope the search to pages within a specific parent page or database
Column A has Notion page titles — search within Notion database ID abc123 only — write the matching page ID to column B, or "not in database" to column C if no match is found in that database
Scoped search prevents returning page IDs from other parts of the workspace where the same title exists.
After writing the IDs, you need to fetch each page's current Status property and write it to column C
Column A has Notion page titles — search for each and write the page ID to column B — then fetch the Status property of each matched page and write it to column C
ID lookup and property fetch in one pass. Column C tells you the current state of each page before the migration script runs.
The kill chain — fuzzy title search, scope to database, fetch status, flag ambiguous
For each title in column A: search within Notion database ID abc123 using fuzzy matching — write the best-match page ID to column B and the matched title to column C — fetch the Status property of each matched page and write to column D — flag any title that matched multiple pages as "ambiguous" in column E
One prompt: scoped fuzzy search, ID capture, title verification, property fetch, ambiguity flagging. The migration script gets a clean input list with one column to manually review before running.
A clean ID list with flagged ambiguities reviewed before the migration runs is the difference between a clean cutover and a two-hour rollback.
Try It
Get the 7-day free trial of SheetXAI and open the Excel workbook with your page titles in column A. Ask SheetXAI to resolve the UUIDs and flag anything ambiguous so your migration script has the inputs it needs. Also worth reading: bulk-update-database-rows for using those IDs to push changes after the migration, and the hub overview for all Notion workflows.