Skip to main content
This article covers the standard ADP Workforce Now connector, which is powered by Lumos partner Merge.dev and sources HRIS user data through a guided pop-up flow. To authenticate directly against the ADP API with your own ADP Marketplace application and enable write-back provisioning actions, use ADP Workforce Now (Direct API) instead. Follow the section that matches the connector card on your Lumos integrations page.

​
After this article

You will be able to connect ADP Workforce Now to Lumos as a source of user data through the Merge.dev-powered pop-up flow.

​
Capabilities

​
Required plan and roles

  • Lumos plan: no minimum plan requirement is documented for this integration.
  • ADP role: you must be an Administrator in your company’s ADP instance, or someone must have shared their access with you.
  • Region: ADP Workforce Now Canada is not supported by this connector.
  • Provisioning / write-back: this Merge-powered connector sources user data only. To provision back to ADP (hire, terminate, rehire, work-assignment changes, business email updates) you register your own ADP Marketplace application, obtain a Client ID and Client Secret, enable the required worker scopes (worker.read plus the write scopes), submit a CSR and install the signed X.509 certificate, and configure the SSL certificate and private key on the connector. That path is the ADP Workforce Now (Direct API) connector. Use its doc for those steps rather than this one.

​
Read-only access vs provisioning

Is read-only possible? Yes, and it’s the only mode this connector supports. The standard ADP Workforce Now connector sources user, group, and role data through Lumos partner Merge.dev and has no write-back path. What read-only requires. An ADP Administrator (or someone who has shared their ADP access with you) completing the Merge.dev-powered pop-up flow. Follow the steps below. ADP Workforce Now Canada is not supported by this connector. What full provisioning requires. A different connector. Actions like hire, terminate, rehire, work-assignment changes, and business email updates require the ADP Workforce Now (Direct API) connector, which authenticates with your own ADP Marketplace application (Client ID and Client Secret), the worker.read scope plus the required write scopes, a CSR submitted to ADP for a signed X.509 certificate, and that certificate and its private key configured on the connector. Watch out for. Moving from this connector to Direct API is a separate connection on a separate connector card, not an upgrade of this one. If you only need ADP as a source of user data, keep using this connector and set it as a source of truth for joiner/leaver information rather than switching.

​
Instructions

Phase 1: Connect in Lumos
  1. Click the ADP Workforce Now card in your Lumos integrations (reconnect an existing card or add a new one).
  2. Click Connect ADP Workforce Now and follow the instructions in the pop-up that appears. Lumos partner Merge.dev guides the flow. Review Merge.dev documentation for integration requirements. (A “How do I link using a practitioner role?” link is referenced in the flow if you connect that way.)
  3. After connecting, set ADP Workforce Now as a source of user data in Lumos if you want it to drive joiner/leaver information (see the Source of Truth settings).

​
Troubleshooting

Intermittent “Invalid credentials for this integration” banner. This banner is a generic wrapper Lumos raises whenever any Merge data model reports a failed status during the nightly sync, regardless of the real cause. That includes transient failures on Merge’s own sync from ADP (for example, a failed Employee model on the Merge-to-ADP leg). If it appears some nights and clears on others, the credentials are fine and the connection restores itself after the next successful overnight sync, so no reconnect is needed. For persistent failures, check the Merge dashboard sync logs for the linked account to see what ADP actually returned. Cannot connect / ADP Workforce Now Canada. ADP Workforce Now Canada is not supported by this connector. A sync has been “in progress” for many hours — is it stuck? Not necessarily. Sync duration varies with data volume, and long ADP Workforce Now syncs (12+ hours) can still complete successfully with no error. Wait for it to finish before treating it as failed.