You've hit on a very common and important workflow design pattern! You are correct that you need to create a "memory" for your workflow to check against. n8n has a built-in way to handle this without needing to set up your own external database or log. The key is the Remove Duplicates node. This node has an operation specifically for your use case called Remove Items Processed in Previous Executions. This mode allows the node to remember unique values from past workflow runs and only pass through items it hasn't seen before. Here’s how you can set it up: 1. Add the "Remove Duplicates" Node: Place this node in your workflow right after the node that fetches the YouTube data. 2. Configure the Node:Operation: Set this to Example Walkthrough Let's say your YouTube node returns items with a unique codeCopy id field. 1. Add the Remove Duplicates node after your YouTube node. 2. In the Remove Duplicates node settings:Set Operation to Now, when your workflow runs: - The first time, all the videos will be new, so they will all pass through the node. - On subsequent runs, if a video from a previous run appears again, the Remove Duplicates node will recognize its This approach creates the "memory" you're looking for directly within your n8n workflow, providing a simple and effective way to prevent processing duplicate items.

@Tony Mahony No problem at all!

@Alex Printer Thank you!