Skip to content
Tutorials Center
My learning

Topics

Lesson 23 of 37 ยท Forms, Ecommerce and Apps

Forms, Submissions and Notifications

Learn how to build contact and lead forms in Wix and Webflow, where submissions are stored, how notifications work, and how to design fields visitors finish.

Almost every business site needs a form: a contact request, a quote, a newsletter signup, a booking. Wix and Webflow both include form builders, store the submissions for you, and can email you when one arrives. The craft is in designing a form people actually finish, and in knowing where the data goes afterwards.

Wix and Webflow are hosted products and cannot run here. Steps are described in words (menu names may change), and the runnable samples are JavaScript stand-ins that model forms and submissions without sending anything to a real server.

Building a form in Webflow

In the Designer, open the Add panel and drag a Form Block onto the page. It contains a Form Wrapper holding the fields, plus Success and Error messages (hidden by default, shown after submit). You can add Text Fields, Text Areas, Select Fields, Checkboxes, Radio Buttons and a Submit Button.

Important settings in the element settings panel:

  • Name: each field needs a name; this becomes the label in the stored submission.
  • Type: text, email, phone, number, password. Choosing email gives you the browser's built-in format check.
  • Required: marks the field mandatory.
  • Form settings: name of the form, the action, method, and the redirect URL after success (an optional "thank you" page).

Submissions are collected on Webflow's servers and appear in Site settings, Forms (the Forms tab). You can configure email notifications to one or more recipients, and connect integrations such as Zapier or a webhook (see Integrations, Webhooks and Automation). Form submission limits depend on your site plan, so check the current plan details before relying on a free or entry plan for a busy site.

Building a form in Wix

In the Wix Editor, use Add Elements, Contact and Forms (the label depends on the editor version). The Wix Forms app gives you templates (contact, booking request, quote) and a form editor where you add fields, set labels and placeholders, and choose what happens after submit: show a thank-you message, go to a page, or send a notification.

Submissions are stored in the site dashboard under Inbox or in the Forms app's submissions list, depending on your setup. You can set notification emails and automations (for example, send the visitor an automatic confirmation or add the contact to your CRM contact list). Wix also treats submitters as contacts, so repeat enquiries are grouped with the same person.

Designing a form people finish

Each extra field lowers completion. A short list of principles:

  1. Ask only what you need now. A first contact form usually needs name, email and message.
  2. Label every field above the input. Placeholders vanish when typing begins and fail accessibility checks when used alone.
  3. Use the right type. email and tel bring the correct mobile keyboard.
  4. Mark required fields clearly (and use the platform's required setting, not just an asterisk).
  5. Explain errors specifically. "Enter an email like [email protected]" beats "Invalid input."
  6. Give a clear success message that says what happens next and when.
  7. Make the submit button say the action: "Send message" or "Request a quote", not "Submit".

What a submission looks like

A submission is a record of field names and values plus metadata such as the time and the page. The stand-in below models a form definition and the record that results, so you can see how names and required flags shape the stored data.

JS Stand-in: form definition to submission record

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notifications that people read

A notification email should tell you who wrote, what they said and how to reply, without opening the dashboard. Both platforms allow you to choose recipients and, to a degree, the subject line and sender name. Practical tips:

  • Send notifications to a shared inbox (such as sales@yourdomain), not one person's address, so leave and holidays do not drop leads.
  • Set a reply-to address if available, so pressing Reply writes to the visitor.
  • Add an auto-reply to the visitor with the expected response time.
  • Check your spam folder when you test; notifications sent from a platform address sometimes land there until your domain's email authentication is set up (see Domains, DNS and SSL).

Here is a stand-in that composes a notification, so you can see which fields make it useful.

JS Stand-in: compose a notification email

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Privacy basics

A form collects personal data, so tell people what you do with it. Link to a privacy policy near the submit button, add a consent checkbox when you plan to send marketing email (and keep it unchecked by default), and delete old submissions you no longer need. Rules differ by region (GDPR in the EU and UK, CAN-SPAM in the United States, and others), so check the requirements that apply to your audience rather than relying on defaults.

Common mistakes

  • No success message, so people submit twice.
  • Using one catch-all notification inbox nobody monitors.
  • Required phone numbers on a simple contact form.
  • Forgetting to test on mobile.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why use the email field type?

    The email type enables the browser's basic format check and shows an email-friendly keyboard on phones.
  2. 2. Where does a Webflow form submission go by default?

    Webflow stores submissions on its servers and lists them in the Forms area of the site settings.
  3. 3. Which is a better button label?

    A label that names the action tells visitors what will happen.
  4. 4. Why set a reply-to address on notifications?

    Reply-to makes the visitor's address the target of your reply.

Summary

  • Both platforms store submissions and can email you; check plan limits before relying on them.
  • Fewer fields, clear labels, correct types and a clear success message raise completion.
  • Notifications work best going to a shared inbox with a reply-to set.
  • Mention privacy and consent wherever you collect personal data.

Next: Form Validation and Spam Protection