Installing an existing Workato recipe makes a copy of it in your Workato account. Only the logic/steps of the recipe(not the data) will be transferred. If you aren't already connected with the apps, simply connect the apps with your own account and you're good to run the recipe. You may want to check through the recipe; however, to see if the information properly mapped, or the input fields in the recipes are appropriate with your use case.
For example, if the recipe has an input field to send a message through email, you may want to edit the message field. Pay special attention to fields with a red outline, these may be because of customized fields or objects in the original recipe. If you have trouble running an installed/cloned recipe, check out another article that talks about 'Why doesn't my cloned recipe work?'.
You can install other users' public recipes, or any of your own recipes. Private recipes cannot be cloned because they will not be visible to you, unless the author has explicitly shared it with you by giving you the sharing token.
You can also clone your own Draft recipes. This is useful when you are building and testing your recipes and don't have them running successfully yet while not wanting to change the original.
How to Install/Copy a Recipe:
1. Click on 'Install'
2. Follow the recipe install wizard to successfully install the recipe in your account.
i) Hook up your app connections, and hit 'Next'
ii) Review the recipe
Recipes sometimes use data fields and objects that are custom to the author’s app. e.g. custom fields added to standard objects like Customer or Invoice. This step checks to see if there are fields used by this recipe that is not available in your app.
Sometimes, you may meet with data field errors during the installation process. This is because the recipe uses some data fields or pills that do not exist in your app. Follow the instructions and re-map the data fields in the respective lines.
There are two ways to fix these errors:
a) Go to your app to create the missing fields. After you have added the missing data in your app, we recommend that you click on 'refresh schema' so the recipe can pick up the updated changes.
b) Alternatively, you can remove the data fields in the recipe if you don't wish to use them.
Even if there are no data field errors, we recommend that you should still check every recipe step to ensure that the data mappings are exactly the way you want.
Hit 'Next' when you're happy with the data mappings in your recipe.
3. Test the recipe
Our test recipe feature allows you to test your recipe setup by only running one job. It picks up the data, depending on the recipe start time you've configured. It also allows you to see if the correct data are mapped across the apps.
To see what the recipe has picked up, check the 'Job History' section.
Click on each of the job to see what the recipe has processed. You can also click on each step of the job report to see exactly what data was passed into and out of the app.
If your recipe was not set up well, you will receive an error that will tell you how to troubleshoot the recipe. Refer to this support article to understand how to troubleshoot recipes.
If you still require help with your recipe, please file a ticket on our success centre here.