I’m using a custom webhook request to make an API call to check if a user account exists in an external service. If a user does exist, a 200 is returned along with their information. Otherwise, the API returns a 404. The purpose of the Zap is precisely to create a new user account if one doesn’t already exist, but it’s always treating the 404 as a hard failure, aborts the run, and sets the Zap in an “errored” state.
I managed to work around the issue of the run aborting using a combination of Storage and Path tasks, but is there a way to tell the Zap that it didn’t fail just because this one API step returned a 404?
