Note: This integration is dependent on WorkTango User Management.

Reach out to WorkTango Customer Success to enable the ADP integration on your platform. IMPORTANT: This step must be completed prior to purchasing the WorkTango Connector through the ADP Marketplace. You must be on Kazoo user management to use the connector.

After WorkTango CS has enabled the ADP integration, it will be visible in your platform.


ADP1

You can then use the “Purchase WorkTango in ADP Marketplace” button to navigate to ADP and purchase the connector, or access via this direct link. NOTE: It is very important that the person responsible for purchasing the connector is both a WorkTango administrator and an ADP administrator.

ADP2

Once purchased, you will need to provide consent to connect the two applications together. Do this by actioning the “Provide consent” button.

ADP3

Once the WorkTango App has been purchased from the ADP marketplace and consent has been given, ADP status will display “Connected”.

ADP4

Once connected, you can configure how your integration works.

  • Choose your unique identifier (email address or ADP Employee ID)
  • “Auto sync”: This connects ADP to WorkTango for a full update on a 24 hour basis, and updates the following employee status details on an hourly basis; name changes, email changes, new hires, termination, rehire, and on leave.
  • “Send welcome email to new users”: This sends welcome emails when new users are synced from ADP to WorkTango
  • “Archive missing users”: If a user is removed from ADP, they will automatically be archived in WorkTango.
  • “Sync now” button: This starts an immediate sync between the platforms.
  • “View sync history” button: This sakes you to the import history page.

How Data Syncs

WorkTango pulls and maps very specific fields from ADP. We are limited to importing these exact fields. We cannot substitute, change, or pull in any additional fields.

WorkTango Field → ADP Field
Name fields are edited in the employees personal profile by editing the Name section.

  • First Name → /workers/person/legalName/givenName
  • Last Name → /workers/person/legalName/familyName1
  • Preferred Name → /workers/person/legalName/nickName preferredName overrides firstName in certain cases in the KW UI, but both values are imported to kw users and stored in our database. both are available from the KW User’s edit user UI
    image

Email is edited in the employees personal profile by editing the Contact section. NOTE: Only the work email field is pulled into Kazoo.

  • Email → /workers/businessCommunication/emails/emailUri
    image

Birthdate is edited in the employees personal profile by editing the Demographics section.

  • Birthdate → /workers/person/birthDate image

User Status & Start date is edited on the Employment Profile page by editing the users Status info.

  • User Status → /workers/workerStatus/statusCode/codeValue
  • Start Date → /workers/workerDates/originalHireDate
    image

Employee ID is edited on the Employment Profile page by editing the users Employment info

  • Employee ID → /workers/workerID
    image

Assigned manager is edited on the Employment Profile page by going to the Position section and by click the pencil on reports, you can then edit the Reports to info.

  • Unique identifier = email: /workers/workAssignments/reportsTo/associateOID to look the manager up and find their email address
  • Unique identifier = employeeId: /workers/workAssignments/reportsTo/workerID/idValue image

Title/Position & Country are edited on the Employment Profile page and editing the Position section

  • Title (primary)→ /workers/workAssignments/jobCode/shortName
  • Title (fallback)→ /workers/workAssignments/jobCode/longName
  • Country →/workers/person/legalAddress/countryCode image

Department annd Location are edited on the Employment Profile page by editing the Corporate Groups section. There can be multiple Corporate Groups (one per position) and we will first attempt to pull the data related to the default position.

  • Department → /workers/workAssignments/homeOrganizationalUnits
    • homeOrganizationalUnits is an array. we filter for the value where typeCode.codeValue === “Department” and then return either nameCode.shortName or nameCode.longName
  • Location → /workers/workAssignments/homeWorkLocation/cityName image

Department and Location Structure

Kazoo user management can support a hierarchical relationship between departments or locations. For example, your “Marketing” department could have a child department of “Social Media Management.”

However, please note that this integration does not import any hierarchy information from ADP.

This means if your organization has a hierarchical structure for departments or locations already established in ADP, this structure will need to be recreated in Kazoo. Once your hierarchy is set up in Kazoo, that structure will persist through new imports.

Important: Each department and location group will have a unique identifier in Kazoo called a group key. When users are added or updated via import, you must be certain that the group keys match to avoid duplication of departments or locations.

As a result, we recommend establishing your hierarchical structure in Kazoo after users, departments, and locations have been imported via the ADP integration to ensure group key consistency.

Enabling the ADP connector after you have launched Kazoo.

If you are actively using the Kazoo platform, and want to turn on the ADP connector we recomend that you go through the following steps to validate your data prior to syncing the two platforms.

  • Please connect and work with the Kazoo Customer Success team to run exports from ADP and Kazoo to confirm that the user data between the two platforms match. You will want to export the fields outlined above in the ‘How Data Syncs’ section from ADP and compare that to your Kazoo user export to validate that user emails, IDs, departments, etc are all 100% correct.
  • ADP is the system of truth, and you as our customer are responsible for your data in ADP. Any data that you want in Kazoo needs to exist inside ADP before turning the connector on.
  • The connector does not import department hierarchy, this has to be manually uploaded via CSV after the initial ADP integration is run. The hierarchy will persist after is created in Kazoo
  • The connector does not import point rules. These have to be configured in Kazoo, and they will persist on the users on subsequent imports. This may be a blocker to wanting to use the connector.