Overview

Clipform uses the Standard Webhooks specification for webhook delivery, providing HMAC signing, replay protection, and automatic retries.

Webhooks are workspace-wide: an endpoint receives every form's completions, instead of being set up per form. Each payload carries form_id, form_name, and share_id so you can route or filter on your side.

A workspace can have several endpoints at once - the one you set in the dashboard, plus one per connected app. Each is registered separately and receives its own copy, so connecting a second Zapier Zap or Make scenario never replaces the first. Setting a new URL in the dashboard replaces only the previous dashboard one.

How it works

1. You register a webhook URL for your workspace (in the dashboard, or an installable app subscribes one for you)
2. When a respondent completes any form in the workspace, Clipform queues an event
3. Within 30 seconds, Clipform builds a structured payload and POSTs it to your URL
4. Your server verifies the signature, then routes/filters by form_id / form_name

Setting up a webhook

1. Open Webhooks in the dashboard - it's its own item under the Developers section (not under Integrations)
2. Enter your webhook URL - it saves automatically, and Clipform generates a signing secret
3. Click Test to send a sample payload and verify your endpoint works

Next steps

• Payload format - understand the data structure
• Signature verification - secure your endpoint
• Retry logic - how failed deliveries are handled