Workflow Automator

Hello,

I noticed that this idea has been open for some time, and I wanted to check if there has been any progress or updates.

This capability would be extremely valuable for streamlining workflows. Currently, when similar actions need to occur with only a minor variation based on a condition, it can result in unnecessarily complex and difficult-to-manage workflow structures. For example, when a single condition determines whether an additional step (such as sending a notification based on a condition) is required, the rest of the workflow often remains identical, but must still be duplicated across both branches.

Having a more efficient way to handle conditional steps without duplicating large portions of the workflow would significantly improve maintainability and reduce complexity.

Subflows is the way to go as of now. But it has limit of 25 nodes per subflow and I think 20 subflow nodes in a normal workflow. 

Not a freshworks employee. However I will add to Daniel's comment above. 

As with the majority of SaaS companies with the GPT revolution that started a couple of years ago, it appears that most of their development resources have been targeting AI and integrating it into the product so it can stay as competitive as possible amongst everybody else doing the same. 

One of the bonuses of this is their advertised agentic workflow builder which may reduce some of the overhead involved in creating workflows with repetitive nature such as this. Only time will tell🙂

These 2 requests should be joined together. I really hope this gets added, subflows is limited.
Join workflow modules together | Freshworks Community

This would be super useful as we had complex workflows that have repeated steps.

Can do that sort of with subflows, there are limit on number of subflows per flow and number of nodes in a flow. 

Yeah but what happens when the subflows fail and we dont know why? Same problem of not moving on or telling it that it can move on.

We need better logging that is true :) FW have talked about that but don’t know when. 
I add error handling to all app actions and web requests actions (Don’t use the web hook action in the action node) 

Rerun a flow can be done, you need to build it in the flow when you design the flow. Use tags, check boxes and so on to trigger the flow again. 

Then subflow can come in real use, each subflow sets a tag when it’s running, like Start and end tag (remove start at the end of the sub flow). When you rerun the flow each subflow has a condition that check the tag, if the endtag is there it skips the step. But there are limitations and it can get tedious editing subflows.