What features should we build next?

Tell us what we should focus next on. Usability improvements? Are there features that you are missing?

Note:

  • This here is an additional space to collect feedback and feature suggestions. All submitted suggestions are carefully evaluated. Once implemented, they are deleted from this board.

  • The actual discussions (and many heated debates đŸ”„) about upcoming features typically take place in our channel #ideas-feature-suggestions on Discord.

  • Release notes with all the updates that have been implemented are posted in our channel #releases on Discord as well as in our FB group.

  • To stay more up to date with our roadmap and releases, join our Discord https://discord.gg/aSUhf75fSz.

Improve auto-scroll when using check web element

Caveat: I’m not sure if I’m making a feature request or if I’m misunderstanding or misusing the product I have a standard loop without auto-detect and with a fixed high number of repetitions (e.g. 999999) so that it will auto-scroll. When I watch the auto-scroll, it works smoothly and as I’d expect for certain setups. For other setups, it keeps jumping way up and then scrolling far down repeatedly in a way that doesn’t look human. When this happens, the run also slows down steadily for each subsequent iteration, which I only noticed because I was saving the current time inside each iteration. I’m not sure why this is happening, but it means the overall run time will grow exponentially as the number of iterations increases. Admittedly, the steps inside the loop happen quickly, and I haven’t put in an explicit delay after every block so I can watch and troubleshoot the auto-scroll precisely - but at this point, my hunch is that the auto-scroll spasms happen when the loop contains a lot of Check Web Element blocks that look for optional elements that usually are “Not Found.”  I think the taskbot is scrolling down excessively when it can’t find those optional elements for the current iteration.  Then when it starts the next iteration, it jumps way up and the process starts again. While it generally makes sense for auto-scroll + check web element to scroll down farther, I think it does not need to scroll as far down as it is doing. The CSS selectors inside the loop are all for nth-child(x), so once the auto-scroll sees that it has reached nth-child(x+1), it can stop without going to nth-child(x+2), etc. Things I’ve tried: * playing around with the “selectors must be visible on screen” box to reduce unnecessary jumping around * making sure the web element blocks inside my loop are processed in the order in which they’d appear, if they appeared but the auto-scroll spasms are still happening

zeroworkme 16 days ago

Option to "Save as a template" when selecting building blocks

When selecting a building block / multiple building blocks: Add the option to save the selection as a custom template (with its current configuration) then you can name the template to describe its function. These templates would be like pre-made flows, which you can always drag and drop into your taskbot (just like a building block) whenever you want to add specific functions. This would solve the need to either: create functions from scratch every time search in your taskbots for where you’ve previously configured a function, selecting the exact building blocks you’re looking for and then duplicate it to wherever you need it placed - too much cumbersome process (which is also prone to mistakes in case you’re not selecting the blocks properly)

Yan 16 days ago

conditional logic - check text on web element

I want to set conditional logic based on the text in a web element (e.g. if text = X
etc). Currently the only way to do this function is to save the web element to variables, and then start condition based on the variable - but that’s just too cumbersome. This is a function that should’ve been easily set in just one block, without having to use variables at all. My suggestion: add a “web element text” option to the dropdown selection in “start condition” block. Then, when “web element text” is selected, you can enter the element’s CSS or XPath selector in the field below. Then you can set the conditions in the next blocks as usual, according to the web element’s text.

Yan 18 days ago

Building block that writes all pending rows to Google Sheet

i would love to have a new building block that forces all accumulated/pending rows to be written out to the Google Sheet without having to wait for the next 100-row mark. i would mostly use it when i have a random delay built into the taskbot inside a loop (inserting it just before the delay). the longer the delay, the more likely it is that the taskbot can crash during that time, such as if the user closes the browser or shuts down their machine or whatnot. if that happens, i don’t want to lose the data that been generated so far. the reason i am not using a repetition limit on the loop and scheduling the taskbot to run every so often is that i do not want to keep starting a new run. in one case, it’s because each separate run will cause the site to show another captcha. in another case, it’s because i’m scrolling down a long page and i want to keep my position for the next run, and not have to scroll down and find it again. i also think that will reflect more human behavior. a side benefit (but definitely not a driving reason) is that this block can allow multiple taskbots to share the same google sheet at the same time, even when taskbot A writes to the google sheet and taskbot B needs to read that data before taskbot A finishes running.

zeroworkme 19 days ago

Send data table into Write JavaScript block

https://docs.zerowork.io/using-zerowork/using-building-blocks/write-javascript says “Custom looping through existing rows of a table within your code block in order to update data (as opposed to append) is currently not supported.” i want to set up a dynamic Start Repeat such that i can access two different rows of the table at the same time. right now, i can use variables to carry over the values from row X to be available when i am processing row X+1, but once i’m processing row X+1, i cannot access row X anymore. i’m guessing that if i can send an entire data table into the javascript block, then i will be able to jump around between different rows however i want.

zeroworkme About 2 months ago