Hello,
This is a part of my workflow and I would have expected that the node “PD - get all deals” does every time when it come back from the loop run again and checks for new deals with that given filter id. But somehow it does only run two times and then stop.
It looks like your topic is missing some important information. Could you provide the following if applicable.
OK I got it. The Merge node seems to only output the first run. How can I do it so it does always output?
You can wrap the process in a loop over nodes loop.
You will still have the problem of making sure you have that merged data since the merge will still only output once.
What you can do is merge it then save the days with an edit fields node. That would be the easiest way to work around it.
These are the hard types of workflows that need to be architected correctly from the beginning in order to avoid these issues. It comes with practice and running into the issues yourself so don’t get discouraged and keep trying things
really not easy 
where would you place the edit fields node? I would think to put two inputs to the excuten node but this also doesn’t work.
Can I save the values with the Edit fields node and access it within the sub-workflow? And how could I delete the set node then to make sure it does not take the wrong data?
I might have overcomplicated that a little bit. While that’s an approach worth taking sometimes, try this workflow.
Copy and paste that into your canvas and see if that is the behavior you’re looking for
Hi Liam,
thank you again for your help. In my case I have no Items to loop through. I do always get a new Item when reaching the “PD - Get all Deals” node.
Any Idea how to manage this? I did like your idea of using the set node and access its data within the loop. But so far I was not able to access it. Tried with a code node but the output of it is empty
I did use now seatable to store the data but I still wonder if there is not an easier or n8n build in solution?
Does the get all deals node return a list of all of the deals or just one? If it returns all of them then you can just loop using the built in features instead of looping back as you are here
This is my problem. It can only list I think 500 or so but the crm can have much more deals thus I do limit it to one and loop as long as there are some.
I found it very complicated to design that workflow and felt like using many workarounds where I thought it should be possible with existing default nodes.
e.g.
A set and get node for one execution would be very handy or as needed a merge node which uses the last input variable if there is only a new one at the other input available.
There is something called pagination which handles that.
APIs will not usually return all data, you will need to detect if there is more then request more. There are pagination features built into n8n’s http node.
What ever service you’re using for the crm google “service API pagination” and the pagination docs should come up.
Then look up stuff on pagination on the n8n forum. I know I myself have written enough on here to cover most common questions.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
