AlertFind ExponentHR Connector
Written by John Pereira
Looking to automate AlertFind Data import? Yes! This is the place to be. Our ExponentHR Connector will make automation a breeze!
In order to perform a successful connection to your ExponentHR instance, we just need the following information and that's it!
1. Client ID: This client ID is provided by the ExponentHR when they create the instance also can be found in the settings with an admin account.
2. Authentication Key: This key can be provided by ExponentHR when the instance was configured or you can find it in the settings of the instance.
Once we have a successful connection, it will enable us to populate your AlertFind instance with the following information:
- Employee Name
- First Name
- Last Name
- Middle Name
- Cell Phone 1
- Cell Phone 2
- Personal Email
- Employee ID
- Master ID
- Job Title
- Job Code
- Location
- Location Code
- Division
- Division Code
- Department
- Department Code
- Emergency Contact
- Emergency Phone 1
- Emergency Phone 2
- Emergency Relationship
How does our ExponentHR connector works
The below graphic explains the various nodes involved in the transition of data from your ExponentHR instance to AlertFind.
Detailed Steps Explaining Above Graphic:
1. ExponentHR 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 ExponentHR system.
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:
- Node 5: Refers to Apache Cassandra Cluster which stores the data for execution purposes. It has a TTL of 7 days after workflow execution finished.
- Node 6: Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.
- 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 Services (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?