I love your platform but pls make more webscrape friendly.
Give detailed explanation to retrieve nested elements. You guys give example of …>… in your documentation which does not explain how it works.
More times it is easier to find ID than a class.
Since you guys are on band wagon of no-code which I love.
When your do HTTP request, clean up the code using the Beautiful Soup libary svp.
Then structure the output of the node based on elements, like parent and children overview of the web pages.
The I only need to select the element to retrieve it is data.
Every growth hacker, markereer, developer, data scientist, data analyst will thank you if you actually build this.
Pls don’t hesitate to reach out to me, I am happy to highlight some other UX improvements that will help you get more customers, and more loyal userbase.
To recap you guys make amazing platforms, just make it marketeers friendly, we suck at coding.
Thanks for the feedback, I do have one question though what do you mean by “why does n8n break at 0.653MB” I can’t see any reference to this or an error message / example in your post.
If you have a link to the docs page we can pass it to our docs team to look at although as a starting point it would be worth playing with css selectors more they are very cool and you can do some neat things with them.
Perfect that doesn’t look like anything is broken. We don’t automatically load all of the data in the UI if it is over a certain amount to help prevent the browser crashing from the extra data. You can still manually view the data if needed.
