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!
Page 1 / 1
Hi there
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
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!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.