The forms — Goeboek AI Prompts
Goeboek has three forms:
| Form | Where | form it sends |
After sending | Content |
|---|---|---|---|---|
| Contact | Contact page | contact |
“Thank you” on the button, the fields clear | form in src/content/pages/contact.json |
| Schedule tour | every property page | tour |
opens /success-scheduled |
tour in src/content/pages/property.json |
| Add property | Add property page | property |
opens /success-add-property |
form in src/content/pages/add-property.json |
The prompts build them with their checks, their states — a turning ring on the button while sending, then success or “Something went wrong” — and a hidden field that catches spam bots. There is no newsletter form.
The fields
Section titled “The fields”The contact form:
| Field | Name it sends | Required |
|---|---|---|
| Name | name |
yes |
email |
yes (an address that looks like name@host.tld) |
|
| Message | message |
no |
“Schedule tour”:
| Field | Name it sends | Required |
|---|---|---|
Property ID (filled in, e.g. 55R886) |
propertyId |
yes |
Property Name (filled in, e.g. Marble House) |
propertyName |
yes |
| Name | name |
yes |
email |
yes | |
| Phone | phone |
yes |
| Message | message |
no |
Add property, in the order of the page:
| Group | Fields (name it sends) | Required |
|---|---|---|
| Personal Information | name, email, phone |
all |
| Property Description | propertyName; location (Brooklyn, Manhattan, Queens, Staten Island, The Bronx) and category (Apartments, Condos, Houses, Villas), radio buttons; for (Sell, Rent); price; duration (/Days, /Months, /Years) |
all but location and category |
| Property Details | size (m2), bedrooms, bathrooms, floor, additionalSpace, furnishing, ceilingHeight (m), constructionYear and renovation (dates) |
all but renovation |
| Property Utility | heating, windowType (text); airCondition, fireplace, elevator, ventilation, intercom, cableTv, wifi (Yes, No) |
none |
| Message | message |
no |
A field left empty arrives empty; a radio group nobody picked does not arrive. The labels, placeholders, the button
(“Submit”) and its two messages (success, error) are content, in the files of the table above.
Before anything is sent, the form checks its fields: the first empty or wrong one gets the focus and every failing field keeps an orange (Accent) border until it is changed. On an error the form keeps what the visitor typed.
Demo mode
Section titled “Demo mode”Until you connect a service, the forms run in demo mode: they wait 800 ms, write the fields in the browser console and succeed — the contact form says “Thank you”, the other two open their thank-you page — but nothing is sent anywhere. Connect them before you publish.
Connecting a form service
Section titled “Connecting a form service”The forms send their fields with a POST, as form data (with Accept: application/json), to the address in an
environment variable:
| Tool / framework | Variable |
|---|---|
| Lovable, Bolt, Replit (Vite) | VITE_FORM_ENDPOINT |
| v0 and other Next.js projects | NEXT_PUBLIC_FORM_ENDPOINT |
| Astro | PUBLIC_FORM_ENDPOINT |
- Create a form at a form service — for example Formspree or Basin — or a webhook in Zapier, Make or n8n.
- Copy the address it gives you (e.g.
https://formspree.io/f/abcdwxyz). - Set it as the variable above: in the tool’s settings for secrets or environment variables, or in a
.envfile. The address is built into the site, so build or publish again after you change it. - Send each form once and check that the request arrives the way you want to read it.
All three forms go to the same address. Every submission also carries form (contact, tour or property) and
subject (“New contact enquiry”, “New tour request”, “New property submission”; the notification text of each form
in the content), which form services use as the e-mail subject. To send the forms to different places — your inbox, a
CRM, a spreadsheet — route them through a Zapier, Make or n8n webhook that looks at form.
When the service answers with an error, or the network fails, the button says “Something went wrong”.
Other ways
Section titled “Other ways”- Your tool’s database: Lovable and some others can save submissions in a database and email you. Ask: “Save the contact, tour and Add property submissions to the database and email me each one.”
- Your own server: the endpoint can be any URL that accepts a form POST — your CRM, a serverless function.
Changing a form
Section titled “Changing a form”The fields, their labels and placeholders are content (each with name, label, placeholder, and type,
required or options where it has them): ask your tool to add or remove a field there and show it in the form
(“Make Phone optional in the tour form”, “Add an optional Budget field to the contact form”). A field arrives at your
form service under its name, so keep the names you already use somewhere. The thank-you pages’ text and buttons are
in pages/success.json (tour, property).
Privacy
Section titled “Privacy”The forms collect personal data (names, e-mail addresses, phone numbers). They go only where you point them: choose a service you trust. Goeboek has no privacy page: write a privacy policy for your site (a new page, see Making it yours) that says what the forms collect and where it goes.
The hidden fax field stays empty for people and gets filled by bots; when it is filled, the form shows success and
sends nothing. Most form services also filter spam themselves.