Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Webhook Connectivity

You will need to request Paylocity to setup webhook for your use cases e.g. new hire, termination, etc. This link provides more information about their process. Use the form specified in step-4 to provide relevant details. The URL, username and password can be copied once new webhooks are created in OnLink. See this link for reference.

image-20240108-173432.png

Once you have authorization, you can create a new webhook in OnLink with Paylocity as the system and the below config:

map:employeeFirstName=customfield_10122
map:employeeLastName=customfield_10123
config:summary='Paylocity Inbound: ', [0], ' ', [1]
config:auth_scheme=basic_auth
config:auth_username=<enter a username>
config:auth_password=<enter a password>

Additional mapping fields can be added. See Mapping section below for common fields you can map from Paylocity.

API Connectivity

You will need to request Paylocity for API credentials. This link provides more info on the information you will receive when API Access is granted i.e., client id and client secret.

The Paylocity connector lets you connect to a Paylocity instance and access Paylocity HR resources using their published APIs.

Ref: https://prod.cdn.paylocity.com/developer/index.html

Mapping

Here are some common fields you can map from Paylocity

employeeId
employeeJobTitle
employeeFirstName
employeeLastName
employeeHireDate
employeeGender
employeeSupervisor
employeeSupervisorId
employeeType
employeeWorkEMailAddress
employeeWorkPhone
employeeCity
employeeZip

More fields can be found in this link.

  • No labels