Ellipse Gradient for Header

Docebo Integration Guide

Integrate Docebo with enterprise systems through REST APIs, selected webhook notifications, OAuth 2.0 authentication, and Martini workflows.

Docebo integration options at a glance

Docebo’s primary integration surface is its REST API, which supports users, courses, enrollments, learning plans, catalogs, sessions, certifications, and reporting operations. Docebo also provides webhook or event-notification capabilities for selected events, subject to tenant configuration and enabled features. OAuth 2.0 and access-token authentication protect API access. Martini can consume these APIs, receive selected webhook-style notifications, expose normalized REST APIs, and orchestrate scheduled synchronization workflows. Pagination, controlled batching, retries, and reconciliation support reliable processing where dedicated bulk endpoints or complete event coverage are unavailable. Reporting data can be normalized and delivered to downstream operational or analytical systems.

Integration pointSupported by Docebo?Common use casesHow Martini supports it
REST APIsYesCreate, update, and retrieve Users; read Courses, Catalogs, Learning plans, ILT sessions, Enrollments, Certifications, and Reports; and perform administrative learning operations.Martini can consume Docebo REST endpoints, map JSON payloads, apply business rules, and expose a normalized REST API for downstream applications.
Webhooks / outbound callbacksLimitedReceive notifications for selected Docebo platform events when enabled and configured in the tenant.Martini can receive webhook-style HTTP requests, validate them, acknowledge promptly, re-query Docebo for authoritative state, and route processing to workflows.
Bulk / async / batch APIsLimitedProcess higher-volume administrative or learning data where a dedicated batch operation exists for the specific resource.Martini can use documented batch operations when available and otherwise implement pagination, bounded batches, checkpoints, and controlled concurrency.
File / attachment APIsLimitedAccess learning-content or file resources where the particular Docebo resource exposes supported file operations.Martini can process supported file responses and transfer content, but each resource must be verified rather than treated as a general attachment API.
Reporting and data extractionYesExtract learning, enrollment, completion, certification, or user information for operational reporting and analytics.Martini can consume report output, normalize it, and load it into a warehouse or operational application without assuming direct database access.
AuthenticationYesAuthenticate API clients using OAuth 2.0 and access tokens configured for the Docebo tenant.Martini can store client credentials, token endpoints, instance URLs, and other environment-specific values as secrets and use authorization headers in API workflows.
Database accessNoDirect customer database access is not assumed for Docebo integrations.Martini should use Docebo APIs, webhook mechanisms, and documented reporting or export facilities instead of direct database connectivity.

How Docebo exposes data and business events

Docebo REST APIs

REST APIs are Docebo’s primary documented programmatic integration surface. They support operations across Users, Courses, Enrollments, Learning plans, ILT sessions, Catalogs, Certifications, and Reports, although exact resources and fields depend on API version and tenant configuration.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates with the configured OAuth 2.0 access token, calls the required Docebo endpoint, handles pagination and response validation, maps the result to a canonical model, and writes to the target system or returns a normalized API response.

Implementation sequence

Authenticate with the configured Docebo OAuth 2.0 credentials
Retrieve the required Docebo resource or changed page
Validate the response and pagination metadata
Map fields to the canonical integration model
Apply business rules and identity correlation
Write the result to the target system or API response

Docebo Webhooks

Docebo supports webhook or event-notification capabilities for selected platform events. Coverage is not universal across all objects or state changes and depends on enabled features and tenant configuration.

Martini implementation pattern

Martini implementation pattern: an inbound workflow receives and validates the notification, acknowledges promptly where appropriate, identifies the affected object, retrieves authoritative state from Docebo, and forwards a normalized event after deduplication and business-rule evaluation.

Implementation sequence

Receive the Docebo webhook notification
Validate configured authentication or request-signing information
Record an event identifier or deterministic fingerprint
Retrieve the current Docebo resource when the payload is incomplete
Map the event to the enterprise event model
Deliver the event and route failures for retry or reconciliation

