Web Services SaaS Connector | How to pass attribute received in JSON response (of Create Operation) in GetObject Request URL?

[SailPoint_Learner (Nisha Usman)]

Hi Experts,

I’m working on “Web Services SaaS Connector” and for one of the applications:

1. Create operation response is: {"isSuccess: true, "message": "account has been created", "data": {"userId": Dynamically generated integer}}
2. As account created in target is not displayed in IdentityNow until Account Aggregation is executed and Add Entitlement Operation requires userId to be passed in request body so I added getObject operation to bring the account in IdentityNow right after account creation.

Request URL for getObject call is https://…/…/userId.

I’ve tried these Request URLs for getObject but none of them has worked:

1. https://…/…/$getObject.nativeIdentity$
2. https://…/…/$plan.nativeIdentity$
3. https://…/…/$response.data.userId$
4. https://…/…/$output.attributes.data.userId$

Other options tried to execute getObject, but they didn’t work:

1. Added Account Aggregation as Child of Create Account EndPoint
2. Added another Create Account Operation to execute getObject

Have I missed anything? Could you please advise on this?

[shekhardas1825 (Shekhar Das)]

@SailPoint_Learner There is a similar post of resolving the issue, you have to write a afterOperation connector rule:

Webservice Connector - Create Account Operation - Empty Response - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community

You may also look into below:
Create Account returns id(nativeIdentity in the schema), it is not getting mapped - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community

[SailPoint_Learner (Nisha Usman)]

Thanks for responding @shekhardas1825.

As this is Web Services SaaS Connector, rules won’t work.

I tried implementing customizers but getting this error while debugging:

node:internal/child_process:421
throw new ErrnoException(err, ‘spawn’);

I tried adding shell:true in environment variable to fix this error but that also didn’t work.

Any other suggestion?