← Back to the app

Web form to CRM

A form is submitted on your site, and it should reach your CRM as a lead.

The purpose

"Every form submission reaches my CRM." A simple-sounding promise that quietly breaks more often than it should. A form tool's native integration silently stops working, or a Zap gets turned off after an unrelated account change, and submissions keep coming in with nobody landing anywhere.

Where the two pings go

  • Start: the moment the form is actually submitted (a webhook from the form tool itself, which Typeform, Jotform, and similar all support, or the first step of whatever automation receives it).
  • Finish: the moment the lead record is created in the CRM.

Use the form submission's own ID as the reference if it has one, or the submitter's email address if it doesn't.

What healthy looks like

A submission comes in, a matching lead appears in the CRM within moments. High delivery rate, nothing confirmed, no completeness flags.

What a failure looks like

A submission comes in and nothing lands in the CRM within the expected window. The classic "the form tool's Zap got disconnected three weeks ago and nobody noticed" scenario. FlowProofs confirms the gap and alerts, so this gets caught in minutes instead of at the next client call.

Common variant

If a required field (phone, or a specific qualifying answer) sometimes arrives empty even though the submission itself succeeded, that's a completeness flag, not a gap. See gaps vs. completeness.