Docebo Reporting and Extraction

Docebo reporting and data-extraction capabilities can provide learning, enrollment, completion, certification, and user information for downstream reporting or operational processes. This is application-level access rather than direct database access.

Martini implementation pattern

Martini implementation pattern: a scheduled workflow retrieves report output or supported API data, applies incremental or rolling extraction logic, normalizes the results, and loads them into a warehouse or enterprise application while recording checkpoints.

Implementation sequence

Start the extraction on a schedule
Retrieve the report or supported API result
Process pages or bounded batches
Normalize dates, identifiers, and status values
Load the data into the target system
Store the checkpoint and reconcile missed or changed rows

Docebo Batch Processing

Dedicated bulk or asynchronous behavior may exist for selected Docebo operations, but it should not be assumed for every resource. Pagination and controlled batching provide a fallback for high-volume synchronization.

Martini implementation pattern

Martini implementation pattern: a workflow selects a bounded page or batch, applies controlled concurrency and backoff, records successful checkpoints, and routes validation or transient failures separately so one bad item does not fail the entire synchronization.

Implementation sequence

Select the resource and bounded batch size
Retrieve or submit the documented batch operation
Process successful items and store correlation keys
Retry throttled or transient failures with backoff
Route permanent failures to an exception workflow
Run periodic reconciliation against Docebo

Common Docebo integration patterns

Pattern 1: Synchronize employees to Docebo Users

When to use this pattern

Use this pattern when an HR or identity application is the source of truth for learner populations. It supports scheduled incremental synchronization, validation of required identity fields, and safe create-or-update behavior.

Integration direction
Workday
Martini
Docebo
Example Mapping
Docebo FieldCanonical FieldTarget Field
workerIdexternalUserIdDocebo User external identifier
emailemailAddressDocebo User email
departmentorganizationUnitDocebo User department
activeisActiveDocebo User status
Martini implementation pattern

A scheduled Martini workflow retrieves changed workers, validates and normalizes identity data, looks up an existing Docebo User by a stable key, and creates or updates the user. Business rules determine eligibility and role mapping; failures are logged, retried where transient, and reconciled later.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data mapping
  • business rules
  • validation
  • error handling

Pattern 2: Synchronize enrollments and certifications

When to use this pattern

Use this pattern to deliver learning outcomes to HR, CRM, compliance, or service processes. Scheduled reconciliation remains useful even when selected event notifications are enabled.

Integration direction
Docebo
Martini
ServiceNow
Example Mapping
Docebo FieldCanonical FieldTarget Field
userIdlearnerIdServiceNow learner reference
courseIdlearningItemIdServiceNow course reference
completionStatuslearningStatusServiceNow compliance status
certificationExpiryexpiresOnServiceNow expiration date
Martini implementation pattern

Martini retrieves paginated Enrollments and Certifications, correlates them to downstream users and learning items, applies completion and expiration rules, and writes updates to ServiceNow. Stable identifiers, checkpoints, retry queues, and periodic reconciliation protect against duplicates and missed changes.

Martini capabilities used
  • scheduled workflows
  • pagination
  • data transformation
  • correlation
  • business rules
  • retry handling

Pattern 3: Process selected Docebo webhook events

When to use this pattern

Use this pattern when a required Docebo event is available and near-real-time processing is valuable. It should be combined with polling or reconciliation for unsupported events and recovery from missed notifications.

Integration direction
Docebo
Martini
Salesforce
Example Mapping
Docebo FieldCanonical FieldTarget Field
eventTypeeventNameSalesforce platform event type
userIdlearnerIdSalesforce contact or user reference
objectIdlearningObjectIdSalesforce course or enrollment reference
occurredAteventTimestampSalesforce event timestamp
Martini implementation pattern

An inbound Martini workflow validates the notification, records a deduplication key, and retrieves the latest Docebo object rather than relying solely on the event payload. It maps the authoritative state to Salesforce, applies routing rules, acknowledges quickly where required, and sends failed deliveries to retry or reconciliation processing.

