Workato offers multiple dev environments, so you can develop recipes in a lower environment and release to production or other interim environments. I think whether you have access depends on your subscription/contract. It might only be available for embedded customers. That said, this is probably a bigger solution than you need.
On a smaller scale, you can create your recipes to determine the environment and behave accordingly. How to do this is up to you, but here's a simple method:
- Create your main recipe as a function recipe with a required input called "environment"
- Create a recipe that triggers from your sandbox. This calls the main recipe and identifies the environment as "sandbox"
- Create another recipe that triggers from production. This recipe calls the main recipes with "production"
- In your main recipe, create any number of conditionals to alter the behavior based on the "environment" value
We use this method regularly for the exact reason you described. If environment == production, email the real contacts, if environment == sandbox, email internal addresses.
On a side note, our trigger recipes rarely do all of the processing. They almost always call a separate function recipe, or route the incoming trigger to the appropriate recipe. This helps tremendously with troubleshooting, re-running, and keeping your processing recipes specific, modular, and not monolithic monsters.
Hope this helps!
