Faster time to market
Embed ready workflows and reduce developer build time.

Embed ADP payroll and HR automations into your SaaS product. Build in-app flows to sync worker records, post timecards, submit payroll inputs and surface ADP events for customer-specific workflows and self-service automations.
Embed ready workflows and reduce developer build time.
Run isolated ADP flows per customer with shared orchestration logic.
Publish ADP actions as controlled tools with role and usage policies.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Teams can integrate ADP to sync worker and payroll data, submit time and payroll inputs and consume HR events across customer accounts. Using Cyclr’s embedded iPaaS you can orchestrate multi-step flows—for example: create or update worker profiles, push payroll data input, read payroll runs and subscribe to ADP event notifications for new hires or time-off.
PRODUCT USE CASES
Quickly create tenant-aware integrations between your SaaS product and ADP using Cyclr’s low-code builder. Publish ADP automations into your white-label embedded marketplace, orchestrate payroll and HR flows, and expose governed MCP tools for secure customer self-service.
Pull worker records (hr/v2/workers) to populate your tenant user directory and keep profiles in sync.
Push payroll data input records and read payroll-run status to automate pay-cycle handoffs.
Create or update time entries and approval status to keep ADP time records accurate.
ORCHESTRATION
Cyclr sits between your SaaS product and ADP to handle authentication, govern access and orchestrate every API call per customer, at scale.
Your app requests an action for a specific customer.
Cyclr authenticates, applies policies and routes the request.
ADP processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore ADP methods you can orchestrate through Cyclr.
Request the list of all available workers that the requester is authorized to view.
Hire a new worker.
Re-hire a worker.
Update a legal address of a worker.
Update a personal email to a worker.
Delete a personal email of a worker.
Update the personal address of a worker.
Add a new personal mobile to a worker.
Update a personal mobile of a worker.
Delete a personal mobile of a worker.
Add a new legal address to a worker.
Add a new personal email to a worker.
Add a new personal landline to a worker.
Delete a personal landline of a worker.
Update a personal landline of a worker.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing ADP integrations in Cyclr.
api.adp.com (token host accounts.adp.com; regional hosts: api.eu.adp.com, accounts.eu.adp.com)Client ID, client secret, X.509 certificate and private key; tenant/company identifier as applicable.
Workers, Payroll, Time & Labor, Recruiting, Benefits and Events—read, create, update, search and subscription methods.
ADP uses OData-style pagination ($top and $skip). Typical max page size is 100; iterate until 204 No Content indicates the end.
ADP enforces request quotas and returns 429 Too Many Requests when exceeded. Exact limits vary by API and tenant—check ADP developer portal for quotas.
IMPLEMENTATION
ADP APIs use OAuth 2.0 (client credentials or authorization code) with X.509 certificate-based transport (mutual TLS). Tokens come from accounts.adp.com and apply to api.adp.com endpoints.
Client ID, client secret, X.509 certificate and private key; tenant/company identifier as applicable.
Requires ADP Marketplace app registration and X.509 certificate provisioning; partner approval may be required.
COMMON QUESTIONS
It syncs worker and payroll data, submits payroll and time inputs and consumes ADP events for automated HR workflows. Use cases include roster syncs, payroll input submissions, timecard write-backs and event-driven new-hire provisioning.
ADP uses OAuth 2.0 with client credentials or authorization code plus X.509 certificate transport (mutual TLS); your app exchanges client credentials at accounts.adp.com to call api.adp.com endpoints.
Yes. Cyclr supports tenant-aware, multi-tenant orchestrations so you can run isolated ADP flows per customer while reusing orchestration logic and credentials mapping.
Yes. Cyclr lets you publish ADP actions as governed MCP tools with usage controls, role policies and centralized monitoring for in-app customer access.
KEEP EXPLORING