Source: https://atomicwork.docs.pageloop.ai/integrations/hrms/adp

# ADP

# ADP

## ADP: Permissions and setup

Learn how to set up the native ADP integration to automate HR, payroll, and workforce workflows.

The ADP integration connects Atomicwork natively to ADP's APIs for HR, payroll, and workforce management operations. By integrating ADP, your HR and IT teams can automate employee lifecycle events, retrieve employee data, and manage time and attendance directly from Atomicwork.

ADP works in Atomicwork in two ways:

- **User sync:** ADP is a source for multi-source user sync, so workers in ADP sync into Atomicwork as users. See [User sync](#user-sync).
- **Workflow actions:** A Call API action lets workflows make requests to any ADP API endpoint. See [Use supported workflow actions](#use-supported-workflow-actions).

### Permissions

To connect ADP with Atomicwork, you need specific permissions in both platforms:

- **Atomicwork permissions:** You must have workspace administrator permissions to manage the app store and install the integration. To use ADP in workflows, you need workflow creation and editing permissions.
- **ADP permissions:** You must register an application in the [ADP Developer Portal](https://developers.adp.com/) to obtain OAuth2 client credentials and mTLS certificates. API permissions depend on the scopes and products subscribed to in your ADP account.

### Configure the integration

When setting up the integration in Atomicwork, you must provide the following configuration details:

| **Field**      | **Required** | **Description**                                             |
| -------------- | ------------ | ----------------------------------------------------------- |
| Client ID      | Yes          | Your ADP OAuth2 Client ID.                                  |
| Client Secret  | Yes          | Your ADP OAuth2 Client Secret.                              |
| Certificate    | Yes          | The PEM-encoded X.509 client certificate.                   |
| Private Key    | Yes          | The PEM-encoded private key.                                |
| CA Certificate | No           | The PEM-encoded CA certificate from ADP.                    |
| Token URL      | No           | Defaults to <https://accounts.adp.com/auth/oauth/v2/token>. |
| Base URL       | No           | Defaults to <https://api.adp.com>.                          |

### Use supported workflow actions

The ADP integration currently exposes one flexible action that allows workflows to make arbitrary HTTP requests to any ADP API endpoint.

#### Call API action

This action requires the following inputs:

| **Input**        | **Required** | **Description**                                                                                 |
| ---------------- | ------------ | ----------------------------------------------------------------------------------------------- |
| HTTP Method      | Yes          | Select GET, POST, PUT, PATCH, or DELETE. The default is POST.                                   |
| API Endpoint URL | Yes          | Enter the full ADP API URL.                                                                     |
| Request Body     | No           | Provide the XML or JSON body depending on the ADP endpoint requirements.                        |
| Headers          | No           | Supply additional headers as a JSON object. The Authorization header is automatically injected. |

### Explore use cases

Since the integration exposes a generic Call API action, you can leverage it for any ADP API endpoint. Practical use cases include:

- **Time and attendance management:** Submit or retrieve time-off requests, punch data, and schedule information.
- **Employee data retrieval:** Query employee profiles, demographics, and employment details to enrich service desk requests.
- **Payroll operations:** Interact with payroll APIs to retrieve pay statements or trigger payroll-related workflows.
- **Workforce management automation:** Build workflows that automatically create or update records in ADP when triggered by events in Atomicwork.
- **Employee onboarding and offboarding:** Automate the creation or deactivation of employee records in ADP.
- **AI-powered HR assistance:** Register ADP as a trusted knowledge source so the AI assistant can reference documentation to answer employee questions.

## User sync

ADP is a user sync source in [multi-source user sync](/product/identity-access-management/people-roles-and-teams/importing-people-into-atomicwork), alongside Azure AD, Okta, JumpCloud, Workday, Rippling, and Slack. Workers in ADP sync into Atomicwork as users.

### What ADP brings to user profiles

As your HR system of record, ADP carries fields that identity sources don't have:

- Contact details
- Job title and department
- Manager
- Worker type
- Work location
- Hire, rehire, and termination dates

You can map these ADP fields to Atomicwork attributes and filter which workers sync by status, department, title, worker type, or location.

Identity can still come from Azure AD or Okta, with ADP supplying the HR attributes. Because each Atomicwork attribute can be mapped to a different source, you can keep your identity provider as the source for sign-in details and pull HR data from ADP.

### Sync modes

| **Mode**  | **How it works**                                           |
| --------- | ---------------------------------------------------------- |
| Scheduled | A full sync runs every 24 hours.                           |
| On-demand | Trigger a sync manually when you need it.                  |
| Real-time | Worker changes in ADP flow into Atomicwork as they happen. |

### HR-driven onboarding and offboarding

With ADP syncing users, your HR system can drive the employee lifecycle in Atomicwork:

- **Onboarding:** A new hire in ADP creates the user in Atomicwork and can trigger your onboarding workflows.
- **Offboarding:** A termination in ADP can trigger offboarding — deprovisioning, access removal, and asset recovery.

HR records hires and terminations before anyone else, so with real-time sync these workflows can start within minutes of the change in ADP.

ADP tracks leave separately from termination, so people on leave aren't offboarded by mistake.

---
