Skip to main content

I have the same problem. I’m using zipcodeapi.com to retrieve city and state in a zap that’s collecting user information for our wireless portal. Works great until someone enters a bogus zip that the API can’t find then it kills the whole zap!

8.7.3

Hi there @tim829 - Are you still experiencing troubles with this? If so, we highly recommend you take this request to our Support team to address this further: http://zpr.io/t4NNK


@tim829 

Try adding a Filter step to the Zap to check if the expected value was returned from the API before having the Zap proceed, which should eliminate the errors.


Hey @tim829,

Just wanted to check in to see whether you were able to solve this using a Filter step as Troy suggested? 

Please let us know!