Integrate ServiceNow with Workday to populate HR Profile table

[Kajal28]

Hi All, 

I hope all are well. 

Can anyone please help me with below?

- What are the best/optimized integration options to get HR Profile data from MuleSoft Workday into ServiceNow? I know we can do API integrations, but ServiceNow is evolving everyday, suggestions on any OOTB/custom options that would be an efficient method to achieve this integration would be greatly appreciated.

[GlideFather · Accepted solution]

Hi @Kajal28,

I created an integration Workday > Mulesoft > ServiceNow, it was only one-directional and for that I used Import set (staging) table where the data are received from WD (eventually MS) and from this table I transformed them to User [sys_user].

You create a custom table extending the [import_set] table, so no licence is consumed, also an endpoint in SN, a service account, give this account permission to write to your staging table.

The staging table will have all the fields string fields and then you just create the mapping, with this remember that even active will be u_active because it's a new custom field and the mapping will be u_active in staging to active in User etc...

This was very effective and yet easy method how to achieve this.

Let me know if this sounds good to you, I'll try to recall more details

[Kajal28]

Thankyou for the detailed explanation. We plan to follow a similar process. 

But do have knowledge on "Enterprise Service Management Integrations Framework" : https://www.servicenow.com/docs/bundle/zurich-employee-service-management/page/product/human-resourc... 

if yes, do you think this will help us with the integration we are planning to achieve?

If you can mention any pros/cons that would be great. 

[GlideFather]

@Kajal28 It was very simple and easy to maintain, also easy to debug. However it was probably the most simple integration ever :)) 

the biggest challenges was the data accuracy which was at Workdays team responsibility .

Pro - when a message was sent from WD it updated ServiceNow instantly, no need for 2 or 4 hours mass updates like in LDAP and neither the manual pull. Staging table was a source of logs, so very easy to debug as mentioned, if updated directly it would be messier.

i no longer have access to that environment but i will try to remind something