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.
The purpose of this article is to help you familiarize yourself with terminology used throughout Docebo Connect.
For more information about Docebo Connect, please visit Docebo Connect.
Glossary of Terms
- Carry out specific predefined operations in the target application (e.g. API).
- Docebo Connect needs to be authorized to communicate with other 3rd party solutions, using the app's API, and it may require OAuth-based authorization, API keys, etc; this authorization is referred to as a connection.
Allows Docebo Connect to interact with other 3rd party applications through a series of triggers and actions. Possible connector types are:
- Community Connector
- If a Global-Scope / Prebuilt connector is not available for your integration project, with Docebo Connect you can access the Community Library where you can choose from hundreds of connectors developed and maintained by the Workato network partner.
- Global-Scope / Prebuilt
- Off-the-shelf Connectors ready to use, developed and maintained by either Docebo or Workato.
- SDK Connector
- If the connector you need is not available in Docebo Connect as not as Global-Scope / Prebuilt or from the Community Library, you can create your own custom connector. Please note: to do so requires some knowledge of Ruby.
- Lookup Table
- Lookup tables (similar to cross-reference tables) let you lookup frequently used data easily in a recipe. Data in lookup tables is typically organized like in a database table, with columns and rows of data. You can find an entry within the specified lookup table by matching against data in one or more columns.
- Account properties allow you to store account-wide recipe configuration parameters. They show up in all recipes as usable values under the Properties data-tree.
- Recipes are automated workflows built by users that can span multiple apps.
- Monitor events that occur in the application you hope to connect to and kickstart a workflow of actions that we call recipes (for example, Webhooks).