Docebo + ReadyTech Axis: virtual lab integration for Spanish SMEs
For a Spanish SME running Docebo as the LMS — typically 50-200 learners with at least one programme that needs hands-on technical practice (a developer onboarding track, a security-operations training, a cloud-platform certification path, an industrial-controls familiarisation course) — the question of where the practice happens has historically forced a choice the L&D lead would rather not make. Spin up real infrastructure and absorb the cost of unused VMs sitting idle between training sessions, or skip the hands-on element and accept that the learners will graduate the programme without ever having touched the system they are supposed to operate. ReadyTech Axis integrated with Docebo Connect is the answer that removes the choice. Virtual labs are provisioned on-demand from Docebo enrollments, embedded directly inside Docebo courses, and tracked in the same reporting view as the rest of the learner’s progress.
What the integration does — embedded labs, auto-provisioning, unified tracking
The Docebo + ReadyTech Axis integration delivers three operational behaviours the SME’s L&D lead and integration owner should know how to use.
Embed virtual labs directly in Docebo courses is the learner-facing benefit. The Axis lab — a pre-configured environment with the operating system, applications, and starting state the lesson requires — appears inside the Docebo course as a course widget. The learner clicks “Start Lab” inside Docebo, the lab spins up in a separate browser pane, and the learner does the hands-on work without ever leaving the Docebo learning context. The pattern eliminates the friction of “now switch to this other tool to do the practical part” that depresses completion rates on hands-on programmes.
Automate lab provisioning based on Docebo enrollments is the operational benefit. When a learner enrols in a course that has an associated Axis lab, the integration automatically provisions the lab environment — no manual ticket to the IT team, no shared lab account that breaks when two learners log in at the same time. When the learner completes the course or the enrollment expires, the integration tears the lab down. The pay-per-use cost model means the SME pays for lab capacity actually consumed, not for VMs sitting idle.
Track ILT attendance + virtual lab completion in one place is the reporting benefit. The integration writes lab-completion events back into Docebo, so the L&D lead’s existing Docebo reports — completion rates by course, time-to-completion by branch, cohort comparisons — include the hands-on work alongside the video views and the quiz scores. For a Spanish SME under INCIBE supply-chain expectations on documented training governance, the unified reporting view is the documentation surface that proves “the learners actually did the practical work” rather than “the learners watched the video.”
Prerequisites — what the SME needs before the integration is configured
The integration requires both a Docebo and a ReadyTech Axis account configured to talk to each other. The integration owner should confirm the prerequisites before the configuration session begins.
ReadyTech side:
- ReadyTech Axis account with API access enabled (some plans require an upgrade)
- API Key and API Secret generated in the ReadyTech admin console
- ReadyTech instance URL (typically
https://api.readytechlabs.com, but enterprise customers have dedicated subdomains) - Admin access to the Axis tenant for lab template configuration
Docebo side:
- Docebo Superadmin access
- Docebo Connect activated on the platform (some Docebo editions require an add-on)
- Course-widget configuration permission to embed third-party content in courses
- Custom lookup tables capability to maintain the Docebo-course-to-Axis-lab-template mapping
Cross-platform:
- A confirmed mapping spec describing which Docebo courses correspond to which Axis lab templates — typically a 5-10 row table the L&D lead and the lab content owner agree on before any technical work starts. The mapping spec is the artifact that prevents the “we provisioned the wrong lab template for this course” failure mode that catches teams who configure the integration without it.
For a Spanish SME under EU AI Act Article 13 transparency expectations on AI-augmented training workflows, the documented mapping spec — what lab template runs for what course, who approved the mapping, when it was last reviewed — is itself part of the audit surface.
The five webhooks — what gets sent where, and why each one matters
The integration is wired through five webhooks between Docebo, Workato (the Docebo Connect runtime), and ReadyTech. The integration owner should know what each does because each is the failure point when a specific behaviour stops working.
| Webhook | Direction | Trigger | Purpose |
|---|---|---|---|
| Enrollment Created | Docebo → Workato → ReadyTech | Learner enrols in lab-enabled course | Provision lab instance for the learner |
| Enrollment Completed | Docebo → Workato → ReadyTech | Learner completes the course | Tear down lab instance, free capacity |
| Lab Started | ReadyTech → Workato → Docebo | Learner clicks Start Lab | Log session start time in Docebo |
| Lab Completed | ReadyTech → Workato → Docebo | Learner finishes lab tasks | Write completion event to Docebo course progress |
| Lab Expired | ReadyTech → Workato → Docebo | Lab session times out | Log expiry, surface to learner for retry |
The five-webhook architecture is symmetrical — two events flow from Docebo to ReadyTech (provision and teardown), three events flow from ReadyTech back to Docebo (started, completed, expired). The bidirectional flow is what enables the unified reporting view: Docebo knows about the enrollment, ReadyTech knows about the lab session, and the webhooks keep both sides in sync without the integration owner needing to reconcile manually.
The failure modes the integration owner should watch for are predictable. Enrollment Created not firing means new enrollees do not get a lab — typically a Docebo Connect connection issue, fixed by re-authenticating the connection. Lab Completed not firing means completed labs do not show in Docebo reports — typically a ReadyTech webhook delivery issue, fixed by reviewing the ReadyTech webhook configuration. Enrollment Completed not firing means torn-down labs continue to consume billing — typically a Docebo course-completion-rule misconfiguration, fixed in the Docebo course settings. The 30-minute monthly review of webhook delivery logs (in both Docebo Connect and ReadyTech) is the discipline that catches each failure before it becomes a billing surprise or a learner complaint.
For a Spanish SME accessing Kit Digital IA/BI vouchers — Segment III (10-50 employees) up to €12,000, Segment II (3-9 employees) up to €6,000 — the integrated Docebo + ReadyTech Axis setup with documented mapping spec, configured webhooks, and monthly review cadence is the deliverable that turns “we want to add hands-on labs to our training” into “we have hands-on labs running with documented operational governance.” The Agente Digitalizador can configure the integration, ship the mapping spec template, and hand the L&D lead a workspace that runs hands-on programmes without IT-ticket overhead. The official ReadyTech Axis integration reference lives at help.docebo.com and the broader product context at docebo.com.
Ready to get started?
Working on this yourself? J4SGON S.L. delivers Docebo Connect, HRIS, SSO and migration work for European organisations — see what a scoped engagement covers or describe your project and we will reply with a written scope.
Tell us what you are integrating or migrating
Send the platform, the systems involved and where you are stuck. You get a written scope back — phases, deliverables and what is out of scope — before anything is billed.