+3We have a serious need for the ability to use placeholders within the action node for adding a name for the approval groups. Without this, we are having to run additional API requests; 1x to GET the approval groups, 2x to GET 2 different custom objects, and another to PUT or POST either creating the approval group or update the approval group. This would be a huge performance saving feature.
+1Not being able to use dynamic placeholders for approval group names forces unnecessary API calls, which adds latency and complexity to workflows. Having to chain multiple GETs and then a PUT/POST just to handle something that could be resolved inline is definitely not efficient.
A placeholder-based approach would streamline the process, reduce API load, and significantly improve performance especially for larger or more complex automations.
Really hope this gets considered, as it would make a noticeable difference in real-world use cases.
+3Not being able to use dynamic placeholders for approval group names forces unnecessary API calls, which adds latency and complexity to workflows. Having to chain multiple GETs and then a PUT/POST just to handle something that could be resolved inline is definitely not efficient.
A placeholder-based approach would streamline the process, reduce API load, and significantly improve performance especially for larger or more complex automations.
Really hope this gets considered, as it would make a noticeable difference in real-world use cases.
MrJohn, don’t forget to upvote. Thanks for your input!!! I’m glad I’m not alone.
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.