We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Workday SAM Pro Integration - Data Brought In

Go to solution
Cairns
Tera Expert

‎01-22-2026 03:58 AM

Hi all,

Looking for some insight from anyone that has set up the Workday/Sam Pro integration. We are in the process of currently setting it up and have been asked by the Workday teams what information/fields are fetched from Workday. With the integration accessing worker data they are interested as to what, if any, sensitive info will be fetched. The documentation about setting up the integration doesn't really specify what data is ingested into the Sam Pro system and I am struggling to find much more about it.

Has anyone set up or, is in the process of setting this up, and could share what type of data is being brought into the system?

We are now looking to see if we can interrogate the the sub-flows to see if this mentions anything specific but wanted to put this out the community as well.

Any information or advice is greatly appreciated.

Thanks in advance,
Cairns

Labels:
0 Helpfuls
  • 2,151 Views
1 ACCEPTED SOLUTION

Go to solution
Matthew_13
Mega Sage

‎01-22-2026 06:22 AM

Hi Buddy,

We’ve been through this discussion as well, and the short answer you can give the Workday team is: SAM Pro only pulls basic worker identity and employment data — nothing sensitive.

Out of the box, the Workday → SAM Pro integration is used strictly for license management and reconciliation, so it only brings in data needed to identify a worker and understand whether they should have software entitlements.

Typically, that means things like:

  • Worker / Employee ID

  • Name

  • Work email

  • Employment status (active / terminated)

  • Worker type (employee vs contingent)

  • Hire and termination dates

  • Org, cost center, or supervisory org

  • Business location

It does not pull compensation, SSN/national IDs, DOB, home address, bank details, benefits, performance data, or anything HR-sensitive.

The reason the docs feel vague is that the integration uses standard Workday worker APIs, and ServiceNow only consumes the fields it needs from whatever the Workday team exposes. If Workday doesn’t send it, ServiceNow can’t ingest it.

The best way to be 100% certain (and usually what satisfies HR) is to open the worker import subflows / mappings and show exactly which fields are being mapped into sys_user. That’s the authoritative list.

Unless someone customizes the integration or expands the API scope, the data footprint stays intentionally minimal.

 

@Cairns - Please mark Accepted Solution and Thumbs Up if you found Helpful

MJG

View solution in original post

5 REPLIES 5

Go to solution
Cairns
Tera Expert
In response to somachandra

3 weeks ago

Hi @somachandra ,

For us the data pulls into the subscription table (samp_sw_subscription). The data being pulled in is similar to other integrations:

  • User principal name
  • Product
  • Publisher

For this data to pull though, you have to ensure that the corresponding modules have been enabled in the Workday integration profile.

Hope this helps

Cairns