Webhook response handling

Hi @Troy Tessalone,

thanks for your reply, so for example I posted an invoice in xero with an invalid email address, xero returned a validation error which is showed under that specific run in the zaps history. This step is triggered by a zapier webhook which is called from my code through an http client (I’m using c# but the language should be irrelevant). Now when I catch the response in my code I’m getting 200 and that criptyc content rather than the below validation error which would be useful to determine if the zap completed successfully or failed.

In this case it failed but the only way to know this is via the notification emails or looking in the zaps history.

I think I’ve been misunderstood. The invalid email was sent on purpose to see the response I get back when the zap fails. I’m triggering the zap from this code which basically posts the json payload to a zapier webhook. I understand zapier webhooks will always return 200 regardless so I’m asking what is the meaning of the reponse below and if it can be used to determine the real zap result. Maybe querying a zapier endpoint with request id?

using (var httpClient = new HttpClient())
{
                    string jsonData = JsonConvert.SerializeObject(invoices);
                    StringContent httpContent = new StringContent(jsonData, System.Text.Encoding.UTF8, "application/json");
                    HttpResponseMessage response = httpClient.PostAsync(trigger.Url, httpContent).Result;
                    if (response.IsSuccessStatusCode)
                    {
                        // NOTE:  Zapier always return 200 and this reponse instead of the email validation error
                        {"attempt":"01875616-eb6d-9e7b-ff2c-29181e97cb38","id":"01875616-eb6d-9e7b-ff2c-                 29181e97cb38","request_id":"01875616-eb6d-9e7b-ff2c-29181e97cb38","status":"success"}
                    }
                }

Ok I understand, it was worth asking anyway.

I think it would be extremely useful to be able to retrieve the real zap run result (and possibly the reason) from the webhook response. Getting always a success even when it’s not feels a bit illogical.

Thanks for the support.

@gusmaster 

The Webhook being received was a success which is why you get the 200 response from the Zap Run trigger step.

How the other steps in the Zap Run play out is different.

You can see those in your Zap Run history: https://zapier.com/app/history/

For example the Zap Run could be designed to take minutes to days to complete running, so it’s unrealistic to expect to be able to keep the connection open for that long to return a response of the full Zap Run outcome.