Hi everyone,
We are currently migrating to Freshservice and building several large and complex workflows.
During this process, we’ve noticed a major limitation — when different condition branches require the same action, we need to duplicate that action node multiple times.
This makes workflows harder to maintain, more error-prone, heavier to load and manage and time-consuming to update when something changes
In most modern automation platforms, this is solved with a “Looping” or “Shared Action” capability — allowing multiple conditions to connect to the same action node instead of duplicating it.
I understand from support that this feature is planned for mid-2026, but given how impactful it is for real-world workflows, I believe it deserves higher priority.
This improvement would simplify workflow design dramatically and help many teams migrating to Freshservice.
💡 Suggestion:
Please consider accelerating the release of the “Looping” feature to early 2025 or make it available under Early Access / Beta for customers facing complex automation use cases.
Would love to hear from others — is anyone else facing the same pain with duplicated actions?
Thanks,
Gabriel
