Skip to content
Sign inJoin waitlist

The forms — Marai Neesu AI Prompts

Marai Neesu has two 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. Both send to the same address, each with its own name, so you can tell them apart.

Form Where form it sends Content
Project inquiry The Contact page contact contactForm in src/content/pages/contact.json
Newsletter sign-up The Blog page, under the articles newsletter newsletter.form in src/content/pages/blog.json
Field Name it sends Contact Newsletter
First Name firstName required —
Last Name lastName required —
Email email required required
Phone Number phone required —
I’m interested in … (checkboxes: your services’ titles) interests — every ticked one, as a list —
Project Budget (USD) budget required —
Message message —

Labels, placeholders and the button texts are in each form’s fields, submit, success and error; a field is required when its required is true. Empty fields are sent empty. The interests are the titles of collections/services.json, in its order.

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 or newsletter) and subject (the form’s notification: “New contact inquiry”, “New newsletter subscriber”), which form services use as the email subject.

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.

A form service collects the sign-ups as messages. To add them to a mailing list (Mailchimp, Kit, Brevo, Beehiiv…), route the submissions through a Zapier, Make or n8n webhook that branches on form and adds the email of each newsletter submission to your list — or ask your tool to send the newsletter form to your mailing service’s own sign-up address instead.

  • Your tool’s database: Lovable and some others can save submissions in a database and email you. Ask: “Save the submissions of the two 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 and their labels 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 Company field after Last Name in the contact form”). A field arrives at your form service under its name, so keep the names you already use somewhere.

Submissions go only where you point them. Say on your site what the forms collect and where it goes, and ask for consent where the law requires it before adding someone to a mailing list.

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.