Cloud Performance Service Manager
now connects to ADP Workforce Now.
Pull employee records directly from ADP's OAuth2 API — no CSV export, no manual re-entry, no vendor base-URL guesswork.
One adapter, shaped around ADP's own API.
Most HCM systems onboard as a generic REST config — base URL, endpoint path, API key. ADP Workforce Now gets its own dedicated adapter instead, because its OAuth2 flow and certificate requirements don't fit that generic shape.
Employee records
Pulls identity, employment, and org data straight from Workforce Now.
OAuth2 flow
Client ID and Secret exchanged for a token on every extract — no static API key to rotate by hand.
Sandbox first
Build and test against ADP's IAT sandbox before flipping the connector to production.
Three fields, one certificate.
The config form asks for exactly what ADP's API needs — nothing generic to guess at.
Production traffic requires the mutual-TLS client certificate ADP issues for the connection, in addition to the Client ID and Secret — sandbox (IAT) needs neither.
Backfill history, then sync forward.
The first run isn't limited to today's snapshot — pull a full historical range on setup, then let scheduled extracts keep it current going forward.
One-time backfill
Set a historical start date on setup to pull past employee records in the initial extract, not just current-state data.
Scheduled syncs after
Once the backfill lands, recurring runs on the pipeline schedule keep records current without re-pulling history each time.
Same adapter, same auth
Historical and incremental pulls both run through the same OAuth2 connection — no separate export or one-off request to ADP.
Connect a client's ADP account today.
Add the connector from Data Sources, drop in the sandbox credentials, and the first extract runs in minutes.