Block 1 - Every day
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
â Who is this for? If youâre using Notion to manage a database (like saving links, tasks, notes, or anything really), and itâs starting to get messy with duplicate entries, this workflow is for...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.notion, n8n-nodes-base.aggregate, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.notiontrigger, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by LucĂa Maio Brioso.
Original n8n.io sourceIf youâre using Notion to manage a database (like saving links, tasks, notes, or anything really), and itâs starting to get messy with duplicate entries, this workflow is for you.
Itâs especially useful if you want to keep things tidy without doing any manual cleanup.
Notion doesnât have a built-in way to find or remove duplicates, so you either clean them up manually đŠ or just let them pile up.
This workflow automatically finds entries that share the same property (like a URL or title) and archives the extra copies, keeping just one.
It includes two optional triggers:
"SET YOUR PROPERTY HERE" with a reference to the property you want to use for detecting duplicates. I recommend using the n8n property drag-and-drop feature.And thatâs it. It runs on its own after that.
Set node.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | đ§š Archive (delete) duplicate items from a Notion database |
|---|---|
| Complexity | intermediate |
| Nodes | 11 |
| Categories | Personal Productivity |
| Author | LucĂa Maio Brioso |
| Published | 01 May 2025 |
Use the JSON export at /data/workflows/3825/3825.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
â Who is this for? If youâre using Notion to manage a database (like saving links, tasks, notes, or anything really), and itâs starting to get messy with duplicate entries, this workflow is for...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Personal Productivity use case.