Skip to content

HR Data Definition (Paylocity Webhook Integration)

Here, you'll find the details on setting up Paylocity webhook integration with H2R and how webhooks function within H2R.

Setting Up Webhook Connection on Paylocity Portal

Prerequisites

  • Webhook configurations are available only for active Paylocity customers or Technology Partners.
  • Identify which webhooks need to be configured. The available webhooks are:
    1. New Hire Webhook – Triggers when a new employee is added to Paylocity, enabling integration with other systems.
    2. Employee Change Webhook – Activates when an employee's details are updated in Paylocity, notifying relevant systems of the change.
    3. Termination Webhook – Initiates upon an employee's termination, informing connected systems of the status change.
    4. Future Dated Change – Not a separate webhook but a special behavior where an event is scheduled for a future date. The webhook triggers when the scheduled date arrives, not when the update is made in the HR system. If users want the event to trigger upon an update in Paylocity Portal, they should map future-dated data using a custom attribute or another suitable field. For more please connect with our Customer Support Team.

To configure a webhook in the Paylocity portal:

Paylocity API Full Load

Figure 1. Paylocity Webhook.
  • Use the provided endpoint URL, which is unique for each workflow and acts as the subscription URL in Paylocity.
  • Include custom headers containing an authorization value, which the H2R uses to validate incoming webhook requests.

Since Paylocity does not provide a predefined mechanism to confirm a successful connection, please contact our Customer Support Team to test the integration after setup.

How Webhook Integration Works in H2R

When a user enables the webhook option on the HR Data Definition Page and deploys the flow:

  • The secret key in the custom header is stored in H2R Server and will be linked to the flow.
  • Incoming webhook requests are validated against the request route and authorization key in the header. If valid, the system returns a 200 OK response; otherwise, it returns 401 Unauthorized or 500 Internal Server Error based on the issue.

According to Paylocity’s documentation, webhook notifications may not always contain all updated information fields. In some cases, a single user-triggered change can lead to automated system updates affecting the same data object. Therefore, additional API calls using the provided companyID and employeeID values may be required to retrieve the latest data.

To ensure data consistency, users can choose between periodic synchronization or a one-time full sync when integrating Paylocity webhooks.