Form basics

Form submission

A form submission is one completed send of a form: the values the visitor entered, plus details such as the time, that a backend receives, checks and stores.

Also called: form submissions, form response, form entry, lead

A form submission starts when a visitor presses the submit button and ends with the data where you can use it. Between those two points a lot can happen, and each step is a place where a submission can be rejected, delayed or lost.

The life of a submission

  1. Received. The browser or a script posts the fields to the form’s endpoint.
  2. Validated. Required fields, formats and file limits are checked (see form validation).
  3. Spam-checked. Honeypot, CAPTCHA and other signals decide whether it is genuine (see bot detection).
  4. Stored. The values and any files are saved so they can be read later.
  5. Delivered. Notifications and integrations run: an email, a Slack message, a spreadsheet row, a webhook.
  6. Answered. The visitor sees a thank-you message or lands on a thank-you page.

What you should be able to do with it

Read it, search it, export it and delete it. For form data that includes personal data, deleting and exporting are also privacy obligations, so a backend should make both easy.

In StaticForm

Every submission is stored in the dashboard, where you can search and filter it, mark it as read, export a form’s submissions as CSV or JSON and download uploaded files. Submissions are unlimited on every plan. A submission classified as spam still returns 200 OK, but it goes to the spam list with its score and skips the submit actions, so a wave of spam never fills your inbox. Each action that runs is logged per submission, and a failed action can be retried from the dashboard.

Learn more