Take bookings, orders and enquiries

What you need first

Decide what you want to know before you ask for the form.

• The fields you actually need — name, phone, date, number of people.
• Who is allowed to read them. Usually only you.
• What happens after someone sends it — do you call them, or email them?

01 · Say what you want to collect

“Add a booking form: name, phone, date, number of people.” Copy the paper book or spreadsheet you use today — it is the most accurate description of what you need.

02 · Let it make the storage

The place the data is kept is created together with the app. There is no separate service to sign up for and no separate bill. One table is one spreadsheet: a row is one booking, a column is one field.

03 · Ask for the list screen too

A form with nowhere to read it is only half the job. “Add a page where I can see the bookings, newest first.” Ask for that page to require a login — see the login guide.

04 · Send yourself a test

Fill the form in on the preview like a customer would. Then open the list screen and check the row is there, with the right values in the right columns.

05 · Check who can read it

Before you publish, the pre-publish check looks at whether the data rules are switched on and whether anything is left open to the public. Two of the nine checks are about exactly this.

If you get stuck

Can visitors attach a file? Yes. Uploads are capped at 5MB each and limited to png, jpg, webp, gif, avif and pdf. SVG is not accepted because it can carry scripts. Up to 200 uploads a day per project.

Can I get an email when someone books? Yes, to you. Notifications currently go to the project owner, not to arbitrary customer addresses. The messaging guide explains the limit.

I need one more field. Ask for it. Adding a column is a small change. Existing rows keep the values they already had.