Martini capabilities used
  • webhook consumption
  • API consumption
  • event orchestration
  • deduplication
  • data mapping
  • error handling

Pattern 4: Publish Docebo catalogs and courses

When to use this pattern

Use this pattern to present active Docebo learning content in an employee portal, collaboration application, or analytics platform. It is suitable for scheduled catalog refreshes and change detection.

Integration direction
Docebo
Martini
Microsoft Teams
Example Mapping
Docebo FieldCanonical FieldTarget Field
courseIdlearningItemIdTeams content reference
titlenameTeams displayed title
durationdurationTeams learning duration
statuspublicationStatusTeams availability status
Martini implementation pattern

A scheduled Martini workflow retrieves Courses, Learning plans, and Catalogs, excludes inactive content, normalizes metadata, and publishes changes to the target. Timestamps or hashes detect changes, while a cross-reference prevents duplicate publication and an exception path handles invalid content.

Martini capabilities used
  • scheduled workflows
  • pagination
  • mapping and transformation
  • change detection
  • business rules
  • exception handling

Applications commonly integrated with Docebo

Docebo can be integrated with adjacent enterprise applications to synchronize identities, learning assignments, completion outcomes, notifications, and compliance information. Exact objects, actions, and product-specific capabilities should be validated against the customer’s Docebo edition and configuration.

Application Scenario Direction Martini Pattern
Salesforce Synchronize learner, customer, partner, and sales-enablement information with Docebo learning records and return completion or certification status to CRM processes. Salesforce → Martini → Docebo Martini retrieves Salesforce users or learning-relevant changes, validates and maps them to Docebo Users, and uses create-or-update REST operations. A reverse workflow retrieves Docebo Enrollments and Certifications and maps them to Salesforce objects with correlation keys and retry handling.
Workday Align employee populations and organizational attributes with Docebo and return learning completion or compliance outcomes to HR processes. Workday → Martini → Docebo A scheduled Martini workflow retrieves changed workers from Workday, normalizes identity and organizational fields, and synchronizes Docebo Users. A second flow extracts completions and Certifications for Workday or an HR reporting process, using checkpoints and reconciliation.
Microsoft Entra ID Support identity lifecycle and access management for Docebo users through the customer’s selected provisioning and sign-on design. Microsoft Entra ID → Martini → Docebo Martini can orchestrate supported identity and Docebo API exchanges, apply lifecycle rules, and protect tenant-specific credentials in secrets. Provisioning and protocol details must be confirmed for the selected Docebo setup.
Microsoft Teams Deliver learning notifications or content access through collaboration workflows where the selected Docebo and Teams capabilities support the scenario. Docebo → Martini → Microsoft Teams Martini receives or polls relevant Docebo status, applies notification rules, and sends normalized messages to Teams through its supported endpoints. Event and activity coverage should be validated before implementation.
Zoom Associate virtual instructor-led training with Docebo ILT sessions and reconcile session participation where supported. Docebo → Martini → Zoom A Martini workflow retrieves or receives relevant ILT session information, maps session identifiers and times, calls supported Zoom operations, and records processing outcomes. Attendance synchronization should be confirmed for the tenant configuration.
ServiceNow Send completion, certification, or compliance information into employee service and governance workflows. Docebo → Martini → ServiceNow Martini retrieves Docebo Enrollments, completion data, and Certifications, applies compliance rules, and writes normalized updates to ServiceNow. Failed items are isolated for retry and reconciliation.

How to build a Docebo integration in Martini

Objective

Configure the Docebo instance URL, OAuth 2.0 client details, token endpoint, and tenant-specific permissions without embedding secrets in workflow logic.

Instructions in Martini

  • Create environment-specific Martini configuration values
  • Store client secrets and tokens in secure secrets management
  • Confirm Docebo API user roles and resource permissions
  • Test authentication and token expiration handling

Objective

