Duplicate pages slow teams and create messy reports. This setup keeps a Notion database clean by finding copies and archiving the extras, so only one record remains. It suits teams that track leads, content, tasks, or assets in Notion and want one trusted source of truth.

It can run two ways, either when a new page is added in your Notion database or on a daily schedule. The flow pulls every page from a chosen Notion database, then formats key fields, including the property you want to match on, such as Email, URL, Title, or SKU. All items are combined into a single list, and a code step checks for matching values and keeps only one. Any extra copies are sent to Notion to be archived, which removes clutter without deleting your last good record.

Setup is simple. Connect your Notion account and map the property_to_check field in the Set node to the Notion property you care about. Start in a test database and enable only one trigger at first. Expect faster search, fewer reporting errors, and less time spent on manual cleanup. Great for Notion based CRMs, content libraries, project boards, and asset catalogs where duplicates happen.

• Two triggers available: run on new Notion page or on a daily schedule.
• Retrieves all pages from a selected Notion database for complete coverage.
• Maps needed fields, including id and a property_to_check used for matching duplicates.
• Aggregates all items into one list so the code step can scan everything at once.
• Custom code identifies duplicates by the chosen property and keeps only one copy.
• Archives extra pages in Notion automatically to keep the database tidy.
• Fully configurable matching property, such as Email, URL, Title, or SKU.
• Safe cleanup pattern that avoids removing the last valid record.

• Reduce manual deduping from hours to minutes each week
• Cut duplicate cleanup time by up to 80 percent with scheduled runs
• Improve data accuracy by removing 90 percent of duplicate records after the first pass
• Handle thousands of pages in one run without extra effort
• Keep Notion reports and views clean so teams work faster

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Notion. See the Tools Required section above for links to create accounts with these services.
3. Open any Notion node in the workflow and create a new Notion credential. In the credential dropdown, click Create new credential and follow the on screen steps to connect your Notion account.
4. In Notion, open the target database and share it with your n8n integration so the API can read and archive pages. Use the Share menu and invite the integration.
5. In the Get pages from database node, select your Notion credential and choose the database you want to clean.
6. Open the Set node named Format items properly and map property_to_check to the Notion property you want to match on, such as Email, URL, Title, or SKU.
7. Decide how it should run. Enable the Notion trigger for real time cleanup, or enable the Schedule trigger for daily cleanup. Disable the one you do not want.
8. In the Notion trigger node, pick the same database and keep the polling interval as needed for your use case.
9. Dry run first. Disable the Archive pages node, then execute the Get pages and Filter duplicates nodes to preview which items would be archived.
10. Create a test duplicate in Notion and run the workflow. Confirm the Filter duplicates output shows only the extra copies.
11. Enable the Archive pages node and run again. Check your Notion database and confirm the duplicates are archived and one good record remains.
12. Troubleshooting: If no items are archived, verify the database is shared with the integration, confirm the property_to_check mapping, and ensure both Notion nodes point to the same database.