Skip to content
Sign inJoin waitlist

The contact form — Catchup AI Prompts

Catchup has one form, the inquiry form on the Contact page, beside the studio’s details. The prompts build it with its states — sending, “Thank you”, “Something went wrong”, each shown on the submit button — and a hidden field that catches spam bots.

Form Where form it sends Content
Inquiry The Contact page, at the right on desktops and under the details on tablets and phones contact contactForm in src/content/pages/contact.json
Field Name it sends Required
Name name yes
Email email yes (a valid address)
Services — Branding, Design, Development, Photography (one choice) service no
Budget — a list of four ranges budget yes
Project Timeline — ASAP, 2–4 Weeks, 1–2 Months, Flexible timeline yes
Message message no

Labels, placeholders, the choices and the button texts are in the form’s fields, submit, success and error. Budget and Project Timeline start on an empty placeholder that a visitor has to replace; a field left empty is sent empty. Under the button, the consent note links to your Terms and Privacy Policy pages (consent in contactPage).

Until you connect a service, the form runs in demo mode: it waits a moment and says “Thank you”, but nothing is sent anywhere. Connect it before you publish.

The form sends its 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 the form once and check that the inquiry arrives.

Every submission also carries form (contact) and subject (the form’s notification: “New inquiry from the Catchup website”), which form services use as the email subject — change it to your own name. To send the inquiries to several places — your inbox, a spreadsheet, a CRM — route them through a Zapier, Make or n8n webhook.

When the service answers with an error, or the network fails, the button says “Something went wrong” and the visitor’s answers stay 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 contact form 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 placeholders, labels and choices are content (fields of contactForm): ask your tool to add or remove a field there and show it in the form (“Add an optional Company field after Email in the contact form”, “Change the Budget ranges to …”). 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 in your Privacy Policy (collections/legal.json) what the form collects 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.