This is an extremely annoying feature/issue of n8n when using pinned data, half the time when you just want to run a single step to test and have all the previous steps using pinned data it throws this error: **
Using the item method doesn’t work with pinned data in this scenario. Please unpin ‘Approval Notification’ and try again.**
An expression here won’t work because it uses .item
and n8n can’t figure out the matching item. The node ‘Approval Notification’ didn’t return enough information.
But this error often has nothing to do with the actual issue being flagged which is that it can’t identify the “item” in question, when previously it had no issue. All you have to do to “clear” the issue is rerun the previous node, even though the output data is already pinned.
For example in my current workflow the “previous node” in question is just a notification, it has nothing to do with the “item” method and somehow just running it again fixes the problem in about 50% of cases. It seems that making any slight change to a previous step in a working workflow “breaks” the “item” path somehow even though none of the related data has changed.