Workflow Versioning
When handling client-based requests (from an app), it could be helpful for me to "version" my workflows, so that when I ship a major update to the client, the endpoint url could be versioned (buildshipurl.com/v2/nodename). That way, if I make breaking changes to the workflow at a later date, I won't break my client requests for those still using the older version.
Solution:
Jump to solution
Hi @swipe, great suggestion 👍 , we can look further on dynamically workflow versioning of deployments endpoints, for now if you are using a RestAPI Call Trigger, you can crate separate workflow and manually set the path.

1 Reply
Solution
Hi @swipe, great suggestion 👍 , we can look further on dynamically workflow versioning of deployments endpoints, for now if you are using a RestAPI Call Trigger, you can crate separate workflow and manually set the path.
