This article helps you choose the best integration approach for your Absorb LMS Portal based on your use case, timeline, and technical requirements. In general, we recommend using Direct Integrations whenever possible, adding options like Single Sign-On (SSO), SCIM, the Integration API, or Webhooks when they provide a clear benefit, using Connectors when you need a pre-built sync to a third-party platform, and relying on Data Imports/Exports only when other options are not a fit.

Many integrations are offered as add-ons and may require purchase and enablement. If you are unsure what is available in your environment, email your Client Success representative.

Integration Decision Order

Use the decision order below to narrow your options quickly. Start at the top and move down only if the earlier options do not meet your requirements.

Compare Integration Approaches

The table below summarizes what each integration approach is best suited for, along with common considerations that can affect implementation effort and long-term maintenance.

Before You Choose

The most successful integrations start with clear requirements. Before selecting an approach, confirm the following items with your internal stakeholders and any third-party vendor involved.

• Business outcome: What process are you trying to automate (authentication, user provisioning, reporting, enrollments, training delivery, etc.)?
• Systems involved: Which system is the source of truth for the data (HRIS, CRM, identity provider, Absorb LMS, etc.)?
• Data direction: Do you need to push data into Absorb, pull data out of Absorb, or both?
• Timing requirements: Do you need near real-time updates, or is a scheduled batch process acceptable?
• Technical ownership: Who will build and maintain the integration (your team, a vendor, or a pre-built Absorb offering)?

Direct Integrations

Direct Integrations are integrations built by Absorb that can be enabled and configured within your Absorb environment (often through Portal Settings). This is typically the fastest and most straightforward path when a supported Direct Integration matches your use case.

Offerings with Direction Integrations include but are not limited to:

• ADP
• BambooHR
• Namely
• Salesforce

For more information review Integrations: Overview.

When to Use Direct Integrations

Use Direct Integrations when you want to enable a supported workflow using configuration (not custom development).

• When an integration can be enabled with a Portal level toggle and basic configuration.
• When you want to minimize custom development and rely on a standardized setup path.

Example: Microsoft Teams Integration

The Microsoft Teams integration can be enabled in Portal Settings. Depending on the Teams capability you are enabling, configuration may include items such as a Tenant ID and notification or chat settings.

For more information review Microsoft Teams Virtual Meeting Integration

Identity and Access Integrations

Identity integrations focus on how Users authenticate into Absorb and how User profiles are created and maintained across systems. These are good additions when you want to improve security, reduce manual User management, or align Absorb access with your organization’s identity platform.

Single Sign-On

Single Sign-On (SSO) allows Users to sign in through a centralized identity platform. Absorb supports incoming SAML 2.0 SSO where Absorb acts as the Service Provider (SP) and the third-party system acts as the Identity Provider (IdP).

• Use SSO when you want Users to authenticate using existing corporate credentials.
• Use SSO when your security team requires centralized access control and a consistent login experience.
• Plan for setup effort because SSO requires configuration in both Absorb and the IdP, and vendor implementations can vary.
• For more information review Absorb LMS & Single-Sign On (SSO).

User Provisioning with SCIM

SCIM (System for Cross-domain Identity Management) supports automated User Provisioning and updates across platforms. For example, Absorb can use SCIM within Okta to synchronize user identities and updates between Okta and Absorb.

• Use SCIM when you want to automatically create, update, or deactivate Users based on changes in your identity system.
• Use SCIM when you want to reduce manual User administration in Absorb.
• Confirm structure fit because SCIM may have constraints (for example, flat department hierarchy expectations) and can rely heavily on Custom Fields.
• For more information review Absorb SCIM in Okta or Absorb SCIM in Azure.

Custom Integrations Using the Integration API and Webhooks

If you need a custom integration workflow that is not covered by a Direct Integration or Connector, the Integration API and Webhooks provide building blocks for integrating Absorb with your internal systems or third-party applications.

Integration API

The Absorb Integration API is a RESTful API that can be used to build custom integrations. Typical setup includes a REST client (for example, Postman), Admin credentials, regional Service Gateway endpoints, and an API Private Key. API documentation is available at docs.myabsorb.com.

• Use the Integration API when you need direct control over data movement and business rules.
• Use the Integration API when you need to integrate Absorb with a system that is not supported by a connector.
• Plan for development work because API integrations typically require web and integration experience.
• For more information review Getting Started with the Absorb Integration API.

Webhooks

Webhooks allow Absorb to send an HTTP request to your listener URL when specific events occur. Webhook payloads are intentionally lean and are commonly used to trigger downstream processes (and then fetch additional details through the Integration API when needed).

• Use Webhooks when you need event-driven notifications (near real-time) instead of scheduled batch jobs.
• Use Webhooks when you have an external endpoint available to receive requests.
• Plan for security and testing because Webhooks can use a secret key to validate signatures and are best tested in a sandbox environment before going live.
• For more information review Webhooks.

Connectors

Absorb Connectors are an add-on option that connects Absorb with external applications and synchronizes data. Connectors are designed to reduce custom development by providing pre-built maps and workflows that you configure to match your needs.

• For more information review Connectors Overview.

When to Use Connectors

Use Connectors when you want a pre-built integration path to a supported third-party system and you want to avoid building and maintaining custom code.

• Use a Connector if you use an application that we don't have a Direct Integration for. 
  • Direct Integrations are available from Absorb for ADP or Salesforce as an example.
• Use Connectors when you want pre-built mapping and automated workflows (and do not want to build a fully custom API solution).
• Use Connectors when near real-time synchronization is helpful and supported by the Connector.

Data Imports and Exports

Data Imports and Exports are file-based integrations used to move data into or out of Absorb on a one-time or scheduled basis. They are typically best suited to batch workflows (for example, nightly or weekly movement of records) and are often used when event-driven options like Direct Integrations, Webhooks, API, or Connectors are not a fit.

For more information review Comparison of Data Export and Data Import Options.

When to Use Data Imports or Exports

Use Data Imports and Exports when your source or destination system cannot support API-based integration, or when a scheduled file delivery model meets your requirements.

• Use Data Exports when you need to extract Absorb data as a file and deliver it via email or secure file transfer.
• Use Data Imports when another system can provide a file on a predictable schedule and Absorb needs to process that file.
• Use file-based integrations when near real-time updates are not required and batch timing is acceptable.

Delivery Options

Data Exports can be delivered by email or posted to a secure FTP (SFTP) site. Depending on your configuration, exports can be delivered to your own FTP server or to an Absorb-hosted FTP location.

Next Steps

Once you have identified which approach best matches your requirements, use the steps below to move forward with implementation planning.

1. Document your integration requirements (systems, data fields, direction, and timing).
2. Check for a Direct Integration that matches your use case.
3. If identity management is in scope, confirm whether you need SSO, SCIM, or both.
4. If you need custom workflows, evaluate whether Webhooks, the Integration API, or both are required.
5. If the target system is supported, evaluate Connectors before choosing file-based imports/exports.
6. Email your Client Success representative to confirm availability, licensing, and implementation path.