.png)
ADP Workforce Now Integration Guide
Connect ADP Workforce Now with enterprise applications through REST APIs, selected event notifications, scheduled workflows, and approved file exchanges.
ADP Workforce Now integration options at a glance
ADP Workforce Now primarily integrates through ADP REST APIs covering workforce, payroll, time, talent, benefits, and related capabilities. Selected ADP products and APIs also provide event-notification capabilities, although coverage is not universal across every object or operation. Some product configurations support asynchronous processing, batch operations, reports, or file-oriented exchanges, but availability must be confirmed for the customer’s subscription and permissions. ADP uses OAuth 2.0 with application credentials, scopes, consent, and tenant context. Martini can consume these APIs, receive supported notifications, schedule paginated synchronization workflows, transform data, and expose controlled APIs for downstream applications.
| Integration point | Supported by ADP Workforce Now? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | ADP provides REST APIs organized by workforce, payroll, time, talent, benefits, and related capabilities. Martini can retrieve or submit supported Workforce Now transactions according to the customer’s products and permissions. | Martini workflows can consume REST endpoints, add OAuth 2.0 authorization, paginate responses, transform payloads, apply business rules, and expose controlled APIs over selected ADP operations. |
| Webhooks and outbound callbacks | Limited | ADP provides event-notification capabilities for selected business events and API products, but notifications are not universal across all Workforce Now objects or operations. | Martini can expose an API endpoint or webhook intake workflow, validate source and authorization details, deduplicate notifications, retrieve the current resource, and route downstream processing. |
| Bulk, asynchronous, and batch processing | Limited | Some ADP products or operations may support asynchronous jobs, batch processing, status polling, or report-based alternatives. Availability and limits must be verified per API. | Martini can submit supported jobs, poll status, stage paginated results, transform batches, and persist checkpoints or failures for controlled replay. |
| File and report exchange | Limited | Some ADP Workforce Now configurations support product-specific file, report, integration, import, or export exchanges. SFTP, formats, and availability depend on the customer’s services. | Where an approved file endpoint exists, Martini can orchestrate file retrieval or delivery, parse supported formats, validate content, map fields, and reconcile processed files. |
| Authentication | Yes | ADP APIs use OAuth 2.0-based application authorization with client credentials, scopes, customer consent, and tenant or organizational context as required by the selected API. | Martini can store credentials securely, configure API authentication, send required authorization headers and parameters, and separate sandbox and production configuration. |
| GraphQL APIs | Not confirmed | No current ADP Workforce Now GraphQL API was confirmed in the reviewed official materials. | Martini can consume GraphQL APIs when a provider documents them, but ADP Workforce Now integrations should use the confirmed REST interfaces instead. |
| SOAP APIs | Not confirmed | A general-purpose SOAP API was not confirmed as the recommended integration method for new ADP Workforce Now integrations. | Martini supports SOAP consumption generally, but no SOAP interface should be selected for ADP Workforce Now without product-specific ADP documentation. |
| Database access | No | Direct access to the underlying ADP Workforce Now SaaS database is not an expected integration method. | Martini should use ADP APIs, approved event notifications, reports, or file exchanges rather than attempting direct database connectivity. |
How ADP Workforce Now exposes data and business events
ADP Workforce Now REST APIs
ADP provides REST APIs across workforce, payroll, time, talent, benefits, and related business capabilities. The available objects and operations depend on subscribed modules, country, application approval, permissions, and tenant configuration.
Martini implementation pattern
Martini implementation pattern: Martini workflows authenticate with OAuth 2.0, call the selected ADP REST endpoint, handle pagination and response validation, transform the result into a canonical model, apply business rules, and write to one or more target systems. For write operations, the workflow validates permissions, effective dates, and idempotency keys before submitting the transaction.
Implementation sequence
ADP Workforce Now event notifications
ADP provides event-notification capabilities for selected business events and API products. Event coverage is selective, and a notification may contain identifiers or metadata rather than the complete current Worker, Person, or other resource.
Martini implementation pattern
Martini implementation pattern: Martini exposes an API endpoint or webhook intake workflow, validates the notification and source details, records the event identifier, checks for duplicates, retrieves the authoritative ADP resource when needed, and routes longer downstream work asynchronously or through an orchestrated workflow.
Implementation sequence
ADP Workforce Now batch and file processing
Some ADP products and customer configurations support asynchronous operations, batch processing, reports, or file-oriented integration exchanges. These capabilities are product-specific and should be confirmed before implementation.
Martini implementation pattern
Martini implementation pattern: Martini schedules a workflow to submit or retrieve an approved batch, report, or file, polls asynchronous status where required, stages data, validates formats and record counts, maps the content, and persists checkpoints for reconciliation. The workflow should not assume that a universal bulk or file API exists for every Workforce Now object.
Implementation sequence
Common ADP Workforce Now integration patterns
Pattern 1: Synchronize employees to enterprise applications
When to use this pattern
Use this pattern when Worker, Person, and Position data must be shared with identity, service-management, sales, or business applications. It supports scheduled synchronization and can incorporate selected ADP event notifications where available.
Integration direction
Example Mapping
| ADP Workforce Now Field | Canonical Field | Target Field |
|---|---|---|
| Worker.workerID | employee.externalId | externalId |
| Person.personName.formattedName | employee.displayName | displayName |
| Worker.workerStatus.statusCode.codeValue | employee.employmentStatus | status |
| Position.positionTitle | employee.positionTitle | jobTitle |
Martini implementation pattern
Martini retrieves paginated Workers and related Person and Position data, or responds to a supported lifecycle event by fetching current state. It normalizes identifiers, applies effective-date and source-of-truth rules, performs idempotent upserts, and sends validation or transient failures to controlled retry and reconciliation paths.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- scheduling
- error handling
Pattern 2: Deliver payroll data to finance
When to use this pattern
Use this pattern when permitted Pay Statements or payroll-related information must be delivered to a finance platform, accounting application, or reporting store. It is appropriate for scheduled, period-based processing with strict data minimization.
Integration direction
Example Mapping
| ADP Workforce Now Field | Canonical Field | Target Field |
|---|---|---|
| Pay Statement.workerID | payroll.employeeExternalId | employeeId |
| Pay Statement.payPeriod | payroll.payPeriod | payPeriod |
| Pay Statement.earnings | payroll.earnings | earnings |
| Pay Statement.netPay | payroll.netAmount | netAmount |
Martini implementation pattern
A scheduled Martini workflow retrieves only the payroll fields authorized for the use case, validates pay-period and worker identifiers, transforms amounts and dates, and writes idempotently to NetSuite or another approved target. Sensitive payloads are minimized, protected from verbose logging, and retained only as required.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- data minimization
- validation
- error handling
Pattern 3: Process worker lifecycle events
When to use this pattern
Use this pattern for supported ADP event types related to worker changes, onboarding, transfers, or terminations. It is useful when downstream identity or service-management actions should begin promptly without treating event notifications as complete resource snapshots.
Integration direction
Example Mapping
| ADP Workforce Now Field | Canonical Field | Target Field |
|---|---|---|
| event.eventId | lifecycle.eventId | correlationId |
| event.resourceIdentifier | worker.externalId | employeeId |
| Worker.workerStatus | lifecycle.status | employmentStatus |
| Position.departmentCode | organization.departmentId | department |
Martini implementation pattern
Martini receives and validates the event, records its identifier, checks idempotency, retrieves the current Worker or Person resource, and applies lifecycle rules before calling the downstream system. The intake acknowledges promptly while longer work is retried or processed asynchronously.
Martini capabilities used
- API exposure
- webhook intake
- workflows
- API consumption
- deduplication
- asynchronous execution
Pattern 4: Synchronize time-off requests
When to use this pattern
Use this pattern when approved, denied, cancelled, or newly requested Time Off Requests must be reflected in a downstream workforce or service application, or when permitted changes must be submitted back to ADP.
Integration direction
Example Mapping
| ADP Workforce Now Field | Canonical Field | Target Field |
|---|---|---|
| Time Off Request.requestId | absence.externalId | externalId |
| Time Off Request.workerID | absence.employeeId | employeeId |
| Time Off Request.startDate | absence.startDate | startDate |
| Time Off Request.status | absence.status | status |
Martini implementation pattern
Martini periodically retrieves supported requests, compares status and effective-date changes using persisted synchronization state, maps dates with the required time-zone rules, and updates the target idempotently. Write-back to ADP occurs only when the selected API permits it; conflicting or late changes are routed to reconciliation.
Martini capabilities used
- scheduled workflows
- API consumption
- state tracking
- data mapping
- business rules
- reconciliation
Applications commonly integrated with ADP Workforce Now
ADP Workforce Now can participate in broader HR, identity, finance, service-management, and operational workflows. The exact objects and direction depend on ADP product entitlements, application permissions, and which system is authoritative for each data domain.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize worker, user, department, and organizational information for account ownership, onboarding, and internal operations. | ADP Workforce Now → Martini → Salesforce | A scheduled or event-driven Martini workflow retrieves Workers, Persons, and Positions, maps them to Salesforce users or operational objects, applies source-of-truth rules, and performs idempotent updates with controlled retries. |
| ServiceNow | Automate employee onboarding, transfers, terminations, and access-related service requests. | ADP Workforce Now → Martini → ServiceNow | Martini receives supported ADP event notifications or runs a scheduled reconciliation, retrieves the authoritative Worker or Person resource, applies lifecycle rules, and creates or updates ServiceNow requests and records. |
| NetSuite | Provide workforce or payroll-related information for finance, costing, and reconciliation processes. | ADP Workforce Now → Martini → NetSuite | A Martini workflow retrieves permitted Pay Statements or workforce data, minimizes sensitive fields, transforms payroll and organizational values into the NetSuite model, and writes results using idempotent business keys. |
| Microsoft Entra ID | Align worker lifecycle and employment-status changes with identity and access-management processes. | ADP Workforce Now → Martini → Microsoft Entra ID | Martini processes supported lifecycle notifications or scheduled Worker changes, maps employment status and identity attributes, applies provisioning rules, and sends approved updates to Microsoft Entra ID with duplicate protection. |
| SAP SuccessFactors | Exchange HR, worker, organizational, or payroll-adjacent data when ADP and SAP products coexist in a broader HR landscape. | ADP Workforce Now → Martini → SAP SuccessFactors | Martini orchestrates domain-specific flows between the two HR platforms, applies explicit source-of-truth rules, transforms organizational identifiers, and records reconciliation results for overlapping objects. |
| Workday | Coordinate worker or organizational data in enterprises operating multiple HR platforms during coexistence, transition, or regional deployments. | ADP Workforce Now → Martini → Workday | A scheduled Martini workflow exchanges only approved domains, normalizes worker and organization identifiers, applies effective-date rules, and routes validation failures for review rather than overwriting authoritative data. |
| UKG Pro | Exchange workforce, time, or payroll-adjacent information in organizations with multiple HR and workforce-management platforms. | ADP Workforce Now → Martini → UKG Pro | Martini retrieves permitted ADP data, maps time or workforce attributes to the UKG Pro model, applies customer-specific ownership rules, and uses checkpoints and reconciliation to manage partial or repeated transfers. |
| Jira | Create or update operational tasks for onboarding, employee changes, or HR-related workflows. | ADP Workforce Now → Martini → Jira | Martini converts qualifying Worker lifecycle changes into Jira issues, enriches them with department and position data, prevents duplicate issue creation, and records downstream failures for replay. |
How to build a ADP Workforce Now integration in Martini
Objective
Establish separate ADP Workforce Now sandbox and production configurations with the correct application credentials, scopes, tenant context, and endpoint settings.
Instructions in Martini
- Obtain ADP application approval and required API permissions
- Store OAuth 2.0 credentials and tokens in Martini environment configuration or secrets
- Keep sandbox and production credentials and endpoints separate
- Test authorization with a minimally scoped API request
Objective
Select the trigger that matches the business process: scheduled synchronization for reconciliation, an ADP event notification for supported events, or an exposed Martini API for controlled invocation.
Instructions in Martini
- Use a scheduler for periodic Worker, payroll, or Time Off Request retrieval
- Expose a Martini API endpoint for supported ADP event notifications
- Use an API-triggered workflow when another application initiates processing
- Confirm that the selected ADP product supports the required event or operation
Objective
Retrieve authoritative ADP resources while accounting for pagination, incremental criteria, asynchronous processing, and event payloads that may contain only identifiers.
Instructions in Martini
- Call the permitted ADP REST endpoint
- Process pages and persist a synchronization watermark where supported
- Follow up event notifications with a GET request when full resource state is required
- Poll approved asynchronous jobs or retrieve approved reports and files when applicable
Objective
Coordinate API calls, enrichment, validation, branching, and downstream actions in a maintainable Martini workflow rather than embedding the entire process in a one-off script.
Instructions in Martini
- Separate intake, retrieval, transformation, and delivery stages
- Use reusable workflow logic for common authentication, validation, and retry behavior
- Route authorization, validation, throttling, and transient failures separately
- Persist correlation identifiers and processing status
Objective
Convert ADP Workforce Now objects into canonical models and target-specific payloads while preserving identifiers, effective dates, and relevant status transitions.
Instructions in Martini
- Map Worker, Person, Position, Pay Statement, or Time Off Request fields
- Normalize dates, amounts, codes, and organizational identifiers
- Treat optional and product-specific fields defensively
- Minimize sensitive payroll and personal information in downstream messages
Objective
Enforce source-of-truth, authorization, effective-date, privacy, and idempotency rules before writing or submitting data.
Instructions in Martini
- Check that the ADP application is permitted to perform the requested operation
- Use stable identifiers or transaction keys to prevent duplicate effects
- Distinguish effective dates from transaction timestamps
- Validate required fields and route business exceptions for review
Common ADP Workforce Now data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Worker | Represents employee or contingent-worker identity, employment status, organizational assignment, and related workforce information. | Microsoft Entra ID, ServiceNow, Salesforce, Workday, UKG Pro | Martini retrieves Workers through permitted REST APIs, applies pagination and incremental criteria where available, maps stable identifiers, and performs idempotent downstream upserts. |
| Person | Contains personal and demographic information associated with a worker. | Salesforce, ServiceNow, SAP SuccessFactors, Workday | Martini applies data minimization, maps only approved attributes, handles optional fields and effective dates, and restricts sensitive values in logs and downstream payloads. |
| Position | Describes job, position, department, location, and organizational assignment details. | Salesforce, ServiceNow, Microsoft Entra ID, data warehouses | Martini normalizes organizational identifiers, enriches Worker messages with Position data, and applies source-of-truth and effective-date rules before writing targets. |
| Pay Statement | Provides payroll results and earnings information for a worker and pay period. | NetSuite, finance applications, data warehouses | Martini retrieves permitted payroll data, minimizes sensitive fields, transforms pay-period and earnings values, and uses strict authorization, retention, and idempotency controls. |
| Time Off Request | Represents requested, approved, denied, or cancelled absence information. | ServiceNow, UKG Pro, Workday, workforce applications | Martini synchronizes status transitions and dates, accounts for time zones and effective dates, and submits changes only where the selected ADP API and permissions allow it. |
| Payroll Instruction | Represents payroll-related instructions or changes submitted for processing. | NetSuite, finance applications, payroll operations | Martini validates business rules, records transaction identifiers, submits only supported operations, and separates validation, authorization, transient, and duplicate failures. |
Authentication and security considerations
OAuth 2.0 and application authorization
ADP Workforce Now APIs use OAuth 2.0 with application credentials, scopes, customer consent, and tenant or organizational context as required by the selected API. The exact grant and authorization process depends on the ADP application and product.
Protecting workforce and payroll data
- Store client credentials and tokens in Martini secrets or protected environment configuration.
- Use separate sandbox and production applications, credentials, and endpoints.
- Apply least-privilege scopes and minimize personal and payroll data sent to downstream systems.
- Use encrypted transport and avoid writing full payroll payloads or access tokens to logs.
Operational considerations for ADP Workforce Now integrations
Rate limits and pagination
ADP may apply quotas, concurrency limits, or tenant-specific throttling. Martini workflows should use bounded concurrency, process pages reliably, avoid repeated reads, and retry transient or throttling failures with backoff.
Events and idempotency
Event coverage is selective and notifications may contain only identifiers. Validate and record event metadata, check for duplicate delivery, retrieve authoritative resources when needed, and acknowledge promptly before longer processing.
Effective dates and schema changes
Worker, payroll, and absence data can contain future-dated changes, pay-period boundaries, status transitions, and historical versions. Use version-aware mappings, optional-field handling, contract tests, and reconciliation workflows to manage schema or permission changes.
Testing and recovery
Test with representative non-sensitive data in the ADP sandbox, classify authentication, validation, throttling, transient, and duplicate errors separately, and persist failed transactions for controlled replay.
Why use Martini instead of scripts or point-to-point integrations?
Centralized orchestration
Martini provides a maintainable workflow layer for authenticating to ADP Workforce Now, retrieving related objects, applying business rules, and delivering data to multiple enterprise systems.
Reusable transformations
Instead of repeating mapping and error logic across point-to-point scripts, teams can create reusable mappings, canonical models, validation rules, and API-based integration assets.
Operational control
Scheduled workflows, event intake, checkpoints, retries, reconciliation, and monitoring provide greater control over pagination, duplicate notifications, transient failures, and effective-dated HR data.
Controlled API exposure
Martini can expose a governed API façade over selected ADP operations, allowing downstream applications to use a stable contract while Martini manages ADP-specific authentication, transformations, and routing.
Frequently asked questions
ADP Workforce Now can be integrated primarily through ADP REST APIs for workforce, payroll, time, talent, benefits, and related capabilities. Selected ADP products also provide event notifications, while some configurations may support asynchronous processing, reports, or file exchange. Access depends on the customer’s modules, permissions, application approval, and tenant configuration.
Yes. Martini can consume ADP Workforce Now REST APIs using OAuth 2.0, receive supported ADP event notifications through Martini APIs and workflows, schedule synchronization processes, transform ADP objects, and deliver data to enterprise applications. No native Martini ADP Workforce Now connector is documented in the supplied materials.
No. A dedicated ADP Workforce Now connector is not required. Martini can integrate using ADP’s confirmed native mechanisms, including REST APIs, OAuth 2.0 authorization, selected event notifications, and approved product-specific file or report exchanges.
Lonti does not charge an additional per-connector or per-vendor fee to integrate ADP Workforce Now. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from ADP, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
REST APIs should be the primary method for new integrations because ADP documents them across workforce, payroll, time, talent, benefits, and related capabilities. Selected event notifications can support near-real-time processing, while batch, asynchronous, report, and file options should be confirmed for the specific ADP product and customer configuration. GraphQL and general-purpose SOAP APIs were not confirmed.
ADP provides event-notification capabilities for selected business events and API products, but coverage is not universal across Workforce Now objects or operations. Martini can receive supported notifications, validate and deduplicate them, retrieve the current ADP resource when necessary, and process downstream actions through a workflow.
Martini can use paginated REST requests, modified-date or effective-date criteria where available, persisted synchronization watermarks, stable ADP identifiers, and idempotent upserts. Scheduled reconciliation remains important because event coverage may be selective and event delivery may be repeated or interrupted.
Yes. Martini can expose a controlled REST API that abstracts selected ADP Workforce Now operations, applies authorization and business rules, transforms requests and responses, and prevents downstream consumers from depending directly on ADP-specific payloads. The underlying ADP operation must still be available and permitted for the customer’s application.
Related Martini documentation
Workflows
Build reliable ADP Workforce Now integrations with Martini
Use Martini to connect ADP Workforce Now APIs and supported event notifications with your enterprise applications through governed workflows, secure authentication, data transformation, and operational controls.