One-directional integration between Workday and SailPoint - Looking for bidirectional

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Which IIQ version are you inquiring about?

8.3

We currently have a one-directional integration between Workday and SailPoint, which has worked well for us so far. However, HR has approached us to explore solutions for managing contractors across the organization.

For example, in our Contact Center, we have around 35 offshore EXL contractors handling calls. We’re trying to determine the best approach for onboarding and offboarding these types of non-employees.

Specifically, we’re interested in understanding:

  • What options are available for enabling SailPoint to feed data back into Workday (e.g., for contractor onboarding and termination)?

  • Whether a bidirectional integration is recommended in this scenario, or if there are better practices for handling contractor lifecycle management

  • How others are managing external/contractor identities while keeping Workday as the system of record (or not)

We’d appreciate any insights, recommended architectures, or lessons learned from those who have implemented similar solutions.

Please share any images or screenshots, if relevant.

[Please insert images here, otherwise delete this section]

Please share any other relevant files that may be required (for example, logs).

[Please insert files here, otherwise delete this section]

Share all details about your problem, including any error messages you may have received.

[Replace this text with the problem that you are facing]

2

Yes, this is usually not true bidirectional OOTB.

In most setups, Workday stays the source of truth and SailPoint just consumes the data from it. If you want SailPoint to push something back into Workday, that normally has to be done through a separate API/web service pattern, not as native reverse sync.

So practical answer is:
• Workday → SailPoint = standard authoritative feed
• SailPoint → Workday = custom writeback using API / middleware / workflow

That writeback is usually only for specific controlled attributes or business actions, not full bidirectional identity management.

1 Like
3

Hi @Nara

If the suggestion solves your problem please mark it as a solution.

If you still have doubts feel to ask.
Happy to help

4

@Nara the recommended approach here,

a. Make workday as authoritative for employee and contractor but in Sailpoint based on workerType you can differentiate Employee and contractor and manage lifecycle.

b. Make workday as authoritative for employee and sailpoint as authoritative for contractor (read from External source EXL ) and Mange Contractor lifecycle in SailPoint.

c. Bidirectional approach - Workday REST APIs but this is little risky and rollback is little complex and hard.

but all options possible.

thanks,

Pravin

5

Hi @Nara ,

Provisioning to Workday is possible from Sailpoint IIQ.

Please refer Connector document for specific IIQ version in which you working.