Hi @daniel_yi,
maybe a small example for your store locator 
Go to your target page and open the network monitor (“Netzwerkmonitor” in German )
Do your search and try to find the relevant get/post request (most one of the first)
There we see that the
will be requested (which includes our input location
It is a get request so we only have to check the target URL as well as if the headers include information we have to provide:
Header cookie includes some information which might be relevant e.g. userLocation, refererer and host
Check what is set in the initial page request:
see that maybe userLocation should be added and try if that is enough
Now create these information in a requestUrl and request cookie:
And it seems in your case that is enough:
Response from KNIME:
Response if doing it manually in firefox:
Now you just have to parse the jsons
*and maybe if you like to test what the Sprint site allows check how far you can “enhance” the distance modifier
9 returned objects
98 returned objects
Example Workflow:
store locator.knwf (15.7 KB)
Next step would be to have a list of ZIP Codes to check and mostly reducing the number of request you have to send in the given area range
And maybe set a good timeout between requests as to not get blocked by their page 