Set up a Paylocity Weblink connector

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:

Resource	Sync	Provision
Accounts		Disable

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.

Action name	Additional fields	Description
disable_user	`user_id` (string, required)	Terminates an employee in Paylocity (sets status to Terminated).
create_user	`first_name` (string, required) `last_name` (string, required) `email` (string, personal email — maps to `homeAddress.emailAddress`) `position_code` (string) `employee_type` (string) `cost_center_1` (string) `job_title` (string) `hire_date` (string, `MM-DD-CCYY` or `CCYY-MM-DD`) `employee_status` (string)	Creates a new employee in Paylocity WebPay. Returns the new `employee_id` on success.

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.

Gather Paylocity Weblink credentials

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.

Create or locate an API client with the WebLinkAPI scope:

If you don’t already have Weblink API credentials, contact Paylocity support to request Weblink API access for your company
Once enabled, create a new API client or use an existing one
Ensure the client has the WebLinkAPI scope

Copy and save the following values:

Client ID: The OAuth2 client ID
Client Secret: The OAuth2 client secret
Company ID: Your full Paylocity company ID including the suffix (e.g., 347766RCU). Using only the numeric prefix will cause 403 errors.
API Gateway URL: The Weblink API gateway URL for your environment:
- Sandbox: https://dc1demogw.paylocity.com
- Production: https://api.paylocity.com

The Company ID must include the full alphanumeric value with its suffix (e.g., 347766RCU). The numeric-only prefix (347766) will authenticate successfully but return 403 errors on all data endpoints.

Configure the Paylocity Weblink connector

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

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Integrations > Connectors and click Add connector.

Search for Paylocity Weblink and click Add.

Choose how to set up the new Paylocity Weblink connector:

Add the connector to a currently unmanaged app
Add the connector to a managed app
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

Click Next.

Find the Settings area of the page and click Edit.

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): Your full Paylocity company ID with suffix (e.g., 347766RCU)
API Gateway URL: Defaults to production (https://api.paylocity.com). Override only for sandbox/testing (e.g., https://dc1demogw.paylocity.com).

Click Save.

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.

Follow these instructions to use the Paylocity Weblink connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals.

Resources

Official download center: For stable binaries (Windows/Linux/macOS) and container images.
GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Paylocity Weblink connector

In C1, navigate to Integrations > Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Paylocity Weblink connector:

Add the connector to a currently unmanaged app
Add the connector to a managed app
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

Click Next.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Paylocity Weblink connector deployment:

Secrets configuration

# baton-paylocity-weblink-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-paylocity-weblink-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Paylocity Weblink credentials
  BATON_PAYLOCITY_CLIENT_ID: <Paylocity OAuth2 client ID>
  BATON_PAYLOCITY_CLIENT_SECRET: <Paylocity OAuth2 client secret>
  BATON_PAYLOCITY_COMPANY_ID: <Paylocity company ID with suffix, e.g. 347766RCU>
  BATON_PAYLOCITY_BASE_URL: <Weblink API gateway URL, e.g. https://api.paylocity.com>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-paylocity-weblink.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-paylocity-weblink
  labels:
    app: baton-paylocity-weblink
spec:
  selector:
    matchLabels:
      app: baton-paylocity-weblink
  template:
    metadata:
      labels:
        app: baton-paylocity-weblink
        baton: "true"
        baton-app: paylocity-weblink
    spec:
      containers:
      - name: baton-paylocity-weblink
        image: public.ecr.aws/conductorone/baton-paylocity-weblink:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-paylocity-weblink
        envFrom:
        - secretRef:
            name: baton-paylocity-weblink-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Paylocity Weblink connector to. Paylocity Weblink data should be found on the Entitlements and Accounts tabs.

Done. Your Paylocity Weblink connector is now pulling access data into C1.

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

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Paylocity Weblink connector

Capabilities

Connector actions

Gather Paylocity Weblink credentials

Configure the Paylocity Weblink connector

Resources

Step 1: Set up a new Paylocity Weblink connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Connector actions

​Gather Paylocity Weblink credentials

​Configure the Paylocity Weblink connector

​Resources

​Step 1: Set up a new Paylocity Weblink connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Connector actions

Gather Paylocity Weblink credentials

Configure the Paylocity Weblink connector

Resources

Step 1: Set up a new Paylocity Weblink connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector