Scenario
You want to integrate PlusPlus with an HRIS or identity-management system that PlusPlus doesn't support out of the box. Your environment isn't a fit for SCIM, or isn't running Workday.
A Custom Integration is a tenant-specific data-source wrapper written by PlusPlus engineering to fetch user data from a non-standard source. Once the wrapper is in place, you self-serve on attribute mapping, custom attributes, and role logic the same way you would with any other people integration method.
Solution
Custom Integrations are not configurable in System Settings. They are scoped, built, and deployed by PlusPlus engineering as an engagement, then handed off to you for self-serve attribute configuration. There are two parts to setup: the engineering work to connect to your data source, and the configuration you do in PlusPlus once data is flowing.
When to consider a Custom Integration
Before requesting a Custom Integration, confirm that none of the standard people integration methods fits your environment:
Workday — if you use Workday HRIS, this is supported natively and is configurable in System Settings without engineering work.
SCIM — if your identity provider (Okta, OneLogin, Azure AD, etc.) supports SCIM provisioning, this is the recommended path for any IdP-driven environment.
CSV over SFTP — supported as a fallback if no API option is feasible.
A Custom Integration makes sense when:
Your HRIS or identity system isn't Workday and doesn't support SCIM.
You don't want a file-based integration like CSV over SFTP.
Your data source has the data you need but exposes it through a non-standard API, custom authentication scheme, or vendor-specific protocol that requires bespoke client code.
Request a Custom Integration
Contact your Customer Success Manager to request a Custom Integration.
Your CSM will scope the engagement with PlusPlus engineering. Expect questions about:
The source system (vendor, API documentation, authentication method)
The shape of the user data and which fields you want available in PlusPlus
Volume and refresh frequency
Connectivity requirements (allowlists, IP ranges, network paths)
PlusPlus engineering writes a custom wrapper for your tenant. The wrapper handles authentication and data retrieval, then passes the resulting payload to the standard People Integration system.
Once the wrapper is deployed, you'll be notified and can begin configuring attribute mappings.
Configure attributes once data is flowing
Once your Custom Integration is live, the configuration experience is identical to other people integration methods. From System Settings > Integrations > People you can:
Map standard attributes (name, email, title, department, manager, hire date, etc.) from your custom payload to PlusPlus user fields
Define custom attributes for use in filtering, reporting, and automated rules
Configure the Restricted-role indicator to flip users between regular and restricted roles based on payload data
Exclude attributes from CSV export
For mapping syntax, examples, and how to test expressions against a sample payload, see People Integration: Attribute Mapping.
Validate the integration
Use the Syncs Dashboard to:
Run a dry sync before any configuration change goes live
Inspect the raw payload PlusPlus is receiving from your custom data source
Confirm attribute mappings are extracting the right values
Review per-user outcomes (created, updated, skipped, failed) to catch issues before they affect users
Go deeper
How a Custom Integration differs from other methods
| Workday | SCIM | CSV over SFTP | Custom Integration |
Available out of the box | Yes | Yes | Yes | No — engineering-scoped |
Configurable in System Settings | Yes | Yes | Yes (mappings) | Mappings only — connection is custom code |
Setup timeline | Self-serve | Self-serve | CSM-assisted | Varies based on integration complexity (engineering-scoped) |
Attribute mapping | JMESPath | JMESPath | JMESPath | JMESPath |
Restricted role support | Yes | Yes | Yes | Yes |
Once a Custom Integration is in place, the data it produces flows into the same People Integration pipeline used by all other methods. From the moment the payload reaches PlusPlus, every standard feature works identically — attribute mapping, custom attributes, restricted-role assignment, deprovisioning, and sync inspection are all available.