Set up an ADP Workforce Now connector

Availability

This connector requires ADP API Central. You cannot use this connector successfully if the ADP API Central add-on is not part of your ADP Workforce Now plan.

Capabilities

The ADP Workforce Now connector syncs the following resources:

Resource	Sync	Provision
Worker

ADP Workforce Now has internal portal security roles (Security Administrator, User Master, etc.), but the ADP API does not expose security role assignments. These roles are managed exclusively through the ADP portal UI and cannot be synced.

Worker profile fields

Each synced worker is exposed as a user resource. The following keys are written to the user profile when the corresponding ADP field is populated. Empty values are omitted.

Profile key	ADP source	Notes
`associate_oid`	`worker.associateOID`	Always set. Also used as the user’s `ExternalID`.
`worker_id`	`worker.workerID.idValue`	The displayed worker number.
`original_hire_date`	`worker.workerDates.originalHireDate`
`adjusted_service_date`	`worker.workerDates.adjustedServiceDate`
`raw_status`	`worker.workerStatus.statusCode.codeValue`	Literal status (`Active`, `Inactive`, `Terminated`). The SDK enabled/disabled mapping collapses `Inactive` and `Terminated` together; this field preserves the distinction.
`reports_to_worker_id`	`workAssignments[<active>].reportsTo[0].workerID.idValue`	Manager’s worker number.
`manager_id`	`workAssignments[<active>].reportsTo[0].associateOID`	Manager’s ADP `associateOID`. C1’s directory manager mapper resolves this against the manager user’s `ExternalID`, so the manager relationship is automatically populated in the C1 user graph. Both this field and `reports_to_worker_id` are derived from the same `reportsTo` entry.
`job_title`	`workAssignments[<active>].jobTitle`
`department`	`workAssignments[<active>].homeOrganizationalUnits[<Department>].nameCode`
`location`	`workAssignments[<active>].homeWorkLocation.nameCode`	Assigned work location. Prefers `shortName`, falls back to `codeValue`.

When a worker has multiple work assignments, fields drawn from workAssignments[] come from the first non-terminated assignment, falling back to any assignment if all are terminated.

Custom worker attributes

ADP Workforce Now tenants can define custom fields on workers via the ADP admin UI. These appear in the customFieldGroup object on the worker record and are not synced by default — you must explicitly map the fields you want using the worker-custom-fields configuration option.

Configuration format

Each entry maps an ADP custom field to a profile key using the format "<fieldType>/<codeValue>"="<profileKey>":

"amountFields/Rate"    → profile key "pay_rate"
"stringFields/PR code" → profile key "pr_code"

The fieldType must be one of: stringFields, numberFields, dateFields, indicatorFields, codeFields, amountFields, percentFields, telephoneFields. The codeValue must match the field’s nameCode.codeValue exactly as it appears in ADP, including spaces and capitalisation.

Amount fields

Amount fields emit two profile keys: the numeric value under <profileKey> and the ISO currency code under <profileKey>_currency_code. For example, mapping "amountFields/Rate"="pay_rate" produces:

Profile key	Value
`pay_rate`	`23.0` (number)
`pay_rate_currency_code`	`"AUD"`

Example

baton-adp-workforce-now \
  --worker-custom-fields="amountFields/Rate"="pay_rate" \
  --worker-custom-fields="stringFields/PR code"="pr_code" \
  --worker-custom-fields="indicatorFields/Emp radio"="is_senior_emp" \
  --worker-custom-fields="dateFields/Emp Date"="emp_custom_date"

Or via environment variable (comma-separated):

BATON_WORKER_CUSTOM_FIELDS="amountFields/Rate=pay_rate,stringFields/PR code=pr_code"

Gather ADP Workforce Now credentials

To configure the ADP Workforce Now connector, you need administrator permissions in ADP Workforce Now.

Navigate to the ADP Marketplace Developer portal and register your application.

Obtain your OAuth2 client credentials:

