Today @emmanuel hosted another Demo Day + AMA on youtube (you can watch the replay here) and in today’s event, he showed something I think a lot of us in the community are very excited about.
Workflow Engine Upgrades
Here are some screenshots from the livestream:
New “Control flow” options like Branching (If/else), For and While loops
The team is actively working on this so the final version we ship might look different than what you are seeing here today.
But this is something coming in months and it’s pretty exciting so I wanted to share with everyone and get your first impressions!
I think both branching and loops will be a step up for crafting cleaner, more readily understandable logic, even if neither necessarily enables something that was previously not possible.
While we didn’t get a glimpse of the looping UI, the burning question for me is whether they’ll be more performant than current client-side iteration techniques, and if so, by how much.
@fede.bubble, is there a way to request early access once the features are mature enough?
Give us an option to make a custom safe guard, for a loop, I want 30 iterations maximum and for another maximum 10. We currently have this but is not custom and applies to every workflow ( can we add a custom value too?).
Unlimited If conditions on if/else conditions, similar to WeWeb and Flutterflow and a view with zoom to help visualization.
Loop inside loops will be available? I made some workflows in the past that required this.
Yes, even for things like using a “Formatted as text” on a list and wanting a number for each item(e.g., 1 - Item, 2 - Item, etc.)
Absolutely necessary. Maybe @brenton.strine can ask for this on Slack? Apparently, he has magical powers that allow feature requests to be turned into shipped features.
One thing that the current demo didn’t show was branching without conditions. It should be possible to also have things run in parallel without having to apply If/Else/Else If. This is something we discussed with @tj-bubble a while back, very important for LLM workflows. Other than that the general implementation looks great. Design is a little wonky but I’m sure it will get ironed out after release just like the Workflow Editor (which is in a great state now).
This would definitely be a welcome convenience (and likely more performant in contexts where that matters), but it’s at least doable now without resorting to a regex hack…
In the above, products is a custom state on the index page.
I’ve used the regex approach in Stripe API request bodies, and the current approach is much simpler and cleaner; but This Product's index would be cleaner still.
This looks promising and will go a long way in cleaning up really complex workflows. Is there any rough timeline of when this will be in a state to test?
so feel free to use it liberally everywhere 
