Form submitted, but the lead is missing from your CRM
Reviewed · White Dot
A form can show success without creating a new CRM contact. Start with the saved submission, check the tool that sends it to your CRM, then look for the contact and its owner. An existing contact may have been updated instead.
You'll need access to the form history and CRM. The examples below use Zapier and HubSpot; check your own tool's rules if you use something else.
Where did the lead stop?
| Observation | What this tells you | What to check next |
|---|---|---|
| You see a success message, but no stored submission. | The page showed success. You still need to find the saved entry. | Confirm the correct form, site, date range and time zone in its submission history. Ask the form maintainer for a redacted storage result if it is custom. |
| The submission is stored; no matching integration run appears. | The form saved the entry. You haven't found a run that sent it to the CRM. | Check the selected form/account, trigger, enabled state, filters and documented polling interval. In Zapier, existing data from before activation does not normally trigger a new run. |
| A run exists, but the CRM step failed, was skipped or received empty fields. | The run started, but the CRM step needs checking. | Read the step's input, output and error. Compare required destination fields and mapped values. Record the failing field without changing or replaying the run. |
| The CRM step returned a record ID, but your lead list is empty. | You have a record ID. Check which record it belongs to and who can see it. | Use that ID in the correct CRM account and object. Inspect an existing contact's update time, record history and view filters. A contact, deal and lead can be different record types. |
| The record exists, but nobody sees it in their assigned list. | The record exists. Check its owner and who can see it. | Read the owner field and assignment history with an authorized administrator. Compare team views and permissions. Do not reassign a customer while diagnosing. |
Check Zapier and HubSpot before changing fields
In Zapier, open the run and inspect the CRM step's Data In and Data Out. Check whether the form sent an empty field or the CRM rejected a filled one. Then read the error for that step.
In HubSpot, repeat submissions with the same email can update an existing contact. Browser tracking cookies can also affect which contact gets updated. Check the form's contact-creation settings and that contact's history before expecting a second record.
For example, if the CRM step returns a contact ID and that contact has no owner, check assignment before resubmitting the form.
Test with a sample lead
- Write down where the lead should go: form → connector → CRM record → owner. Save the current settings and decide what you need to see at each step.
- Use a sandbox or a separate test form and CRM that you have permission to use. Check every action it can start, including emails, SMS, tasks and sales sequences. Make sure the test cannot send anything to a customer before you submit.
- Use sample values such as
DEMO-CRM-001anddemo-crm-001@example.invalid. That address cannot receive email. If your tool rejects it, use a test address you control and have permission to use. Never use a customer's address. - Submit once. Keep its timestamp and time zone. Match the saved submission to a run, the run's CRM output to a record, and that record to the expected owner. Note any step you can't confirm.
- If duplicate handling needs testing, use a second marker,
DEMO-CRM-002, with the same isolated test identity. First confirm no customer messages can fire. Compare the returned record IDs and update history rather than assuming two submissions mean two contacts. - Stop at the first step you can't explain. Keep the test records according to your business's policy. Don't delete real records or replay live runs to make the test pass.
If you need more help
If the test could message a customer, you can't read the history or the result is unclear, stop and ask the administrator for help. Have someone check saved inquiries while you investigate, so people can still get a reply.
Keep the form name, submission time and time zone, run ID, failed step, error and CRM record ID. Note the fields involved and who should own the contact. Remove customer details, passwords and private links before sharing.
Saved Wix submissions with missing email alerts involve a different path. See Wix form notification email checks.
Official help links
- Zapier: Zap isn't triggering: trigger/account checks and new-data behavior.
- Zapier: Zap is not sending data: mapped fields and step input/output.
- HubSpot: Troubleshoot forms: submission counts and existing contacts.
- HubSpot: Create and customize forms: contact association and form settings.
We're not affiliated with Wix, Zapier or HubSpot.