Help center

Publish and responses

Once the form is built, you publish it to open its public link, share it, and start collecting answers. Respondents need no account, spam is filtered out automatically, and every valid submission arrives as a new row in the linked table — which you read in the Bases module.

Publish the form

A form stays as a draft until you turn it public with the "Published" switch in the builder header. Its address has the format /f/ followed by a short random code — the code is generated when the form is first saved, never derived from the title, and stays the same from then on. Turning the switch off again stops new responses without deleting anything.

  1. 1Open the form in the builder.
  2. 2Turn on the "Published" switch in the header and click "Save" — changes only take effect after saving.
  3. 3In the "Public link" panel that appears, copy the link with the "Copy link" button.
  4. 4Share the QR code next to it for quick access from a phone.
  5. 5Open the link in another tab to check how the public page looks.
Respondents do not need an account or login: anyone with the link can answer. The public page opens outside your workspace and never exposes who owns the form or which table feeds it — and the random code cannot be guessed from your form's name.
While the form is not published, the link shows "Form not found." to everyone. Turn "Published" back off at any time to close the form to new responses — the link comes back to life if you publish again.

Spam and abuse protection

The public page carries a hidden trap field (a honeypot) that people never see but automated bots tend to fill in. Any submission with that field filled is rejected as spam before it reaches your table. Several other guards run on every submission:

  • Rate limit: a handful of submissions per minute from the same origin — beyond that, further ones are turned away, so a single sender cannot flood the table.
  • Size limits: oversized submissions and oversized individual answers are rejected.
  • Strict validation: every answer must match its column type — numbers, dates, email, URL, phone, and selection options are all checked on the server.
  • Duplicate protection: each page load gets a unique submission id, so a double-click on the submit button never creates two rows.

Read the responses

There is no separate response inbox. Each valid submission becomes one new row in the table the form is built from, with the answers written into the matching columns. You read and work with them in the Bases module.

  1. 1In the builder, click "View responses" — the shortcut in the public link panel that shows the response count — to jump straight to the table.
  2. 2Or open the Bases module on the linked table.
  3. 3Read each response as a row; the columns hold what was filled in for each field.
  4. 4Sort, filter, and export the rows to analyze the results.
Required fields are checked on the server at submission: if any is missing, the submission is rejected and the person sees an error, so incomplete responses never become rows.
Deleting a form does not delete its responses: the rows already collected stay in the table. To set up fields and source table, see "Build a form"; for everything you can do with the collected rows, see "Rows" in the Bases module.