Skip to main content

I’ve set up a zap -- “Create module entry in Zoho CRM when catch raw hook in Webhooks by Zapier” where I’m connecting “Webhooks by Zapier” to the Zoho CRM. Within minutes I was able to create a zapier URL that accepts a POST request which will add a new module in Zoho. This is fantastic!

It’s also terrifying because anyone with the webhook URL can send requests to it, which could lead to unauthorized access or abuse. Surely there’s a basic auth or token system available to mitigate this threat, but I can’t seem to find it anywhere in the UI.

I’m brand new to zapier -- what am I missing?

Hi @teeky301 

Good question.

Help articles about Zapier Webhooks: https://zapier.com/apps/webhook/help

 


If Zapier is claiming compliance then there must be an alternative to this “security through obscurity” approach. Maybe I can add my own ‘path’ trigger in the zap that handshakes with my own basic auth and includes a conditional to proceed to the next trigger?

Are there any offerings in the pro version to address this security hole?


@teeky301 

Best to open a ticket with Zapier Support for further clarification and guidance: https://zapier.com/app/get-help


For the edification of future readers:

It looks like an “integration” can be set up in zapier platform which includes a number of authentication methods. This integration can be used as the ‘trigger’ in a zap instead of a webhook.