Context:
We have multiple environments. For example, stage and production. Sometimes we need to modify or test a workflow without affecting production. While we can publish versions, we’d like to test changes in one environment first and then promote them to production.
Issue:
It seems that Retool workflows don’t support maintaining multiple active versions or environment-specific configurations. While resources can have environments, workflows themselves can only have a single version at a time. Additionally, each Retool webhook used to trigger workflows generates a different secret key, even when both workflows belong to the same environment. This makes secret management more difficult.
Current Approach:
We’re creating separate workflow instances to handle this setup:
-
Stage workflow 1
-
Production workflow 1
-
Stage workflow 2
-
Production workflow 2
This allows us to:
-
Have different webhook URLs for each environment
-
Modify resource details in one environment without affecting the other
Questions:
-
Is there a recommended or built-in way to manage multiple workflow versions or environment-specific configurations without duplicating workflows?
-
Is there a way to define or reuse a single webhook trigger API secret for multiple workflows, or to manage it through Retool’s configuration variables, to simplify secret maintenance?