Select scheduled retrieval, a selected Docebo webhook event, or an inbound Martini API based on the required timeliness and event coverage.

Instructions in Martini

  • Use a scheduler for synchronization and reconciliation
  • Use webhook consumption only for confirmed Docebo events
  • Define an API trigger when another system initiates processing
  • Document fallback polling for missed or unsupported events

Objective

Call the relevant Docebo REST resource and process pagination, incremental filters, reporting output, or controlled batches.

Instructions in Martini

  • Retrieve Users, Courses, Enrollments, Learning plans, ILT sessions, Catalogs, or Certifications as required
  • Track pages, cursors, timestamps, or high-water marks
  • Limit concurrency and batch sizes
  • Preserve Docebo identifiers for correlation

Objective

Coordinate validation, enrichment, lookups, target writes, and exception paths in a maintainable Martini workflow.

Instructions in Martini

  • Separate transport, transformation, business rules, and target operations
  • Re-query Docebo after incomplete webhook notifications
  • Use reusable workflow logic for common authentication and correlation
  • Route permanent failures separately from transient failures

Objective

Convert Docebo payloads into the canonical model required by downstream applications while handling tenant-specific fields and statuses.

Instructions in Martini

  • Normalize names, email addresses, dates, identifiers, and status values
  • Map completion and certification states explicitly
  • Preserve unknown fields where practical
  • Validate required fields before target writes

Objective

Enforce eligibility, active-content, role, completion, expiration, and organizational rules before synchronizing data.

Instructions in Martini

  • Exclude inactive or archived learning content when required
  • Determine which users and learning items are eligible
  • Apply certification expiration and escalation rules
  • Use stable identifiers for idempotent processing

Common Docebo data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
UsersSynchronize learners, instructors, managers, and other platform users with HR, identity, or CRM populations.Workday, Microsoft Entra ID, Salesforce, ServiceNowMartini validates identity fields, maps organizational attributes, performs create-or-update operations, and preserves Docebo identifiers for idempotency.
CoursesSynchronize learning content, course metadata, delivery format, and completion requirements.Employee portals, Teams, Salesforce, data warehousesMartini retrieves and transforms course data, applies active or archived filtering, and maintains cross-references with downstream identifiers.
EnrollmentsTrack assignments, participation, enrollment state, and completion-related information.Workday, Salesforce, ServiceNow, compliance platformsMartini retrieves paginated enrollment data, maps statuses, applies reconciliation rules, and isolates failed records for retry.
Learning plansRepresent structured groups or paths of courses assigned to learners.HR systems, employee portals, reporting platformsMartini normalizes plan structure and course relationships, applies eligibility rules, and publishes supported fields to target systems.
ILT sessionsCoordinate instructor-led training sessions and associated event information.Zoom, calendars, collaboration platforms, reporting systemsMartini maps session identifiers, dates, instructors, and participation data where exposed by the relevant APIs.
CertificationsMonitor certification status, completion, expiration, and compliance outcomes.Workday, ServiceNow, Salesforce, compliance reportingMartini extracts certification status, applies expiration or escalation rules, and sends normalized updates with retry and audit handling.

Authentication and security considerations

OAuth 2.0 and access tokens

Docebo integrations generally use OAuth 2.0 and access-token-based API authentication configured for the tenant. The exact grant, scopes, and token behavior should be verified against the current tenant documentation.

Credentials and permissions

Martini can store client IDs, client secrets, token endpoints, instance URLs, and environment-specific values as secrets. Docebo roles, tenant permissions, branches, and groups determine which Users, Courses, Enrollments, Reports, and other resources are accessible.

Data protection

  • Use least-privileged API clients and users.
  • Keep tokens and client secrets out of payloads and logs.
  • Protect learner, completion, and certification data in transit and at rest.
  • Use separate configuration for different Docebo environments.

Operational considerations for Docebo integrations

Rate limits and pagination

Confirm tenant and endpoint limits, process paginated responses, use bounded concurrency, and apply exponential backoff for HTTP 429 and transient 5xx responses.

