+1Within a workflow I may want to take different actions based on a condition however later actions may be common regardless of result of that condition.
My idea is functionality be added to allow modules (action/condition etc) within a workflow to be joined together with connectors manually.
Image below demonstrates a simple example. Were I able to add the green ling the action within the red box could be deleted as it’s a duplicate of the line above.
+5I will admit...the limitations around looping and inability to add business logic has caused us to look at other solutions for automation outside of Freshservice. We now use freshservice as the initiator utilizing the web request node to make an API call that runs automatons we have in another tool. We created a custom field on our ticket form that agents can use to select an automation they want to run on a ticket. This will trigger a freshservice workflow that grabs information from the ticket and sends it in the request to another third party automation tool where we are able to use python scripts with looping and business logic, then write back to the ticket with those updates. This has worked well for us while we wait for Freshservice’s WFA functionality to catch up. Fingers crossed, that the new features mentioned get added sooner rather than later.
Very curious on the tool, is it workato? it would be largely beneficial to have forked/conditioned branches to be able to reference nodes from another branch. This would eliminated the need to duplicate nodes and from having to create additional subflows. Specially considering each workspace is limited to automated workflows and each workflow is limited subflow nodes and subflows are limited to nodes in general.
There is a similar request here.
Workflow Automator | Freshworks Community
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
