Integrating Darwinbox with Empuls for automated user data management
Seamlessly integrate Darwinbox with Empuls for swifter and automated user data management.

Why This Integration?

This integration automates the user account management processes in Empuls based on the employee data available in Darwinbox, letting you appreciate and recognize your team members directly and instantly through your already existing Darwinbox framework.
With this integration, you can :
  • Add new employees to Empuls automatically as soon as their Darwinbox profile is created.
  • Edit existing employee data in Empuls simply by updating their Darwinbox profile.
  • Remove exited employees from Empuls based on their exit date in Darwinbox.
Once this integration is enabled, the data will sync between Empuls and your Darwinbox account once every 24 hours.
This article will show you how to set up your Darwinbox integration and go on a strategic recognition spree.

How To Set This Integration Up

Contact your Darwinbox account manager and request him to share the below client details concerning your Darwinbox account.

Client Details Needed from Darwinbox:

  • Email: Email registered with Darwinbox
  • Domain: HRMS domain name
  • UID: UID (Unique Identifier)
  • Secret Key
  • Active Dataset Key[1]

Data Fields Required from Darwinbox

We need the below keys from Darwinbox in 2nd JSON format, with respect to your account account on Darwinbox:
darwinboxKeyMap = { first_name: 'first_name', last_name: 'last_name', email: 'company_email_id', grade_name: 'grade', address: 'office_area', city: 'office_city', department: 'department_name', contact: 'primary_mobile_number', emp_id: 'employee_id', joining_date: 'date_of_joining', dob: 'date_of_birth', designation: 'designation_name', manager_email: 'direct_manager_email', hr_email: 'hrbp_email_id', department_head_email: 'hod_email_id', employee_status:'employee_status' }
{ "email": "<Email registered with Darwinbox>", "domain": "<HRMS domain>", "uid": "<UID>", "secretKey":"<Secret>", "activeDatasetkey": "<Key>", "inactiveDatasetKey":"<Key2>" }
Once the client details are provided to us, we will go ahead and set up the integration based on your guidance.
Last modified 2mo ago