I’ve never really struggled with Webhooks in the past but this is my first go at it with WeWeb. Typically I’d send to a Webhook from the backend for this but I have my reasons for trying to avoid it in this specific use case.
keep in mind that when a server doesn’t handle CORS and gives you a network error in the browser it’s a good sign that the endpoint was not meant to be called from the browser and it’s assuming you make your requests from a secure server that you control. It’s better to check that you are not using secret data that is not meant to be shared in a browser environment.
Zapier triggers are largely fire-and-forget. The REST plugin thinks you care about the response, but I bet you really don’t. You can get it to send (without erroring out) through a custom javascript action, which is how I would do it.
The behavior should be that Zapier receives the webhook, sends a response without CORS headers, and Weweb won’t use it - throwing an error. If that’s the case, you can ignore the error since Zapier webhooks are fire-and-forget anyway.