Status 200 is Success
If Request succeeds, we'll update the Work Order
Lets also Update Record if the request is not status 200
We'll need to add a Failed status to our Reverse Geocode Status field
If the request fails, we'll be able to trigger other steps
Lets make a Pipeline Logs table, so we can monitor and trigger workflows based on these logs
For now lets store the Web Request Status and Content
We want to create a Pipeline Log step
Here, we can convert the content to json object and target a specific area of the object
The data we want is under the "results"
Now, a quick test to see if it's narrowing results and converting to json object
At this point, I found out Google Maps API doesn't allow you to store data...
So I went searching for alternatives
I found this URL in the API docs
We will put our Latitude and Longitude variables in the URL in the correct spot and add our API key
I made a quick test to see the response...
We need to check if 'results' is still relevant and it is... keep it
Lets test it in Quick Base....
The content was converted to a json object, now we can make magic happen!
Now we can add the Reverse Geocode Address fields to the Update Record step
The data we want is stored in "address_components"
Inside "address_components", we can select "city", "zip", etc.
Here is how I mapped the Geocodio response
Lets run it and see what we get
Same as before, I got the URL from their API documentation. Add Latitude, Longitude and API credentials
Within minutes, I had the API ready. Solid Support!
With SmartyStreets, we can get the full Street 1 address in one spot
Time to test...
Note: All API keys were harmed in the making of this video... Have fun!
Watch the YouTube video to see each and every step.
If this walk-through has helped you use Quick Base Pipelines for Reverse Geocoding, let us know in the comments section below!