Form shows success but no lead arrives
Visitors fill in the form and see the success message, but nothing lands in your inbox, CRM, or sheet. You usually discover it by accident — days or weeks of leads are simply gone.
- Webflow
- Bubble
- Any stack
- Forms & leads
- Email delivery
Root cause, in plain English
The success message only confirms the browser-side submit. Behind it, delivery is a chain — form tool, notification email, automation step, CRM — and any link can break silently: the notification address bounces or filters to spam, a Zapier/Make scenario is paused or out of quota, a webhook URL went stale after a domain change, or a required-field mapping fails. The visitor keeps seeing "Thanks!" because the first link still works.
How to fix it
Submit a test lead yourself, right now, and follow it through each hop. The break is wherever it stops appearing.
Check the form tool's own submissions list first (Webflow's Forms panel, Bubble's database): if your test is there, capture works and the failure is downstream — and the missing leads are recoverable.
Check notification email: is the address current, is the mail in spam, did the form provider's sender get blocked? Send-to-self services break quietly when mail authentication changes.
Open the automation's run history (Zapier/Make/n8n): paused scenarios, exhausted task quotas, and errored runs are all visible there — and most tools can replay failed runs once fixed.
Re-check field mappings after any form edit; adding or renaming a field can silently break the integration that fed your CRM.
Export the form tool's stored submissions for the gap period and import them — the leads usually weren't lost, just undelivered.
Go deeper: read the full guide · copy the open-source health-check recipe.
How Nightlamp detects this automatically
- Browser journey
- Email flow
- API canary
A browser_journey fills and submits the real form on a schedule with a tagged synthetic lead, and an email_flow check asserts the notification actually arrives in a monitored mailbox — together they test the full chain, not just the button. An api_canary can verify the downstream endpoint (CRM webhook, sheet API) is still accepting writes.
Catch this before your customers do
Nightlamp runs these checks continuously against your live app and sends a plain-English diagnosis — not a wall of logs — the moment this pattern shows up.
Related patterns
Frequently asked questions
- Are the missing leads gone forever?
- Usually not. Most form tools store every submission independently of delivery — check Webflow's Forms panel or your Bubble database for the gap period and export them. What's lost is response time, which is why detection speed matters for this failure.
- What's the most common silent break in the chain?
- Automation quota and pause states: a Zapier plan running out of tasks mid-month, or a scenario auto-paused after repeated errors. Second place is the notification email quietly going to spam after a DNS or sender change.
- How do I monitor a form without polluting my CRM with fake leads?
- Use a reserved marker — a dedicated test email address or a hidden field value — and filter it at the CRM or automation layer. The synthetic lead exercises every hop and gets discarded at the last one.
Newsletter
Get new incident patterns as we publish them
One email when new failure patterns, fixes, and monitoring recipes for no-code and AI-built apps land. No fluff, unsubscribe any time.
Double opt-in. One-click unsubscribe. No spam, ever.