Introduction

Docebo Connect is a Docebo module acting as a connector between your platform and third-party SaaS systems, helping you to integrate your platform with more than 400 third-party external systems, reducing the integration effort.

Docebo Connect offers a large catalog of connectors for the most popular SaaS systems, to manage automated workflows (called recipes) shared among systems in order to exchange and share data on the basis of triggers.

Please note that Docebo Connect takes advantage of the APIs and business logic already existing in the integrating systems and does not create new ones. In addition, Docebo Connect does not manage SSO flows with Identity Providers (such as SAML, OpenID Connect, etc), JavaScript integrations (such as Google Analytics or Google Tag Manager) or iframe integrations (such as Docebo OEM or Salesforce Canvas).

The purpose of this article is to explain how to correctly copy Docebo Connect recipes and update the recipes in order for them to properly call the newly copied sub-recipes. This is done in order to allow for possible customization of the recipes to not be automatically overwritten when new versions of the recipes are released by Docebo.

For more information on the definition of terms and concepts used throughout this article, please read Docebo Connect Glossary of Terms.

Warning: The default Docebo connector must never be moved, renamed or deleted. Doing so may render your recipes non functional or even disable the connection to your platform.

Copying Docebo Connect recipes

Docebo Connect Recipes are distributed in an example folder. These recipes should not be used from their default location as any customizations and configurations performed on them will be overwritten in the event of an update being released by Docebo. Instead, before their first use and configuration, the recipes should all be copied to a new location, taking care to preserve the existing folder structure.

As recipes in Docebo Connect can contain calls to other recipes (or sub-recipes), once all the recipes have been cloned to a new location, every recipe that contains a call to a sub-recipe will need to be edited in order to point the call to the new location of the cloned sub-recipe.

For example, if recipe "A Original" calls recipe "B Original" then the first step is to clone both recipes. Now we have recipes "A Clone" and "B Clone" in the new location as well as recipes "A Original" and "B Original" in the example folder. Without editing the cloned recipes, the new recipe "A Clone" will continue to call recipe "B Original" and not "B Clone". The help center article for each specific integration contains a list of recipes and, where applicable, the sub-recipes that are called in order to help you locate which recipes will require editing prior to configuring and running.

Please note: If a new version of a recipe is released into the Example folder by Docebo, you will be notified that a newer version of your cloned recipe is available for use. In the event that you choose to update to the new version of the recipe, you will need to reconfigure the sub-recipes being called by the new version after updating. If multiple recipes in the same integration are being updated, Docebo recommends updating all the recipes first and then updating all the recipe calls prior to running the new versions.

Cloning a recipe

Access Docebo Connect by pressing the admin (gears) icon in the top right corner of your screen, locate Docebo Connect and press Manage. Then, locate the recipe in your project folder and press the ellipsis button and choose Clone Recipe.

You will then be brought into the recipe editor for the cloned recipe where you can make optional changes and test your recipe. It is recommended that you skip this step until you have cloned all the recipes available for an integration.

Please note: Docebo recommends recreating the folder structure of your original recipe in a different folder, next move the cloned recipe into the folder corresponding to the original location and rename the cloned recipe to match the original recipe.

To move your new recipe into a different folder, simply grab the recipe by its handle located on the left side of the recipe and drag it to its new location in your project folder tree in the left side menu. Once you have moved the recipe, you can rename it by pressing the ellipsis button at the end of the recipe and choosing Rename recipe.

Please note: Docebo recommends leaving the "Copy of…" recipe name in place as it will make locating the new recipe easier when editing the links to the new recipes easier at a later stage.

Editing the cloned recipes

After you have cloned all the recipes in the example folder and moved them into your new folder, you will need to edit the recipes and point all calls for sub-recipes to the newly cloned recipe instead of the original. To do so, press the ellipsis button at the end of the recipe and choose Edit recipe.

Next, in the Recipe Editor, scroll down to the element that calls a different recipe and press the element. Then, in the resulting slide-in window, press on the Recipe to call drop-down menu.

In the resulting drop-down menu, select the new recipe you would like to call instead of the example recipe. If you did not rename the cloned recipe, you will be able to identify the difference between the example recipe and the cloned recipe from the name in the list by the recipe name starting with "Copy of".

Once you have updated all the calls to sub-recipes within the recipe, you can press the Save button in the top right corner of the recipe editor.

Please note: You will need to repeat this process for every recipe in the integration you have cloned.