Skip to content
Sign inJoin waitlist

The forms — Semono AI Prompts

Semono has three forms. The prompts build each with its states — sending, “Thank you”, “Something went wrong”, each shown on the submit button — and a hidden field that catches spam bots. All three send to the same address, each with its own name, so you can tell them apart.

Form Where form it sends Content
Contact inquiry The Contact page contact contactForm in src/content/pages/contact.json
Consultation request Every service page, in the white card consultation consultationForm in src/content/pages/service.json
Job application Every position’s page application careerForm in src/content/pages/career.json
Field Name it sends Contact Consultation Application
Full Name / Name name required required required
Business Email / Email email required required required
Phone Number / Phone phone
Company Name company —
Service Required (a list of choices on Contact; the page’s service on a service page) service required —
Project Budget (Under $5,000, $5,000 — $10,000, $10,000 — $25,000, $25,000+) budget required — —
Project Details details —
Job Position (the page’s position) position — —
LinkedIn URL linkedin — —
Cover letter letter — —

Labels, placeholders, the choices of the selects and the button texts are in each form’s fields, submit, success and error. Empty fields are sent empty.

Until you connect a service, the forms run in demo mode: they wait a moment and say “Thank you”, but nothing is sent anywhere. Connect them before you publish.

The forms send their fields as 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
  1. Create a form at a service that accepts JSON posts — for example Formspree or Basin — or a webhook in Zapier, Make or n8n.
  2. Copy the address it gives you (e.g. https://formspree.io/f/abcdwxyz).
  3. Set it as the variable above: in the tool’s settings for secrets or environment variables, or in a .env file. The address is built into the site, so build or publish again after you change it.
  4. Send each form once and check that the submissions arrive.

Every submission also carries form (contact, consultation or application) and subject (the form’s notification: “New contact inquiry”, “New consultation request”, “New job application”), which form services use as the email subject. To send applications somewhere else than inquiries — a recruiting tool, another inbox — route the submissions through a Zapier, Make or n8n webhook and branch on form.

When the service answers with an error, or the network fails, the button says “Something went wrong” and the visitor’s text stays in the fields.

  • Your tool’s database: Lovable and some others can save submissions in a database and email you. Ask: “Save the submissions of the three forms to the database and email me each one.”
  • Your own server: the endpoint can be any URL that accepts a JSON POST — your CRM, a serverless function.

The fields, their labels and the choices are content (fields of each form): ask your tool to add or remove a field there and show it in the form (“Add an optional Website field after Company Name in the contact form”). A field arrives at your form service under its name, so keep the names you already use somewhere. When your services change, change the contact form’s Service Required choices too (contactForm.fields.service.options).

The application form takes a LinkedIn address and a cover letter, not a file: a CV upload needs a service that stores files. Ask your tool for one if you need it.

Submissions go only where you point them. The demo’s Privacy Policy (collections/legal.json) is sample text: write your own, saying 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 says “Thank you” and sends nothing. Most form services also filter spam themselves.