Why isn't my Lovable contact form working?
Last checked 31 Aug 2026
Short answer
Check, in order: whether a submit handler is actually wired up, whether a backend (Lovable Cloud/Supabase) is connected if you're saving data, whether client-side validation is blocking submission, and the browser console for errors.
Work through it methodically
"Not working" covers several different failures. Narrow it down before prompting a fix.
- Does the button do anything at all? Open the browser console (right-click → Inspect → Console) and submit the form. JavaScript errors here point to a broken handler.
- Is validation silently blocking it? Required fields or a regex check can prevent submission without a visible message. Check that error text actually renders.
- Is there a backend to write to? If the form is meant to save data, confirm Lovable Cloud or Supabase is actually connected — a form calling a table that doesn't exist will fail.
- Is email involved? If the form should send a notification, the failure might be in the email step, not the form — see why aren't form emails being delivered.
Ask Lovable to debug it directly
The contact form doesn't submit — clicking "Send" does nothing and there's an error in the console: [paste the exact error]. Fix it.
Pasting the exact console error rather than describing it in vague terms gets a far more accurate fix.
Check row-level security
If data should insert but doesn't, and there's no console error, RLS is a common culprit: a table with no insert policy for anonymous users will reject the write quietly on the backend side, and it typically shows up as a 401/403 in the Network tab.
The enquiries table isn't accepting new rows from the contact form. Check the row-level security policy and allow public inserts.
What usually goes wrong
- Testing in Preview only: some behaviour (like real email sending or RLS) can differ once published — verify on the live URL too.
- Multiple forms with the same name conflicting: if you've asked for several forms, check the right one was edited.
- Silent validation failures: a required field with no visible asterisk or error message looks broken but is working as designed.
If the form still fails after a couple of fix attempts, check /troubleshooting for general debugging steps, or describe the exact symptom plus console error to Lovable rather than re-prompting the whole feature from scratch.
Sources
Was this answer helpful?
Related questions
- AnswerWhere do Lovable form submissions go?Nowhere, by default — a form only exists on the front end until you connect a destination: a database table (Lovable Cloud/Supabase) and/or an outgoing email via an integration like Resend.
- AnswerHow do I email form submissions to myself?Connect an email integration (Resend is the standard option), then ask Lovable to trigger a server-side function that emails you the form data whenever it's submitted.
- AnswerHow do I save form submissions to a database?Connect Lovable Cloud (or your own Supabase project), then ask Lovable to create a table for submissions and wire the form's submit handler to insert a row into it, with row-level security limiting who can read the data.
- AnswerHow do I connect Resend to Lovable?Open the Resend integration in Lovable (or ask in chat to connect Resend), authorise your Resend account, then prompt Lovable to use it for whatever emails you need sent.