In order to perform a successful connection to your Paylocity instance, we just need the following information and that's it!

  1. Environment: You must provide to which environment we are connecting if it is Production or Sandbox.
  2. Client ID: Please provide your client ID.
  3. Client Secret: This can be found in the settings of the instance or can be provided by the Paylocity personnel.
  4. Public Key: This can be found in the settings of the instance or can be provided by the Paylocity personnel. Please copy and paste the whole text it will start with <RSAkeyvalue>

Once we have a successful connection, it will enable us to populate your AlertFind instance with the following information:

  • Employee ID
  • First Name
  • Middle Name
  • Last Name
  • Gender
  • Work info (Email, Phone, Phone Ext, Country, City , State, Address, Postal Code)
  • Home Info (Email, Phone, Mobile Phone, Country, City, State, Address, Postal Code )
  • Company Name
  • Employee Status
  • Job Title
  • Employee Type
  • Cost Center
  • Supervisor

How does our Paylocity Connector works:

The below graphic explains the various nodes involved in the transition of data from your Paylocity instance to AlertFind

Detailed Steps Explaining Above Graphic:

  1. Paylocity Connector fetches the user information stored in your instance via API.
  2. Based on your chosen frequency, our connector running on AWS Lambda fetches data from Paylocity.
  3. At this stage, data goes through the validation and processing and is finally transformed into a CSV.
  4. The CSV is compressed to a Zip file and sent to AlertFind API via the AlertFind Connector running on AWS Lambda.

Data Storage Nodes in Above Graphic:

  1. Node 5: Refers to Apache Cassandra Cluster which store data for execution purposes. It has a TTL of 7 days after workflow execution has finished.
  2. Node 6: Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.
  3. Data Safety: All data is encrypted in transit via HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames, passwords are encrypted at rest using Amazon Key Management Service (KMS) which uses FIPS 140-2 validated hardware security modules.

We encourage you to keep searching the connector that suits your needs in our main AlertFind Connector List under the section System of Records Integrations by clicking the button below.



Did this answer your question?