Why not call Jotform's API directly from your own endpoint? You can — but then you own Jotform's signature verification, retry handling, and payload quirks yourself. ZestyGlue verifies the signature, normalizes the event into a clean JSON body, and POSTs it to your URL — you only write the part that's actually yours.
What it looks like
ZestyGlue
Jotform — New Submission
A real Jotform event, shown as ZestyGlue formats it for Custom Webhook.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Jotform → Custom Webhook connector. You'll get a unique webhook URL right away.
- Point Jotform at it. Go to Settings → Integrations → Webhooks, and paste in your ZestyGlue webhook URL. That's the only setting — Jotform's webhooks have no secret to configure.
- Point it at your endpoint. Paste the URL of your own server, script, or automation tool's webhook receiver — no signup, no app to install.
Tip: Jotform doesn't sign its webhooks, but it does send your form's raw field data — ZestyGlue automatically strips Jotform's internal field-name prefixes (like q3_) so notifications read naturally.
Events you can forward
form submission
Questions
Does this work with conditional logic and multi-page forms?
Yes — Jotform sends the final submitted answers regardless of which conditional path a respondent took or how many pages were shown.
Why are some field names shortened, like 'name' instead of 'q3_name'?
Jotform prefixes every field with an internal question number. ZestyGlue strips that prefix automatically so notifications read like normal field names.
Do I need to write my own server to receive this?
Yes — this destination expects your own endpoint (or a tool like a serverless function, a script, or another automation platform's webhook trigger) to receive the POST. If you don't have one yet, pick one of ZestyGlue's built-in destinations instead.
What happens if my ZestyGlue subscription lapses?
Events are silently dropped rather than causing errors on Jotform's side — Jotform never sees a failure response, so it won't retry aggressively or flag your webhook as broken. Your dashboard will simply stop showing new events until you resubscribe.