Skip to content
Sign inJoin waitlist

Forms — Catchup Framer

Catchup for Framer has one form, on the Contact page: a project inquiry with a name, an e-mail address, a service, a budget, a timeline and a message, sent with the “Submit Inquiry” button.

It has no destination when you copy the template: until you choose one, submissions go nowhere. The general guide is Forms; this page covers Catchup’s form.

Form Where it is Select it in
Contact form, button “Submit Inquiry” The Contact page, on the right of the contact details (under them on tablets and phones) Pages → /contact; in Layers the layer Form inside Main → Inner → Description
  1. Open the page and select the form: the layer named Form (the one that holds the six Label layers and Action) in the Layers tab, as above. Or click a field, then select its parent until the right panel shows Form. The button inside Action, also named Form (the Button/Form component), is the submit button.

  2. In the right panel → Form, find Send to and click Add….

  3. Pick a destination:

    Destination What happens
    Email Each submission is emailed to the address you enter
    Webhook Each submission is posted as JSON to a URL: Zapier, Make, n8n, your CRM, your own server
    Google Sheets Each submission becomes a row. Connect your Google account first in Settings → Forms (not connected in the template).

You can add more than one destination. Framer’s guide to webhooks is Connect Framer forms to a webhook.

The form’s other settings stay as they are: Redirect is empty, so the button itself says “Thank you” once the form is sent (the button’s Form state: Loading → Loading, Success → Success), and Antispam is set to Basic. The button also has an Error variant (“Something went wrong”) that the form state doesn’t use yet (fix it). The form sits on the page on Desktop, Tablet and Phone; one setting covers all three.

Each field has a name in the right panel (Input → Name): that is the key your email, webhook or sheet receives. Change its label and placeholder freely; change its name only if you also update where the data goes (a sheet’s columns, a webhook).

Field on the page Name the destination receives Notes
Name Name A text field, required. Placeholder “Your name*”
Email Email An e-mail field, required. Placeholder “Your email*”
Services Service Chips, one per service: a collection list of the Service CMS, each chip a Button/Option whose value is the service’s title. A new service gets a chip by itself. Not required
Budget Budget A select, required: Estimated Budget, Under $5,000, $5,000 – $10,000, $10,000 – $20,000, $20,000+
Project Timeline Project Timeline A select, required: ASAP, 2–4 Weeks, 1–2 Months, Flexible
Message Message A text area the visitor can resize (150 tall at first), not required. Placeholder “Your message”

Each field has a visible label above it (Name, Email, Services, Budget, Project Timeline, Message). Under the button, “By submitting, you agree to our Terms and Privacy Policy” links to the two legal pages.

Things to check before you publish:

  • Budget and Project Timeline. Their first option is a real choice: “Estimated Budget” is sent as the budget when the visitor doesn’t pick one, so the required check never stops anyone, and the timeline starts on “ASAP”. Read submissions with that in mind, or follow the fix in Questions and answers.
  • The Services chips. One choice is sent, but the chips can look selected several at a time (same place).
  • Message. It is optional; make it Required in the right panel → Input if you want every inquiry to say something.

Publish, then submit the form on the live site with a real address, on a phone as well as a laptop, and check that the submission arrived at every destination you added. Test on the published site rather than in the editor preview, so you see exactly what visitors get.

Submissions go only to the destinations you add. The form links to the Terms of Service and the Privacy Policy, whose texts are boilerplate with blanks to fill in (Questions and answers). Make the Privacy Policy say what you do with the data, and keep it in step with what you do. Don’t add senders to a mailing list unless they asked for it.