If that is the intended behaviour, then you need to have a ‘Get rows’ node just before the ‘if row exists’ with almost the same logic, so kind of redundant?
Maybe this is a common n8n pattern I’m not aware of, so would appreciate some clarity.
The documentation may not be very clear on this one
If row exists data table node passes the items it receives if a matching row exists. If the row doesn’t exist, this node won’t output anything. So make sure to toggle on Always Output Data from node settings so your workflow doesn’t stop.
It’s different than other nodes, and its closer to the IF node as it is a statement. You can attach Get row(s) data table node after it if you want to retrieve all values for that row.
But what’s the point of ‘if row exists’ then? You can just use ‘get rows’ and check if the output is empty or not. You achieve the same with less compute.
