Cloud Performance Service Manager
now connects to Paychex Flex.
Pull employee records directly from Paychex Flex's OAuth2 API, scoped to a single Company ID — no CSV export, no manual re-entry.
One adapter, scoped to your Company ID.
Most HCM systems onboard as a generic REST config — base URL, endpoint path, API key. Paychex Flex gets its own dedicated adapter instead, because its OAuth2 flow and per-company scoping don't fit that generic shape.
Employee records
Pulls worker identity and employment data straight from Paychex Flex.
OAuth2 flow
Client ID and Secret exchanged for a token on every extract — no static API key to rotate by hand.
Company-scoped
Every lookup is scoped to a single Company ID, so a client's data never crosses into another's.
Four fields, scoped to one company.
The config form asks for exactly what Paychex Flex's API needs — nothing generic to guess at.
Every request is scoped to the Company ID on file — set it once per client so their employee data never mixes with another company's.
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 Company-scoped OAuth2 connection — no separate export or one-off request to Paychex.
Connect a client's Paychex account today.
Add the connector from Data Sources, drop in the sandbox credentials and Company ID, and the first extract runs in minutes.