Duplicate form leads
A retried event can create another CRM record when the original ClickFunnels event_id is not preserved as the delivery identity.
ClickFunnels form CRM delivery
Prove every ClickFunnels form submission reached the sales system.
Protect ClickFunnels V2 form-submission webhooks with signature verification, stable event identity, duplicate-safe delivery, and a destination receipt.
Paid plan uses secure Stripe checkout · plan assigned after verified payment · activate with the checkout email- 25live deliveries
- 14 daysproduction access
- No cardto start
- Real APInot a demo
A successful automation run is not proof of delivery.
ClickFunnels can retry webhook events and deliver them out of order. If an adapter treats each attempt as a new lead, skips signature verification, or returns success before the CRM-bound handoff is complete, a valid funnel response can be duplicated or disappear after the page converts.
ClickFunnels V2 form_submission.created -> signature-verifying adapter -> LeadProof -> CRM or sales queueUnverified webhook input
Processing the body before checking ClickFunnels signature and timestamp headers allows unauthenticated requests into the lead workflow.
Premature success
Returning a successful webhook response before the destination outcome is recorded can hide the final CRM failure.
Implementation
Put LeadProof in the delivery path.
Keep the tools that create and process the lead. Standardize only the fragile handoff between them.
Platform reference: ClickFunnels: How to Work with Webhooks ↗Open sandbox instructions →- Configure a V2 ClickFunnels endpoint for form_submission.created and keep its webhook secret only in the receiving adapter.
- Verify the raw request with the ClickFunnels signature, timestamp, and freshness requirements before parsing approved form fields.
- Use the webhook event_id as the LeadProof Idempotency-Key and send only the contact fields required by the authorized destination.
- Return success after the adapter records the LeadProof receipt, then reconcile any final failures through the original ClickFunnels event and receipt IDs.
POST
https://leadproof.jessesay.chatgpt.site/api/v1/leadsAuthorization: Bearer lp_live_your_key
Idempotency-Key: stable-source-lead-id
Content-Type: application/json
{
"destination": "https://your-crm.example/webhook",
"name": "Alex Morgan",
"email": "alex@example.com",
"source": "clickfunnels"
}Questions
What teams ask before adding LeadProof.
Does LeadProof need the ClickFunnels webhook secret?
No. Keep the webhook secret in the signature-verifying adapter. LeadProof receives the normalized delivery request and public HTTPS destination, not the ClickFunnels secret.
Why use the ClickFunnels event_id for idempotency?
ClickFunnels can retry a webhook event. Reusing its durable event_id lets every attempt resolve to one LeadProof delivery identity instead of creating another CRM record.
Does a ClickFunnels webhook success prove the CRM stored the lead?
Not by itself. The adapter should return success only after it has recorded the LeadProof destination receipt or a durable asynchronous handoff it can reconcile.
See the gaps in your real workflow.
Get an explainable risk score, prioritized fixes, and the right LeadProof plan.