Why not call Typeform's API directly from your own endpoint? You can — but then you own Typeform'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
Typeform — New Response
A real Typeform event, shown as ZestyGlue formats it for Custom Webhook.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Typeform → Custom Webhook connector. You'll get a unique webhook URL right away.
- Point Typeform at it. Go to Connect → Webhooks → add a webhook, and paste in your ZestyGlue webhook URL.
- (Optional) set a secret. Typeform can sign its payloads if you set a secret on the webhook — enter the same value into ZestyGlue for extra verification, though it isn't required to get started.
- 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: Typeform's signature is optional — if you skip setting a secret, ZestyGlue still accepts the webhook (relying on the URL staying private), so you can get started even on plans that don't expose the signing secret setting.
Events you can forward
form_response
Questions
Is my Typeform Webhook Secret safe with ZestyGlue?
It's encrypted at rest with Fernet symmetric encryption before it ever touches disk, it's never logged, and it's never displayed again in the dashboard after you enter it — only a masked placeholder is shown.
Are all question types supported in the preview?
The most common ones — text, email, number, and single choice — are shown directly. More complex types like file uploads still trigger the notification, just without every detail spelled out.
Can I connect more than one Typeform form to the same channel?
Yes, create a separate ZestyGlue connector (and webhook URL) per form, and point them all at the same channel if you want a combined feed.
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 Typeform's side — Typeform 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.