Skip to main content
Paylocity has two separate API systems. This connector uses the Weblink (legacy) API v2, which does not return sensitive PII fields (SSN, DOB, ethnicity). There is a separate Paylocity connector that uses the NextGen API.Use this connector if you need to avoid transmitting sensitive PII data to C1.

Capabilities

The Paylocity Weblink connector syncs the following resources:

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step. The create_user action mirrors the Paylocity Add Employee endpoint. Only first_name and last_name are required by the API; all other fields are optional. If employee_status is not provided, the action always defaults it to A (Active) so the new employee lands as a usable record. The action uses the v2 direct-create endpoint rather than the v1 /onboarding/employees flow. The v1 flow stages an employee that requires manual graduation in the Paylocity admin UI; the goal here is to produce a fully-usable employee from a single C1 automation step, not a draft awaiting human review. Compensation fields (pay rate, salary, pay type) are intentionally not exposed here. Those changes go through HR/payroll approval workflows in Paylocity and should be set in the Paylocity admin UI rather than provisioned through C1.
Reactivation (Terminated → Active) is not supported. The Paylocity Weblink API rejects that transition; customers who need to re-enable a terminated employee must do so through the Paylocity admin portal.
Configuring the connector requires you to pass in credentials generated in Paylocity. Gather these credentials before you move on.
A Paylocity administrator with access to the Web Pay portal’s Web Services settings must perform this task.
1
Sign in to the Paylocity Web Pay portal and navigate to Company > Setup > Integrations > Web Services.
2
Locate your Weblink API credentials:
  1. API access cannot be self-served — credentials are always issued through your Paylocity representative. If you don’t already have Weblink API credentials, contact your representative to request Weblink API access for your company
  2. Once access is granted, your API client is visible under Web Services
  3. Ensure the client has the WebLinkAPI scope
3
Copy and save the following values:
  • Client ID: The OAuth2 client ID
  • Client Secret: The OAuth2 client secret
  • Company ID: The company ID issued by Paylocity for this environment
  • API Gateway URL: The Weblink API gateway URL for your environment:
    • Sandbox: https://dc1demogw.paylocity.com
    • Production: https://api.paylocity.com
Demo/sandbox and production Company IDs are different values, and neither follows a fixed format. For example, a company’s demo ID might be 347766RCU while its production ID is 347766; some production IDs include an alphanumeric prefix. Use the company ID issued for the environment your API gateway URL points at — an ID used against the wrong environment will authenticate successfully but return 403 errors on all data endpoints. If you’re unsure which ID applies, confirm with your Paylocity representative.
To complete this task, you’ll need:
  • The Connector Administrator or Super Administrator role in C1
  • Access to the set of Paylocity Weblink credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Paylocity Weblink and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Enter the required configuration:
  • Client ID (required): Your Paylocity Weblink OAuth2 client ID
  • Client Secret (required): Your Paylocity Weblink OAuth2 client secret
  • Company ID (required): The Paylocity company ID issued for this environment (demo/sandbox and production company IDs are different values)
  • API Gateway URL: Defaults to production (https://api.paylocity.com). Override only for sandbox/testing (e.g., https://dc1demogw.paylocity.com).
9
Click Save.
10
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your Paylocity Weblink connector is now pulling access data into C1.

All versions of this connector are available at dist.conductorone.com.