Home Glossary Zoho Forms Webhook (Forms)
Zoho Forms

Webhook (Forms)

A Webhook in Zoho Forms sends response data to an external URL via HTTP POST at the moment of submission, enabling real-time integration with

Technical Term

A Webhook from Zoho Forms gives any external system immediate awareness of a new submission without polling. Unlike the built-in Zoho integrations, a Webhook delivers raw JSON to any endpoint, meaning it works with any platform that can receive an HTTP POST, not just the Zoho ecosystem.

How Webhook Works in Zoho Forms

A Webhook in Zoho Forms is configured in the Integrations section of the form settings. You specify a target URL (the receiving endpoint), choose the HTTP method (typically POST), and optionally customise the payload format. When a form is submitted, Zoho Forms sends an HTTP request to that URL containing the form response data as a JSON or form-encoded payload. The receiving server must return a 2xx HTTP status code to acknowledge receipt; failed deliveries are logged for review.

When to Use Webhook

Use a Webhook when you need to send form submission data to a system that is not listed in Zoho Forms’ native integration catalogue, such as a custom-built internal application, a Zapier or Make (Integromat) automation, or a third-party CRM. Webhooks are also appropriate when you need the submission data to trigger processing in real time rather than waiting for a scheduled sync. If your target system is already natively supported, use the dedicated integration instead, as it is more resilient and requires no custom endpoint development.

Key Considerations for Webhook

The receiving endpoint must be publicly accessible on the internet; Webhooks cannot reach localhost or private network addresses. Zoho Forms sends the Webhook synchronously at submission time, but does not guarantee delivery: if the endpoint is down, the response is still recorded in Zoho Forms, but the Webhook may not be retried automatically depending on configuration. Always log incoming Webhook payloads on the receiving side. For sensitive data, configure HTTPS on the receiving endpoint and consider adding a shared secret or token for authentication.

India Example: A Pune e-commerce distributor uses a Zoho Form for dealer stock requests. A Webhook sends each submission to their in-house Node.js inventory system in real time, which checks stock availability and creates a warehouse pick task automatically. The integration replaced a two-hour manual process with an instant one.
Does Zoho Forms retry a Webhook if the receiving server is temporarily unavailable?

Zoho Forms logs Webhook delivery attempts and their HTTP response codes. Retry behaviour depends on the specific plan and configuration: some configurations do support automatic retries on failure, while others log the failure without retrying. It is best practice to build idempotency into your receiving endpoint so that duplicate deliveries, whether from retries or testing, do not create duplicate records in your system.

Can you send Webhook data only for approved responses rather than all submissions?

Yes. Zoho Forms allows you to configure the Webhook trigger condition, so you can set it to fire only when a response reaches a specific approval status such as Approved, rather than on every initial submission. This prevents your downstream system from receiving data that is later rejected and reduces the need for your receiving application to handle conditional filtering.

Need help implementing this in Zoho?

Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.