Why Your Typeform Submissions Are Not Coming Through

“`html

Check Your Notification Settings First

Typeform submissions not coming through? Honestly, it usually has nothing to do with the form itself — I learned this the hard way. Spent two hours debugging a client’s “broken” form only to discover they were checking the wrong email inbox.

Here’s what gets people: Typeform sends data in two completely different ways. Email notifications and actual form submissions are separate systems. You can receive an email notification about a response without that response ever reaching your CRM, your webhook, or your database. Conversely, your form could be submitting data perfectly while the notification email sits undelivered in spam. These aren’t connected the way most people think they are.

So, without further ado, let’s dive in.

Open your Typeform workspace and navigate to the form in question. Click the Settings gear icon, then scroll to Notifications. You’ll see two tabs: Email notifications and Webhooks. The email tab controls who gets alerted about responses — it’s cosmetic. It doesn’t affect whether your form data actually goes anywhere.

If you’ve configured a webhook, email notifications, or integration, they live in their own sections. Check that the correct email address is listed and that it’s not set to “off.” I’ve seen forms disabled accidentally when someone toggled the notification switch while troubleshooting something unrelated — the form was fine, but nobody knew about incoming submissions.

Next, use Typeform’s built-in test feature. It’s right there at the bottom of the form settings. Click Send test submission. Fill out the form as a user would. If you receive a test notification email within 30 seconds, your email notifications are working. If you don’t, your data isn’t leaving Typeform at all.

This test submission tells you whether the problem is upstream — the form isn’t capturing data — or downstream — the form captures it but integrations aren’t working. Most small business owners skip this step. Don’t make my mistake.

Fix Webhook and Integration Failures

Probably should have opened with this section, honestly. Webhook failures cause roughly 40 percent of submission problems in teams I’ve worked with.

What is a webhook? In essence, it’s how Typeform sends your data to another system — Zapier, Make (formerly Integromat), a CMS, a custom API endpoint, or a spreadsheet. When a user submits your form, Typeform sends an HTTP request to your webhook URL with all the response data. If that request fails, your data vanishes. But it’s much more than just a simple data transfer — the entire integration chain depends on it.

Confronted by a silent form failure, check Typeform’s webhook logs immediately. Go to Settings → Integrations → Webhooks (or Settings → Notifications → Webhooks depending on your account age). You’ll see a list of configured webhooks with delivery status right there.

Click the webhook URL to expand it. You’re looking for a delivery history — Typeform logs the last 1,000 webhook attempts. Each entry shows:

• Timestamp
• Response status (200 = success, 400/500 = failure)
• Error message or response body

If you see all red, your webhook endpoint is rejecting requests. Common reasons include:

• IP whitelisting — Your server is blocking Typeform’s IP addresses. Typeform publishes its IP range — if your firewall is configured strictly, you need to whitelist 35.190.0.0/16 and 34.125.0.0/16
• Timeout — Your endpoint takes longer than 30 seconds to respond. Typeform gives you 30 seconds max. Anything slower fails silently
• Authentication missing — You configured the webhook without API keys or tokens, and your endpoint requires them
• Webhook URL is dead — The domain doesn’t resolve, the path is wrong, or the server is offline

Test your webhook directly. Copy the URL from Typeform settings. Paste it into a REST client like Postman or Insomnia — both are free. Typeform sends POST requests with a JSON payload. Grab a sample from the webhook logs and paste it as the request body. Hit send. If your endpoint returns 200, the problem isn’t the URL itself — it’s something about Typeform’s request format or your endpoint’s timeout threshold.

Using Zapier or Make? The diagnosis is different. These services sit between Typeform and your destination system. A Zapier integration can break if your Zapier account loses connection to Typeform, or the destination app (like Mailchimp or Airtable) disconnects and Zapier can’t re-authenticate. Server overloads happen too, though rarely.

Log into Zapier and check your zap’s status. Go to your Typeform zap, click Activity, and look at recent runs. Failed runs are red — click them to see why. Typical failures: “Unable to write to this spreadsheet—permission denied,” or “Mailchimp API key is invalid.”

Resolve Third-Party App Connection Issues

Your Typeform is connected to Mailchimp, HubSpot, Airtable, or some other service. Submissions used to work. Now they’re not coming through. The form still submits — you see responses in Typeform’s response tab — but your CRM or email platform receives nothing. That’s what makes this problem endearing to many people, actually — everything looks fine on the surface.

The culprit is usually API token expiration or revocation.

When you first connected Mailchimp to Typeform six months ago, you authorized Typeform to access your Mailchimp account. You did this by clicking “Connect” and logging in with your Mailchimp credentials. Typeform received an API key that expires after a certain period — typically 90 to 180 days, depending on the service. That’s the window we’re talking about here.

Once that token expires, Typeform can’t write new contacts to Mailchimp. Submissions keep arriving in Typeform, but Mailchimp never hears about them. Nothing breaks audibly — no error messages, no warnings in your inbox. The data just disappears into the void.

I’m apparently someone who’s seen this happen dozens of times. Business owners add a new team member to their Mailchimp account and, without realizing it, revoke the API key. Or their hosting company rotates credentials. Either way, Typeform’s stored token is suddenly invalid.

Here’s the fix.

Go to Settings → Integrations and find the problematic app. For Mailchimp, HubSpot, Airtable, or any other native integration, click the connected app. You’ll see a Reconnect or Re-authorize button. Click it. This prompts you to log in again and grants Typeform a fresh API token. Submissions should resume immediately — we’re talking within seconds if everything’s working.

For Zapier or Make, the process is similar but happens inside those platforms. Log into Zapier, navigate to your zap, and click the Typeform trigger. Typeform should already be authorized — it was when you created the zap. But check the destination app. If you see a yellow warning icon, the connection is stale. Click it and re-authenticate.

Some integrations require you to manually rotate API keys. If you use a custom webhook and you control the endpoint, check whether your API keys have a rotation schedule. Some security practices rotate keys every 90 days. When yours rotated, did you update Typeform’s webhook configuration? Probably not, which is why submissions stopped.

Log into Typeform settings, find the webhook, and update the API key in the URL or headers. Test with a submission. If Typeform’s logs now show 200 responses, you’ve fixed it.

Browser and Cache Problems That Block Submissions

CORS errors and JavaScript conflicts rarely affect form *display*, but they absolutely block *submission*. A user sees your form, fills it out, clicks submit — and nothing happens. No error message. The form just hangs there.

This is almost always a browser issue, not a Typeform issue.

CORS stands for Cross-Origin Resource Sharing. In essence, it’s a security mechanism that restricts how browsers load resources across different domains. But it’s much more than that — it’s actually blocking your form submissions. Your form is embedded on domain A, but Typeform’s servers are on domain B. Modern browsers restrict cross-domain requests for security. If Typeform’s embed code isn’t configured with proper CORS headers, the browser silently blocks the submission.

Test this in incognito mode. Open your form in a private/incognito window. Try submitting. If it works in incognito but fails in normal mode, the problem is browser cache or a browser extension — at least if you want to narrow this down methodically.

Clear your browser cache entirely. In Chrome: Settings → Privacy → Clear browsing data. Select “All time” and “Cookies and other site data.” Refresh your form and try again.

Browser extensions are sneaky culprits. Ad blockers, password managers, and security tools sometimes interfere with form submissions. Disable extensions one by one and test. I’m apparently someone who’s spent hours debugging forms only to find that uBlock Origin was stripping out Typeform’s tracking pixel, which broke the submission flow.

If you’re embedding the form using an iframe or custom code, check the embed settings in Typeform. The form must be embedded with the correct domain whitelist. Go to Settings → Share, select your embed method, and verify the domain is listed.

When to Contact Typeform Support and What to Share

You’ve checked notifications, tested webhooks, re-authorized third-party apps, and cleared your cache. Submissions are still failing. Time to contact Typeform.

Have this information ready before you reach out:

• Form ID — Found in the URL: typeform.com/to/[FORM_ID]
• Submission timestamp — The exact date and time you tried submitting (or ask a user for theirs)
• Expected destination — Where the data should go (Zapier, webhook, email, CRM)
• Webhook logs — Screenshots of failed deliveries with error codes
• Steps to reproduce — The exact steps you took: open form, fill field X, click submit, nothing happens

Typeform support’s response time is typically 24–48 hours for standard accounts, faster for paid plans. They’ll investigate your webhook logs, check for server-side issues, and sometimes discover problems you can’t see from your browser.

One more thing: if you’re a paying customer, you get priority support. Basic plans are community-driven. Know which tier you’re on before submitting a ticket.

“`