I have created a knowledge wiki for plants with WordPress.
Using a link list (website links), I provide different plant names.
Example: 100 plant links that are then processed with the help of AI, Wikipedia, Google, etc., and finally published as new posts in WordPress.
(So far this works great.)
Now I need a way to check for existing entries to avoid duplicates when new plant links are added.
In other words: I want to check if the plant already exists in the wiki.
My first idea was:
After the n8n process runs and a new knowledge entry is created in WordPress, I send the title (plant name), source link, and WordPress post ID to a baserow.io table.
Before creating a new post, I query this table in the n8n loop to check if the title (plant name) already exists.
This part works – but: baserow.io only gives me a simple output like “match found” or not.
What I actually need is branching logic like this:
-
If the query finds a match → go back into the loop (Path 1).
-
If the query finds no match → continue with Path 2 and create a new post.
But the Baserow module doesn’t support this kind of branching. I’m not sure how to move forward.
Alternative idea: Would it be easier to query WordPress directly for existing posts (e.g., by title)?
So far, I haven’t found a solution for how to do this with n8n.