Troubleshooting
Email not received
Section titled “Email not received”Formkove sends notification emails instantly. If you don’t see one:
- Wait a bit: delivery can take up to 2 minutes in rare cases
- Check Spam/Junk: drag to Primary if it’s there
- Check Promotions: Gmail sometimes filters it there
- Verify your MX records: your domain needs proper mail DNS for delivery to work
If emails keep bouncing, contact support with your form ID. You may be on a suppression list.
Email received but no data
Section titled “Email received but no data”Make sure every form field has a name attribute:
<!-- ✗ Missing name — data won't send --><input type="text" placeholder="Email">
<!-- ✓ Has name — data will send --><input type="text" name="email" placeholder="Email">CORS errors in JavaScript
Section titled “CORS errors in JavaScript”If you see a CORS error in the browser console when submitting via fetch:
The cause: You’re mixing content types. Using x-www-form-urlencoded with fetch triggers a redirect, which browsers block in CORS contexts.
The fix: Always use application/json when submitting via JavaScript:
// ✗ Wrong — triggers redirect, causes CORS errorfetch(url, { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, body: JSON.stringify(data)});
// ✓ Correct — returns JSON, no redirectfetch(url, { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify(data)});If you’re using the HTML form action attribute directly (not JavaScript), x-www-form-urlencoded is fine. The browser handles the redirect naturally.
Form works locally but not on my hosted domain
Section titled “Form works locally but not on my hosted domain”Formkove blocks certain high-risk free domains and subdomains by default to prevent spam abuse.
If your form works in localhost but fails when deployed:
- Add a custom domain to your site
- Contact Formkove support with your domain to request unblocking
Free subdomains from platforms like *.vercel.app, *.netlify.app, *.glitch.io etc. are blocked on the free plan. Deploy to a custom domain to resolve this.
405 Method Not Allowed
Section titled “405 Method Not Allowed”This is usually a content-type mismatch or an incorrect request method. The API only accepts POST requests. If you are submitting via JavaScript and get a 405, make sure you are not using GET and that you set Content-Type: application/json to prevent redirects.
429 Rate Limited
Section titled “429 Rate Limited”Too many submissions from the same IP in a short period triggers temporary rate limiting.
Wait an hour and try again. This resets automatically. If you’re testing, add delays between submissions.
“Invalid form ID” error
Section titled ““Invalid form ID” error”- Check that you’re using the correct Form ID from your Formkove dashboard
- Make sure there are no typos in the URL
- The Form ID goes in the URL path, not as a hidden field (when using the direct URL method)
Notifications not sending to Slack/Zapier
Section titled “Notifications not sending to Slack/Zapier”- Verify the webhook URL is correct and uses
https:// - Make sure the integration is enabled in your form settings
- Check that the receiving service (Slack, Zapier, etc.) hasn’t hit its own limits
- Test with webhook.site to confirm Formkove is sending the payload
Still stuck? Check the FAQ for more common questions.