Copy the Client ID and Client Secret
Download the SSL client certificate (PEM-encoded .pem or .crt file)
Download the SSL private key (PEM-encoded .pem or .key file)
Save these credentials securely — ADP requires mTLS authentication

Configure the ADP Workforce Now connector

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Integrations > Connectors and click Add connector.

Search for ADP Workforce Now and click Add.

Choose how to set up the new ADP Workforce Now connector:

Add the connector to a currently unmanaged app
Add the connector to a managed app
Create a new managed app

Set the owner for this connector.

Click Next.

Find the Settings area of the page and click Edit.

Enter the required configuration:

Client ID (adp-workforce-now-client-id): Your ADP OAuth2 client ID
Client Secret (adp-workforce-now-client-secret): Your ADP OAuth2 client secret
SSL Certificate (adp-workforce-now-ssl-cert): PEM-encoded SSL client certificate for mTLS
SSL Key (adp-workforce-now-ssl-key): PEM-encoded SSL client private key for mTLS
Base URL (adp-workforce-now-base-url): The ADP API base URL (default: https://api.adp.com)
Worker Custom Fields (worker-custom-fields): Optional. Map worker custom attributes to profile keys. See Custom worker attributes for format details.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your ADP Workforce Now connector is now pulling access data into C1.

Follow these instructions to use the ADP Workforce Now connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals.

Step 1: Set up a new ADP Workforce Now connector

In C1, navigate to Integrations > Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new ADP Workforce Now connector:

Add the connector to a currently unmanaged app
Add the connector to a managed app
Create a new managed app

Set the owner for this connector.

Click Next.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your ADP Workforce Now connector deployment:

Secrets configuration

# baton-adp-workforce-now-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-adp-workforce-now-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # ADP Workforce Now credentials
  BATON_ADP_WORKFORCE_NOW_CLIENT_ID: <ADP OAuth2 client ID>
  BATON_ADP_WORKFORCE_NOW_CLIENT_SECRET: <ADP OAuth2 client secret>
  BATON_ADP_WORKFORCE_NOW_SSL_CERT: <path to PEM SSL client certificate>
  BATON_ADP_WORKFORCE_NOW_SSL_KEY: <path to PEM SSL private key>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-adp-workforce-now.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-adp-workforce-now
  labels:
    app: baton-adp-workforce-now
spec:
  selector:
    matchLabels:
      app: baton-adp-workforce-now
  template:
    metadata:
      labels:
        app: baton-adp-workforce-now
        baton: "true"
        baton-app: adp-workforce-now
    spec:
      containers:
      - name: baton-adp-workforce-now
        image: public.ecr.aws/conductorone/baton-adp-workforce-now:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-adp-workforce-now
        envFrom:
        - secretRef:
            name: baton-adp-workforce-now-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Applications. On the Managed apps tab, locate and click the name of the application you added the ADP Workforce Now connector to. ADP Workforce Now data should be found on the Entitlements and Accounts tabs.

Done. Your ADP Workforce Now connector is now pulling access data into C1.

All versions of this connector are available at dist.conductorone.com.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up an ADP Workforce Now connector

Availability

Capabilities

Worker profile fields

Custom worker attributes

Configuration format

Amount fields

Example

Gather ADP Workforce Now credentials

Configure the ADP Workforce Now connector

Step 1: Set up a new ADP Workforce Now connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Documentation Index

​Availability

​Capabilities

​Worker profile fields

​Custom worker attributes

​Configuration format

​Amount fields

​Example

​Gather ADP Workforce Now credentials

​Configure the ADP Workforce Now connector

​Step 1: Set up a new ADP Workforce Now connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Availability

Capabilities

Worker profile fields

Custom worker attributes

Configuration format

Amount fields

Example

Gather ADP Workforce Now credentials

Configure the ADP Workforce Now connector

Step 1: Set up a new ADP Workforce Now connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector