Mini lesson · English

How to get website feedback in your inbox

Publish a ready contact form, connect your notification inbox and trace one message all the way through.

Start the interactive lessonRead the lesson below

Who is this for?

People who want visitors to send website feedback to their inbox. A complete form is supplied and a coding assistant can make changes; HTML knowledge is not required.

Before you start

Your own Netlify practice account and an inbox you control. Download the supplied workshop and use only the starter folder for this separate test site. Hosted form processing starts after publication; a local preview does not send mail. Worked answers are illustrative examples, not completed tests on your account. Replace their sample observations with your own results, or identify the step that is still blocked.

Estimated time: 25–43 min

Estimates for the supplied starter files with prerequisite accounts and tools ready. Setup, deployment queues and delivery/DNS waits take additional time. Planning estimates with accounts ready. Account setup and email delivery can add time. Hosting service usage and charges depend on your account.

What you will learn

  • Publish the supplied form and configure an inbox.
  • Match one message in the provider and the actual email.
  • Add a useful field with an assistant and repeat delivery checks.

Workshop files

Step 1

Know what a complete result looks like

A thank-you page is only one part of the journey.

Open the supplied starter locally to see the form. For a real delivery check, use your own hosted practice project and notification inbox in the following steps.

Completion means finding the exact message in the host’s submission list and in the inbox. Keep those two observations separate.

A concrete example

Journey: visitor sends C1 → host stores C1 → owner receives its notification. If C1 exists in Forms but not the inbox, processing partly worked and notification delivery still needs attention.

Use the supplied starter contact form without rebuilding it. Guide me through publishing the contents of starter to my separate Netlify project, enabling form handling and configuring my own notification inbox. Preserve the existing form identity. Help me send a distinctive test and find it in Forms and the actual inbox. Ask before publishing or sending; do not claim delivery from the thank-you page.

MDN: sending form data

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

The result: website feedback in your inbox

Give visitors a way to share feedback and receive their messages by email. We will build a small contact form, then follow one test message from the browser to your inbox.

An HTML form collects values. A submission handler receives them. A notification service then sends an email to the site owner. These are separate parts of one journey.

We will use Netlify Forms as the handler for a small practice site. This lets us learn the journey before writing a custom email backend.

Download the workshop and read START-HERE.txt. The starter is a fictional portfolio. Local file previews show its layout; Netlify’s hosted form handler becomes available after you publish the practice site to your own account.

Worked example: what counts as delivery?

A visitor submits the message “Workshop test C1”. The provider lists that exact message, and the notification email contains the same text. Those two observations give you useful evidence.

A screenshot of a thank-you page only tells you that the page opened. Someone could open that URL without submitting anything.

MDN: sending form data

Extra implementation exercise

You see a thank-you page after sending “Workshop test C1”, but have not checked anything else. Which two places will you check before saying the form works?

  1. Name the two places and the exact text you will look for.
Show a worked solution

Find “Workshop test C1” in the provider’s submission list. Then find a notification containing the same message in the inbox configured for that form.

If the record exists but the email is absent, investigate notifications and delivery before changing the HTML.

  • Checks the provider submission list for the exact test message.
  • Checks the destination inbox for a matching notification; does not treat the thank-you page as proof.

Step 2

Prepare one recognizable test

Decide which message and return address you will use.

Choose a short synthetic message and an email address you control. Ask your assistant to preserve the supplied form and use that address as the visitor’s reply address, not as an arbitrary delivery destination.

The site owner’s notification destination belongs in the provider settings. The visitor should not choose who receives notifications.

A concrete example

Visitor address means “reply to this sender.” Owner inbox means “send this site’s notifications here.” Letting the visitor replace the owner destination would turn this into a different and unsafe mail-sending feature.

MDN: sending form data · Netlify: submission notifications

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Trace the message before editing code

The browser sends named fields to the handler. The handler records the submission and uses a configured notification recipient.

With method="POST", the browser places the submitted values in a request body. The name on each field becomes a key such as email or message. A visible label alone does not create that key.

The action is the submission destination. Netlify’s hosted form processor handles this static form and can redirect a successful submission to the thank-you path. On an ordinary local file server that processor is absent.

The inbox address belongs in the provider’s notification settings. Visitors supply their own reply address; they must not be able to choose arbitrary notification recipients.

Worked example: the data that travels

A visitor enters an email address and writes a message. The handler needs named fields to receive both values. In Netlify notifications, a field named email also supplies the reply-to address.

<label for="email">Your email</label>
<input id="email" name="email" type="email" required>
<label for="message">Your message</label>
<textarea id="message" name="message" required></textarea>

MDN: sending form data · Netlify: submission notifications

Extra implementation exercise

This input is visible and accepts an address, but the submitted request does not contain an email field. What is missing?

<label for="email">Your email</label>
<input id="email" type="email" required>
Show a worked solution

Add name="email". The id connects the input to its label; the name determines the submitted key.

<input id="email" name="email" type="email" required>
  • Adds the name attribute, not merely another label or id.
  • Explains that name="email" creates the email key in the submission.

Step 3

Open the supplied form

Inspect the visitor experience before publication.

Download the workshop, then ask your coding assistant to open starter/index.html. Try clicking the field labels, leaving the message empty and entering an invalid address. No code reading is needed.

The browser should help correct missing or invalid input. This preview tests layout and ordinary validation, not hosted processing or email delivery.

A concrete example

Try an empty required message, then an invalid email address. The browser’s correction is useful feedback. It cannot tell you whether a future valid submission will be stored or reach an inbox.

Netlify: form setup

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Open the starter and identify the moving parts

Use a separate practice project so the exercise does not disrupt an existing site.

Unzip the workshop. Inside starter/, index.html contains the form, style.css controls its appearance, and thanks/index.html is the page shown after a successful hosted submission.

Open starter/index.html in your editor and browser. Check that each label focuses its field and that a blank required field prevents normal browser submission. Do not expect an inbox message from this local preview.

The complete form source is shown below. You can copy it, but keep the file and folder structure from the workshop. No email-service API key belongs in this HTML.

Worked example: inspect the complete form

Read the form opening line first, then the field names and submit button. The hidden form-name value matches the form’s name. The honeypot field is a spam signal, not a complete abuse-prevention system.

  <form name="contact" method="POST" data-netlify="true"
        netlify-honeypot="bot-field" action="/thanks/">
    <input type="hidden" name="form-name" value="contact">
    <p hidden>
      <label>Leave this empty <input name="bot-field" tabindex="-1" autocomplete="off"></label>
    </p>
    <label for="name">Your name</label>
    <input id="name" name="name" autocomplete="name" required maxlength="80">
    <label for="email">Your email</label>
    <input id="email" name="email" type="email" autocomplete="email" required maxlength="254">
    <label for="message">Your message</label>
    <textarea id="message" name="message" rows="5" required maxlength="3000"></textarea>
    <button type="submit">Send message</button>
  </form>

Netlify: form setup

Extra implementation exercise

Before publishing, inspect the starter and list the form name, the three visitor-facing field names, and the thank-you path.

Show a worked solution

The form is contact. The visitor-facing fields are name, email, and message. The thank-you path is /thanks/.

The hidden form-name value identifies the hosted form, while bot-field is the honeypot.

  • Identifies contact; name, email, message; and /thanks/.
  • Does not count bot-field or form-name as visitor-facing fields.

Step 4

Publish only the practice site

Give the host the folder whose homepage is ready.

In your own Netlify practice project, publish the contents of starter so index.html is at the root. Enable automatic form detection if required; if you enable it after publication, publish the same files again.

Open the public page signed out and check the Forms area for the contact form. Ask the assistant to inspect the publishing folder if the page is missing.

A concrete example

Two separate checks: the visitor can open the form, and the host recognizes a form named contact. A missing page and a missing detected form call for different repairs.

Netlify: form setup

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Publish the practice folder and enable form handling

A local HTML file cannot activate a hosting provider’s form processor. This step connects the files to that processor.

In your own Netlify account, create a separate practice project using its supported manual-deploy flow. Publish the contents of starter/, with index.html at the site root. Uploading the whole workshop folder puts the homepage in the wrong place.

Check the project’s Forms area and enable automatic form detection if needed. If you enable detection after a deployment, deploy the practice files again so the HTML can be parsed.

Open the published page and verify that Netlify detected a form named contact. The supplied site is plain HTML: its form is present in the delivered page and needs no framework build command. Keep the opening attributes and matching hidden identifier intact. Review the provider’s current usage terms before publishing.

Local preview checks layout and ordinary browser validation only. To test Netlify Forms, publish the practice HTML to your own Netlify project with form detection enabled. If detection was enabled after that upload, redeploy so the host parses the form. Then test a real submission and delivery as separate steps.

Worked example: match the hosted form identifier

The identifier must agree in both places. This is a static HTML exercise; a JavaScript-rendered framework form needs additional setup described in the provider documentation.

<form name="contact" method="POST" data-netlify="true"
      netlify-honeypot="bot-field" action="/thanks/">
  <input type="hidden" name="form-name" value="contact">
  <!-- The named fields and submit button follow here. -->
</form>

Netlify: form setup

Extra implementation exercise

You enabled form detection after publishing and still cannot see contact in the Forms area. What should you do next, and what will you check afterward?

Show a worked solution

Deploy the practice files again after detection is enabled. Then check whether contact appears in the Forms area.

If it does not, inspect the deployed homepage source and folder structure before changing notification settings.

  • Republishes the correct static site folder after enabling detection.
  • Checks for contact in Forms and confirms that the uploaded HTML includes the form markup.

Step 5

Connect the notification inbox

Set delivery in the provider, not in visitor input.

Open the project’s submission-notification settings and add your test inbox. Complete any address confirmation your account requests. Keep the form’s visitor email available for replies.

Confirm the destination is the inbox you control and that notifications apply to the intended form. Account options and usage terms can vary.

A concrete example

Stored submissions can exist before any notification destination is set. Finish the destination setup for the intended form, then prove delivery with a new recognizable message.

Netlify: submission notifications

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Choose and verify the notification inbox

A captured submission and an email notification are different observations. Configure the second part explicitly.

Open the project’s form submission notification settings and add an email notification for the contact form. Use an inbox you control for this test.

If the recipient needs confirmation, complete that step before testing delivery. Current Netlify documentation describes confirmation for addresses outside the team; available options can depend on the account.

Keep the visitor’s address in the email field so that replying to a notification reaches the visitor. The visitor’s address is not the notification destination or a sender identity you should impersonate.

Worked example: two different addresses

The notification destination is the inbox you configured in your own account. The visitor types their reply address into the form.

When the notification arrives, inspect its reply-to value before replying. You should not need to copy the visitor’s address by hand.

Netlify: submission notifications

Extra implementation exercise

The form record contains “Workshop test C2”, but no notification arrives. Which notification and delivery checks will you make before editing the form?

Show a worked solution

Check that the notification is enabled for this form, that its destination is correct and confirmed when required, and that the message is not in spam or junk.

Do not conclude that changing the form’s CSS will repair a notification-delivery problem.

  • Checks that an email notification is enabled for the relevant form and correct destination.
  • Checks recipient confirmation if required and the destination’s spam/junk folder.

Step 6

Follow a real message through both places

Use exact text to avoid mistaking an old result for the new test.

On the published page, submit “Workshop test C3 — blue notebook” with your own address. Find that exact text in the provider list and notification inbox, then inspect the reply address.

Try a normal empty/invalid form submission too. Separate browser correction, stored message and delivered notification in your record.

A concrete example

If C3 appears in Forms but no email arrives, keep that partial result. The exact text and time give the assistant something to trace through notification and delivery settings.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Run a test with evidence you can match

Use one distinctive message so you can connect the request, stored submission, and email.

On the published practice site, send a short message such as “Workshop test C3 — blue notebook”. Use your own real inbox address in the email field.

Find the exact text in the provider’s submission list, then in the destination inbox. Record whether reply-to matches the address you entered. Use synthetic test text instead of someone else’s personal information.

Try an empty message and an invalid email through the normal browser form. Browser validation should help you correct them before submission. Browser checks improve usability; the provider must still handle untrusted requests and spam.

Worked example: a compact test record

Write down outcomes instead of “looks fine”. A received message and a missing notification should remain two different results.

Test message: Workshop test C3 — blue notebook
Provider record: found / missing
Notification email: found / missing
Reply-to matches my test address: yes / no
Empty message blocked by browser: yes / no
Invalid email blocked by browser: yes / no

Extra implementation exercise

Your record says “provider: found; inbox: missing; reply-to: not checked”. Is the inbox goal complete? What is the next action?

Show a worked solution

The provider accepted the submission, but the inbox goal is not complete. Investigate notification settings, recipient confirmation and delivery.

Keep reply-to marked “not checked” until there is a real notification to inspect.

  • States that inbox delivery is still unverified.
  • Investigates notification configuration/delivery and leaves reply-to unresolved until an email arrives.

Step 7

Fix the first stage that failed

Describe the observed break to your assistant.

If the homepage is missing, inspect publication first. If the form is absent, inspect detection. If the record exists but no email arrives, inspect notifications. Give your assistant the exact stage and a redacted example.

After one repair, repeat the same test. Changing the button’s appearance cannot prove a missing submission or email was repaired.

A concrete example

Public page works → form detected → message stored → inbox missing. This chain narrows the next check to notifications or delivery instead of rebuilding the form.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Debug the first broken boundary

Find where the evidence stops before changing code.

If the published homepage returns 404, check the deployed folder and root file first. A form hidden one folder too deep cannot be discovered from a missing homepage.

If the page opens but the form is absent from the provider, inspect form detection, the deployed HTML and the matching form identifier. If the record exists but email does not, inspect notifications.

For a problem that remains, keep the test message, time and observed status. Share a redacted example when asking for help; do not share account secrets or a visitor’s private message.

Worked example: a button that never submits

This element can display the next page, but it sends no form submission. Replace it with the submit button inside the form.

<!-- This only opens another page: -->
<a href="/thanks/">Send message</a>

<!-- This submits the form it belongs to: -->
<button type="submit">Send message</button>

Extra implementation exercise

A developer replaced the submit button with the link above. The thank-you page opens, but there is no stored message. Which boundary failed and what exact change fixes it?

Show a worked solution

The browser never submitted the form. Restore <button type="submit">Send message</button> inside the form and repeat the test from the published page.

Only investigate notification delivery after a matching submission exists.

  • Identifies missing form submission rather than email delivery.
  • Restores a type="submit" button inside the form.

Step 8

Add a useful topic choice

Let the assistant edit the form, then judge the result yourself.

Ask the assistant to add a required topic choice for project, speaking invitation and other, preserving the existing form handling. Publish to the practice project and send one distinctive test per choice.

Check the topic in each provider record and email. Try submitting without choosing a topic and record the visible correction.

A concrete example

For the Project choice, inspect the Project value in both the stored submission and its email. Repeat for Speaking invitation and Other; merely seeing all three labels on the page does not establish delivery.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Your assignment: add a required message topic

Extend the working form without breaking the journey you just verified.

Add a selector named topic with three options: a project, a speaking invitation, and something else. Give it a visible label and an empty initial option so a visitor must make a choice.

Publish your change to the practice project. Send one test for each topic, then inspect the provider records and emails. Try submitting without choosing a topic through the normal form.

Use a coding assistant if useful: ask it to add only the labelled selector while preserving the existing form identifier and action. Read its changes and run the same tests yourself.

Worked example: scope the change

A useful request is small enough to review: “Add a required topic selector to starter/index.html. Keep the current submission route and field names. Explain the changed lines.”

The reference solution is included in worked-solution/index.html. Try the assignment before opening it.

The complete reference walkthrough is available in reference/assignment-walkthrough.txt. Compare its steps with your own result; fill the test record from observations in your own project.

Extra implementation exercise

Build and test the required topic selector on your own practice site. What evidence shows that the new field travelled all the way to the inbox?

  1. Add the labelled selector and preserve the existing form handling.
  2. Send three distinct test messages, one per topic.
  3. Check browser validation for the empty option and inspect every stored record and email.
Show a worked solution

Use the starter's existing form name and named fields. Publish the practice folder to your own Netlify project with form detection enabled; a file:// preview cannot activate the hosted handler. If detection was enabled later, redeploy the HTML.

Submit your own test address and a unique message. Find the matching entry in the host's Forms area before investigating notification delivery. Configure the owner notification, find the received copy and test that Reply targets the visitor's test address rather than an unrelated system address.

Reference partial record: submission exists in provider, inbox message missing, reply-to not checked. That is not inbox completion. Check notification settings/delivery and spam; when the message arrives, verify Reply separately. The worked-solution form adds the required topic field, and the full source is available for comparison.

<label for="topic">What is your message about?</label>
<select id="topic" name="topic" required>
  <option value="">Choose a topic</option>
  <option value="project">A project</option>
  <option value="speaking">A speaking invitation</option>
  <option value="other">Something else</option>
</select>
  • Selector has a label, name="topic", required, and an empty placeholder option.
  • All three selected topic values appear in matching submission records and notification emails.
  • Normal empty-option submission is blocked and existing email/message fields still work.

Was this lesson useful?

Leave a like, or share it with someone who could use it.

Continue learning

Explore the other lessons