Splitting items not working

Hey,
I’m fairly new to n8n and quickly running into issues. I’ve checked previous questions related to this topic but can’t find the exact use case. So apologies if asking something that is somewhere else. I actually have 2 questions in 1:

I’m building a recipe scraper, and managed to scrape and clean the data. So that part of the flow is ok. Then I want to add 1 row to my recipe table and as many rows to my ingredients table as ingredients.

This is the workflow:

The first Supabase insert works ok.
Then I want to split out the json node ingredients from the previous node (not the Supabase one). I think this is possible right? doing something taking as input a previous node (not the immediately previous one).

When Testing the Split Out I’m not getting anything. See the error:

The second question is if this is the right pattern: I’m assuming the second Supabase node will execute as many times as items in the Split, and then it’ll pull input from both the Split item and the previous Supabase node (2 steps before). Is that right?

Information on your n8n setup

  • n8n version:1.79.3
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): cloud
  • Operating system:

Your Field to Split Out parameter appears to be referencing the output of the 2nd previous node. I don’t think Split Out will operate on anything but the immediately previous node.

So, it might fix things to fork the output from the LLM and route into Insert scraped recipe and Split Out in parallel. Then, if you need the output from Insert scraped recipe as context/input for Insert scraped ingredient, you’ll need to merge the output of those forked paths.

If you add an Edit Fields, before it and have it reference the fields you want to split out it should work, Something like the following

Thanks, this worked!

1 Like

Which thing worked? See if you can re-mark the actual post that solved it as the Solution.

I think it was your response that fixed it. I noticed it has your profile picture lol @hubschrauber

Yep, that was the one. I think it would have also worked by using the Set / Edit node. I just thought that moving the Split Out just after the Node that generates the info seemed mroe elegant. I’m new to this, but trying to learn

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.