Idempotency and reconciliation

Use stable Docebo IDs and cross-reference tables for Users, Courses, Enrollments, sessions, and Certifications. Treat webhook deliveries as potentially duplicated and run periodic reconciliation to detect missed updates.

Webhook reliability

Validate configured webhook authentication, acknowledge promptly where required, record event fingerprints, and retrieve authoritative state when payloads are incomplete.

Schema and tenant variation

Fields and behavior can vary by API version, enabled modules, custom fields, and tenant configuration. Test mappings after configuration or API changes and preserve unknown fields where practical.

Testing and monitoring

Separate validation, authorization, throttling, and transient errors. Monitor workflow logs, capture permitted response details, and route failed records to retry or exception workflows.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration instead of isolated scripts

Martini coordinates Docebo API calls, webhook intake, scheduled reconciliation, target writes, and exception handling in maintainable workflows rather than scattering logic across scripts.

Reusable integration logic

Authentication, pagination, correlation, validation, mapping, and retry behavior can be implemented as reusable integration assets and applied across multiple Docebo flows.

Controlled enterprise interfaces

Martini can expose normalized REST APIs so downstream applications use a stable enterprise contract while Docebo-specific authentication, permissions, transformations, and business rules remain centralized.

Operational reliability

  • Support scheduled, event-driven, API-led, and batch processing patterns.
  • Separate transient failures from permanent validation errors.
  • Use checkpoints, deduplication, retries, and reconciliation.
  • Monitor workflows and troubleshoot integration behavior centrally.

Frequently asked questions

How can Docebo be integrated with enterprise systems?

Docebo can be integrated primarily through its REST APIs, OAuth 2.0 authentication, selected webhook or event notifications, and reporting or data-extraction capabilities. Scheduled workflows, pagination, batching, and reconciliation are useful where event coverage or bulk support is limited.

Can Martini integrate with Docebo?

Yes. Martini can consume Docebo REST APIs, receive selected Docebo webhook-style notifications, expose normalized REST APIs, and orchestrate scheduled synchronization, mapping, validation, retry, and reconciliation workflows.

Do I need a connector to integrate Docebo with Martini?

No. A dedicated Docebo connector is not required. Martini can use Docebo’s confirmed native integration mechanisms, including REST APIs, OAuth 2.0 access tokens, selected webhooks, and documented reporting or export facilities.

Is there any extra Lonti cost to integrate Docebo with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Docebo. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Docebo, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.

Which Docebo integration methods should be used?

Use Docebo REST APIs as the primary method for Users, Courses, Enrollments, Learning plans, ILT sessions, Catalogs, Certifications, and Reports. Use selected webhooks for supported near-real-time events, and scheduled API retrieval for unsupported events, high-volume processing, and reconciliation.

Are Docebo webhooks or event notifications available?

Docebo provides webhook or event-notification capabilities for selected events, subject to tenant configuration and enabled features. Coverage is not universal, so integrations should validate the required events and retain polling or reconciliation as a fallback.

How does synchronization handle pagination, duplicates, and failures?

Martini can process paginated results with checkpoints, stable Docebo identifiers, bounded batches, and incremental or rolling retrieval. Workflows can deduplicate webhook deliveries, retry throttling and transient server failures with backoff, isolate permanent failures, and run periodic reconciliation.

Can Martini expose an API façade for Docebo?

Yes. Martini can expose a REST API that presents a normalized interface to downstream applications while orchestrating authenticated calls to Docebo. This can centralize mapping, permissions, validation, business rules, and error handling without requiring every consumer to understand Docebo’s API model.

Related Martini documentation

APIs

Triggers

Workflows

Security

Operations

Connect Docebo with your enterprise systems

Use Martini to build a secure, maintainable Docebo integration around REST APIs, selected webhook events, scheduled workflows, data mapping, and reliable synchronization.

EXPLORE MARTINI
BOOK A DEMO