Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
I am New to ISC and recently faced an issue while configuring a SaaS Web Services connector in IdentityNow tenant , and wanted to share in case others faced something similar.
My Test Connection was passing successfully, but when I ran Account Aggregation it was successful but in accounts it’s showing 0
There could be two issues
This typically means your API call works, but ISC cannot parse the response due to mapping, JSON structure, or root‑path issues. kindly check all these.
Adding to @Deepak_Chaudhary comment, please check whether it returns response in Postman and that gives you a fair idea about the response payload.
I agree with both of the suggestions from these users.
The Success message is just stating that it ran through the process and completed without error, since 0 results is a valid return number for aggregations.
As @Deepak_Chaudhary suggested, some of the common issues are the configurations of the response to the specified schema attributes. These are the most common areas I see when setting up the connectors.
As @suresh4iam Expands on, using Postman or Bruno (or other API Tool) to test the calls outside of ISC to verify they are working and return values is a good thing to do. It will also allow you to verify that you have the correct Parameters being sent. The returned results can also be seen, and allow you to review your mappings to verify they are correct too.
If you are using any rules with the Web Service connector, make sure that you are returning the correct objects and values from there also.
@gmilunich @suresh4iam Thanks for the explanation and consideration.
you can troubleshoot with the below:
Step 1: Enable Logging in Web Services Connector configuration
Turn on “Show Debug Info” → run aggregation → check raw response.
Step 2: Copy the raw response into a JSON viewer
Check the structure & paths.
Step 3: Validate parsing path & pagination
Some APIs return:
JSON{ “status”: “success”, “data”: []}
This looks “successful,” so IdentityNow doesn’t fail — but no accounts appear.
Hi @Nishx100 ,
You have to mention the Root Path as $.data[*].data
the JSON payload inside a list so you should mention it with []
In the response mapping you can directly mention the email, status etc. attributes
yes after changing the root path all accounts have been succesfully aggregated
Hi @Nishx100
The issue is due to the structure of the API response. The JSON payload is inside a list, so the Root Path should be defined as $.data[*].data to correctly parse the array elements. Since the response contains a list, the [*] notation is required to iterate through each object.
After setting the correct Root Path, you can directly map attributes such as email, status, and other required fields in the response mapping section.
