/ Docs
Vendor Integrations

Docebo

Last updated October 13, 2025 · View as Markdown

Docebo_Logo.jpeg Docebo is a cloud-based eLearning solution and learning management system (LMS) that can facilitate training for your employees, partners, and customers. Docebo is easy set up and maintain, being one of the most significant benefits.

In order to integrate Docebo with Relyance AI you will need your Docebo Subdomain, Client ID, a Client Secret, and need to follow an OAuth2 flow.

This integration requires Superadmin permissions in order to access all available endpoints. Please see https://help.docebo.com/hc/en-us/articles/360020082940-User-levels-roles-and-statuses for more info.

In Docebo:

  1. Login to Docebo.

  2. Navigate to your Docebo Admin Panel.

  3. If the API and SSO app is present, click Manage and proceed to step 5 of this document. Otherwise, select Add New Apps.

  4. Click the Third Party Integrations tab, then click Try it for free next to the API and SSO app.

Docebo-2.png

  1. Click the gear icon next to the API and SSO app to configure.
  2. Select API Credentials and click Add Oauth2 App.

Docebo-3.png

  1. Create a name and description for your integration. Copy the Client ID and Client Secret to enter into the Relyance app.

i. Enter https://root.relyance.ai/api/oauth2 for the redirect URL ii. In advanced settings, ensure Authorization code + Implicit Grant is selected.

Docebo-4.png

  1. Enable the OAuth2 App by selecting the check mark next to the app.

Docebo-5.png

  1. Your Docebo Subdomain will be the web URL that you use to log into Docebo.

Docebo-8.png

In the Relyance AI application:

  1. Login to your Relyance account.
  2. Navigate to the Settings Menu in the bottom left-hand side.
  3. Select Integrations.
  4. Click on the Vendor Integration tab.
  5. Find the Docebo integration card and click it to open its connections.
  6. Under Authentication Method, choose Oauth2 / App Token.
  7. Paste the Docebo Subdomain, Client ID, and Client Secret into their respective fields.

Docebo-6.png

  1. Click Save.
  2. This will bring you to Docebo to authorize your integration. Click AUTHORIZE in the resulting dialog box.
  3. At this point, you should see the following result on the Vendor Integrations page:

Docebo-7.png

  1. Congratulations, you are now connected to Docebo.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

  1. Authorised, then empty. The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
  2. A credential rotated at the vendor is not picked up here. Client Secret is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
  3. Check the address fields before suspecting the credentials. Docebo Subdomain identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example docebo/<connection_id>) or reading it with the relyance_integration_connection data source.

← Previous
Detectify