If I have a list of items being sent to a node, should the node be called “n” times, once for each item?
Im using a Notion node to get the content blocks on a page - the input is a list of pages and their ids - there are 3 sent to this node and Im expecting “get page content” to be called 3 times
From my understanding as long as I dont specify to “run one with all” then this should work this way - however Im getting 13 items out, with blocks from all 3 pages - this is kinda throwing the entire workflow out of wack since I want everything to be called once for each item - I had to create a JS node as a work around to ground them back together
Just wondering if this is a bug or if Im missing something
Yup thats why I raised the question. I think this is a bug with the Notion node then, unless “return all’ has something to do with it - maybe that option needs some clarification - thanks
No I doubt it is a problem with the Notion node. This is how n8n is designed to work. The “Return All” option on the Notion Node is purely to control whether you want Notion to return all data or whether you want to only return 10 records as an example. Imagine you have a million records in Notion, then Return All could slow down everything as it’s unrealistic to pull so many records. You can also hover over the (?) next to the field to see what it does.