Web Services Connector - Using information from two parent endpoints

Hi all,

We have a use case for provisioning with our web services connector in which the third call in the chain needs to use information from the responses of two different parent calls. For example, data is returned in the response of the first call that is no longer present in the response of second call but will still be needed in the third. (Call 1 returns X β†’ Call 2 uses X and returns Y β†’ Call 3 uses both X and Y)

Has anyone seen a configuration like this before, and if so, how did you make the first call’s data accessible as a variable for the request body of the third call? Any help is appreciated, thanks!

1 Like

There is an example that Fernando has put together that uses transientValues that should persist through calls for the same operation. Take a look here: SailPoint IdentityNow - Introduction to loopback connectors

1 Like

This is super helpful thanks! We’ll take a look and see if we can use this to keep values from our first call around for our third call to use.