When setting up a Hire2Retire workflow to automate employee lifecycle between HRIS systems and Active Directory (AD), you have the option of an API-based or an extract-based integration with HRIS to get employee lifecycle events. In this article, we will go over the pros and cons of each integration approach to help you make the right choice for your organization.
With an extract-based integration, Hire2Retire will get data from the HRIS system as a file either pushed by HRIS or pulled by RoboMQ. The file-based extract is delivered to RoboMQ securely with RSA Key based authentication and encryption to ensure data integrity, privacy, and security.
The setup process of extract-based integration is extremely straightforward and easy to implement. The data is extracted from the HR system and processed by Hire2Retire finally landing on AD or Azure AD as an identity profile. This integration promotes superior guaranteed delivery and data integrity as the SFTP based transfers are less error-prone and maintain guarantees of delivery at a bulk record level. This is further ensured by RoboMQ through its use of message-queue based transport. Also, you can control what you share with third parties like RoboMQ by strictly choosing what employee profile attributes are sent by HRIS.
However, since extract-based integrations operate on a batch processing model, the data is processed periodically or in a schedule-based way rather than in near real-time. Also, in this option, the one-time setup engagement with HRIS tends to consume time and may incur delays depending on the responsiveness of the vendor.
With an API-based integration, data transfer and communication happen over well–defined, published, and standardized application programming interfaces. A real-time connection is established between the HR system and RoboMQ to get employee lifecycle events which are processed to AD or Azure in AD in near real–time.
Since, the APIs are already published by the HRIS vendor, and the setup is as easy as authenticating an API key, almost no setup is needed in this option. With API-based integration, the data sync operation between HR and AD or Azure AD is swift resulting in near real-time updates to AD identity profile. Also, in API-based integration, you can write back to email or other AD data to HR, automatically sending some crucial information back to the HR system and further automating the Hire2Retire process.
On the other hand, this integration is dependent on APIs to be provided and published by the HR system vendor. Furthermore, data elements that are shared are determined by the HR vendor and the customer cannot choose what not to send. However, RoboMQ will process only the attributes that are required by the employee lifecycle and identity provisioning workflow for the customer and discard the rest reducing the impact of this con.
We understand each organization has unique resources and objectives, and it may not be a simple decision to pick a data integration method that aligns with your needs and goals based on generalized facts. You can always Speak to an Integration Specialist at RoboMQ to compare these two integration methods and make an informed decision to kickstart your automation journey with Hire2Retire.