Archive and Delete Duplicate Items from a Notion Database

This n8n workflow helps you maintain a clean Notion database by identifying and archiving/deleting duplicate entries. It's designed to run on a schedule, ensuring your database remains free of redundant information.

What it does

This workflow performs the following steps:

1. Triggers on a schedule: The workflow is initiated at predefined intervals (e.g., daily, hourly).
2. Fetches Notion database items: It connects to a specified Notion database and retrieves all items.
3. Identifies duplicates: A "Code" node processes the retrieved Notion items to find duplicates based on a defined criteria (e.g., matching titles, specific property values).
4. Filters for duplicates: An "Edit Fields (Set)" node likely prepares the data for the next step, possibly by extracting unique identifiers or flags for duplicates.
5. Aggregates duplicate IDs: An "Aggregate" node collects the IDs of all identified duplicate items.
6. Archives/Deletes duplicates in Notion: For each identified duplicate, the workflow interacts with Notion to either archive or delete the item, depending on the configured action.

Prerequisites/Requirements

• n8n Instance: A running instance of n8n.
• Notion Account: A Notion account with access to the database you want to manage.
• Notion Integration: An n8n Notion credential configured with access to your Notion workspace and the specific database.

Setup/Usage

1. Import the workflow: Import the provided JSON into your n8n instance.
2. Configure Notion Credentials:
   • Locate the "Notion Trigger" and "Notion" nodes.
   • Click on the "Credential" field and select an existing Notion credential or create a new one. Ensure the credential has the necessary permissions to read and modify (archive/delete) items in your target Notion database.
3. Configure Notion Database:
   • In the "Notion Trigger" node, select the "Database ID" you want to monitor for duplicates.
   • In the "Notion" node (for archiving/deleting), ensure the "Database ID" is also correctly set.
4. Customize Duplicate Detection (Code Node):
   • Open the "Code" node. This is where you define what constitutes a "duplicate."
   • Modify the JavaScript code to match your specific criteria for identifying duplicates (e.g., comparing properties.Name.title[0].plain_text, or other unique properties).
5. Choose Action for Duplicates (Notion Node):
   • In the "Notion" node responsible for processing duplicates, configure the "Operation" to either Archive Page or Delete Page based on your preference.
6. Set Schedule (Schedule Trigger):
   • Adjust the "Schedule Trigger" node to define how often you want the workflow to run (e.g., daily, weekly, or at a specific time).
7. Activate the workflow: Once configured, activate the workflow to start automatically cleaning your Notion database.