Skip to main content
Question

Docebo Connect Feedback

  • January 7, 2026
  • 1 reply
  • 45 views
L
Novice I

Happy New Year, everyone!

Our company is currently in the process of selecting a new HRIS, and we are looking to move away from SFTP toward a more automated API-driven approach. As part of this transition, we are evaluating Docebo Connect to bridge the gap.

I’m relatively new to the technical side of APIs, but I am working on building a business case for Connect. I’d love to hear from those of you currently using it.

  • How has your experience been with "recipes" and maintaining the sync?
  • Are there things you wish you knew before implementing?
  • For those who chose Connect over a standard custom API build, what was the deciding factor for your business case?
  • What are you using Connect for? Was it worth it?

Our potential use cases:

  1. Bidirectional HRIS Sync: Automating user creation & profile updates and potentially sending completion data back to the HRIS.
  2. Outlook/ILT Integration: Sending automated calendar invites for ILT/VILT sessions without manual input.

There could be more, but as I mentioned I’m unfamiliar with this area. If you have any "lessons learned" or tips on how to present this to leadership, I would greatly appreciate it!

1 reply

hailey.gebhart
Helper III

For my company, using Connect is a large portion of our job, and it has been a game changer for us.

  • How has your experience been with "recipes" and maintaining the sync?
    • If you set it up thoughtfully and intentionally, it is way better than any sort of upload/input. You can create the changes and updates in real-time, or close to. This is also a little dependent on your implementation, API options for your specific HRIS, and other data sources, such as an SSO. All of these can complicate your implementation and data flow. However, if your goal is straightforward is gathering user data from the HRIS and sending certain data back, you will be golden.
    • The webhook functionalities are your friend for this case. 
  • Are there things you wish you knew before implementing?
    • You get charged based on the number of connections you have. 
    • Although the solution is marketed as “low code,” it is extremely helpful to have someone who has at least general programming experience (specifically working with APIs and JSON files) to get it up and running. You need the mind of a programmer to make your implementations run smoothly.
    • Connect is actually a Workato Embedded instance, and they also have an entire community and a multitude of support documents.
    • You are on your own for implementation. If you are having issues and it relates to your automation even a little bit, be aware that Docebo will do everything they can to have you use PS hours.
    • The API calls for your connected items are only as good as the API functionality of your connected items. If support and documentation on the other end it minimal, your task becomes much harder.
  • For those who chose Connect over a standard custom API build, what was the deciding factor for your business case?
    • We had a lot of use-cases that would not be possible without an API. When we would reach out about our situations, we would get many responses along the lines of “but you CAN do it with an API.”
  • What are you using Connect for? Was it worth it?
    • We use Connect for a wide variety of topics. Including but not limited to,
      • Our HRIS.
      • Our email marketing platform.
      • User management
      • Course creation management
      • Certification enhancement
      • In short, if you can dream it (and there are API options in Docebo), you can do it.

Once again, I absolutely recommend Connect. It is wwaaayyy easier and more centralized than implementing the APIs yourself (or using IT resources to do so). I now do not offer solutions to problems that would require API development outside of Connect. In addition, there are a lot of experts in the community here you can provide you a lot of guidance as you learn more about it and implementation.

Terms & ConditionsCookie settingsAccessibility statement