ADP Workforce Now is ADP's HR, payroll, time and benefits platform. The connector reads workers, payroll, time, benefits, recruiting and organization data from the ADP API, and can send HR and payroll events such as hires, contact changes and pay data input.
Power end-to-end data operations for your ADP Workforce Now API with Nexla. Our bi-directional ADP Workforce Now connector is purpose-built for ADP Workforce Now, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to ADP Workforce Now or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your ADP Workforce Now workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating an ADP Workforce Now credential, you'll need to obtain OAuth 2.0 client credentials and a PKCS12 certificate from the ADP Developer portal. The ADP Workforce Now API uses OAuth 2.0 with mutual TLS (mTLS) authentication, which requires a client certificate in PKCS12 format.
To obtain the required credentials for ADP Workforce Now:
Access ADP Developer Portal: Navigate to the ADP Developer Portal and sign in to your ADP account. If you don't have an account, you'll need to register for one.
Create an Application: In the ADP Developer Portal, create a new application or select an existing application that will be used for API access. Applications in ADP are used to manage OAuth 2.0 credentials and API access.
Obtain Client Credentials: From your application settings, obtain the following:
Client ID: The unique identifier for your application
Client Secret: The secret key associated with your application
Generate or Obtain Certificate: ADP Workforce Now requires mutual TLS (mTLS) authentication using a PKCS12 (.p12) certificate file. You'll need to:
Generate a certificate signing request (CSR) or obtain a certificate from your certificate authority
Convert your certificate and private key to PKCS12 format if needed
The PKCS12 file should contain both the certificate and private key
Convert Certificate to PKCS12 Format (if needed): If you have a certificate in PEM format (.pem) and a private key (.key), you can convert them to PKCS12 format using OpenSSL:
You'll be prompted to enter a passphrase for the PKCS12 file. Remember this passphrase as you'll need it when creating the credential.
If you use the ADP Workforce Now OAuth2 authentication method instead, you paste the certificate and private key as PEM text, so no PKCS12 conversion is needed.
ADP Workforce Now uses OAuth 2.0 with mutual TLS (mTLS) for enhanced security. The PKCS12 certificate file must contain both the certificate and private key. Keep your certificate passphrase secure, as it's required for authentication. For complete information about ADP Workforce Now authentication, see the ADP developer documentation.
ADP Developer Account: You must have an active ADP Developer account
OAuth 2.0 Client Credentials: Client ID and Client Secret from your application
PKCS12 Certificate: A certificate file in PKCS12 format for mTLS authentication
Certificate Passphrase: The passphrase used to protect the PKCS12 certificate file
The ADP Workforce Now API uses OAuth 2.0 client credentials grant flow with mutual TLS authentication. All API requests must use HTTPS and include the client certificate for authentication.
For complete information about ADP Workforce Now API authentication and getting started, see the ADP developer documentation.
OAuth2 with client certificate authentication for ADP Workforce Now API. Requires API Central subscription.
Field
Required
Secret
Description
ADP API Base URL
Yes
No
Base URL for ADP API (Production: https://api.adp.com or Sandbox URL provided by ADP) Allowed values: Production
Client ID
Yes
Yes
OAuth2 Client ID from ADP Developer Self Service Portal
Client Secret
Yes
Yes
OAuth2 Client Secret from ADP Developer Self Service Portal
SSL Client Certificate (.pem)
Yes
Yes
SSL client certificate content in PEM format (-----BEGIN CERTIFICATE----- ... -----END CERTIFICATE-----)
SSL Private Key (.pem)
Yes
Yes
SSL private key content in PEM format (-----BEGIN PRIVATE KEY----- ... -----END PRIVATE KEY-----)
Performs OAuth 2.0 client credentials grant with mTLS using a PKCS12 (.p12) certificate file. The P12 file can be generated from your .pem certificate and .key files using OpenSSL.
Field
Required
Secret
Description
Client ID
Yes
No
Your application's Client ID from the ADP Developer portal.
Client Secret
Yes
Yes
Your application's Client Secret from the ADP Developer portal.
Certificate (.p12 File Content)
Yes
Yes
Paste the Base64-encoded content of your PKCS12 (.p12) certificate file.
Certificate Passphrase
Yes
Yes
The passphrase for your PKCS12 (.p12) certificate file.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – ADP Workforce Now
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Select the authentication method you want to use, and enter the required values:
ADP Token (mTLS Client Credentials): Enter your ADP application's Client ID and Client Secret from the ADP Developer portal. Paste the Base64-encoded content of your PKCS12 (.p12) certificate file, which must contain both the certificate and private key, in the Certificate (.p12 File Content) field, and enter its passphrase in the Certificate Passphrase field.
The PKCS12 certificate file must be Base64-encoded before pasting into the credential field. You can encode the file using base64 command-line tools or online Base64 encoders. The certificate passphrase is required to decrypt the certificate during authentication. Keep your certificate and passphrase secure, as they provide access to your ADP Workforce Now data.
ADP Workforce Now OAuth2: Select the ADP API Base URL (https://api.adp.com for production), enter your Client ID and Client Secret, and paste your certificate and private key as PEM text in the SSL Client Certificate (.pem) and SSL Private Key (.pem) fields, including the BEGIN and END lines.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the ADP Workforce Now connector tile, then select the credential that will be used to connect to ADP Workforce Now, and click Next; or, create a new ADP Workforce Now credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common ADP Workforce Now endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Templates are grouped by area below. All of them call https://api.adp.com. Most worker-level templates take an Associate OID, ADP's ID for a worker; use the List Workers template to find it (workers[].associateOID in the response). Templates whose description mentions a manager take the manager's associate OID and return data for that manager's team.
What each template returns depends on the ADP products and API scopes your ADP application is subscribed to; a template outside your subscription returns an authorization error from ADP.
Lists all workers, with person, work assignment and status data. Results are fetched in pages of 100. Sensitive personal data is masked unless you turn masking off.
Mask Sensitive Data (optional): Mask sensitive PII (Accept header masked=true). Set to false for unmasked data if your ADP app is allowed to read it. Default: true.
Retrieves one worker by associate OID: person, work assignments, status and dates. Sensitive personal data is masked unless you turn masking off.
Associate OID: ADP associateOID of the worker. Get it from List Workers (workers[].associateOID).
Mask Sensitive Data (optional): Mask sensitive PII (Accept header masked=true). Set to false for unmasked data if your ADP app is allowed to read it. Default: true.
Retrieves a worker's work assignments, including job title, department, location and manager.
Associate OID: ADP associateOID of the worker. Get it from List Workers (workers[].associateOID).
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves a worker's compensation history, such as raises, bonuses and pay rate changes.
Associate OID: ADP associateOID of the worker. Get it from List Workers (workers[].associateOID).
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves a worker's status change history, such as hire, leave and termination.
Associate OID: ADP associateOID of the worker. Get it from List Workers (workers[].associateOID).
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves a worker's workers' compensation insurance details and coverage codes.
Associate OID: ADP associateOID of the worker. Get it from List Workers (workers[].associateOID).
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Lists the workers that match a filter, then reads each worker's time cards whose time period starts on or after a date. It makes one time-card request per worker, so a large worker list takes longer to read.
Worker Filter ($filter): OData $filter for the worker list. Default keeps workers with an active work assignment (status code A).
Time Period Start Date: Return time cards whose period starts on or after this date (yyyy-MM-dd). Default: 30 days ago.
Lists the time-off request summaries of the team managed by one worker (Time v3 API). Enter the manager's associate OID. Results are fetched in pages of 100.
Associate OID: associateOID of the manager. Get it from List Workers (workers[].associateOID).
Retrieves labor codes used for time tracking and job costing.
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves a worker's active garnishments, such as child support, tax levies and creditor liens.
Associate OID: ADP associateOID of the worker. Get it from List Workers (workers[].associateOID).
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves the earnings codes used in payroll, such as regular pay, overtime, bonuses and commissions.
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves the pay cycle configuration, including pay frequency, periods and check dates.
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves the pay groups used to organize employees by pay schedule and processing.
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves a worker's benefit enrollments, such as health, dental, vision and 401(k).
Associate OID: ADP associateOID of the worker. Get it from List Workers (workers[].associateOID).
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves the benefit plans the organization offers.
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Retrieves the organization's positions, with job codes, titles and descriptions. Follows ADP's next-page links.
Nexla could not match this endpoint to a path in ADP's Workforce Now API documentation. Check with ADP that your API subscription includes it before relying on it.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
ADP Workforce Now data sources can also be manually configured to ingest data from any valid ADP Workforce Now API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
ADP Workforce Now API URLs take the form https://api.adp.com/hr/v2/workers for workers or https://api.adp.com/time/v2/workers/<associateOID>/time-cards for a worker's time cards. List responses wrap records in a named array, so use a response data path such as $.workers[*]. ADP list endpoints page with the $top and $skip query parameters. Authentication headers are added automatically from your credential. For the available endpoints, see ADP's API Explorer for Workforce Now and the Workforce Now API inventory.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new ADP Workforce Now data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the ADP Workforce Now destination, and select the Send to Destination option from the menu. Select the ADP Workforce Now connector from the list of available destination connectors, then select the credential that will be used to connect to ADP Workforce Now, and click Next; or, create a new ADP Workforce Now credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common ADP Workforce Now endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Every destination template posts an ADP event that changes HR or payroll data in ADP Workforce Now; see the Side effect note on each. Your ADP application must be subscribed to the matching event API.
Hire Worker (Event)
Hires a new worker in ADP Workforce Now with active status and an onboarding profile.
Each record is sent as-is as the JSON request body, so it must be a complete ADP event request (an events array) as shown in ADP's API Explorer. One request is sent per record.
Rehires a previously terminated worker with a new hire date and restores active employment status.
Each record is sent as-is as the JSON request body, so it must be a complete ADP event request (an events array) as shown in ADP's API Explorer. One request is sent per record.
Side effect: reactivates the worker's employment in ADP.
Adds an emergency or personal contact to a worker's profile.
Each record is sent as-is as the JSON request body, so it must be a complete ADP event request (an events array) as shown in ADP's API Explorer. One request is sent per record.
Side effect: adds a contact to the worker's record.
Changes the email address in a worker's personal communication profile.
Each record is sent as-is as the JSON request body, so it must be a complete ADP event request (an events array) as shown in ADP's API Explorer. One request is sent per record.
Side effect: overwrites the worker's email address in ADP.
Each record is sent as-is as the JSON request body, so it must be a complete ADP event request (an events array) as shown in ADP's API Explorer. One request is sent per record.
Side effect: overwrites the worker's legal name in ADP, which payroll and tax records use.
Each record is sent as-is as the JSON request body, so it must be a complete ADP event request (an events array) as shown in ADP's API Explorer. One request is sent per record.
Side effect: overwrites the worker's marital status, which can affect tax withholding and benefit eligibility.
Starts a new general deduction instruction for a worker in payroll.
Each record is sent as-is as the JSON request body, so it must be a complete ADP event request (an events array) as shown in ADP's API Explorer. One request is sent per record.
Side effect: adds a deduction that applies to the worker's future pay.
Changes an existing general deduction instruction for a worker in payroll.
Each record is sent as-is as the JSON request body, so it must be a complete ADP event request (an events array) as shown in ADP's API Explorer. One request is sent per record.
Side effect: changes a deduction that applies to the worker's future pay.
Stops an existing general deduction instruction for a worker in payroll.
Each record is sent as-is as the JSON request body, so it must be a complete ADP event request (an events array) as shown in ADP's API Explorer. One request is sent per record.
Side effect: stops a deduction from applying to the worker's future pay.
Creates or appends a pay data batch for a payroll cycle, with earnings, deductions and reimbursements.
Nexla sends up to 100 records per request and wraps each record as {"data": record} inside an events array, so each record should be the data object of one pay data input event.
Side effect: adds pay data to the payroll cycle, which changes what workers are paid when that payroll is processed.
ADP Workforce Now destinations can also be manually configured to send data to any valid ADP Workforce Now API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured ADP Workforce Now endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the ADP Workforce Now endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.