Forms and Submissions

Purpose

The Forms collection is a no-code form builder. Build a form once with the fields you want, then embed it on any page via the Form block. Submissions appear in the Form Submissions collection.

When to use this

• Membership enquiries, society bookings, contact forms, event entries, surveys.
• For the standard contact form, see Contact Settings — there's a pre-wired version.

Key fields (Forms collection)

• Title — internal name.
• Name — slug used in the URL of the embed.
• Fields — array of field configs. Each field has a type:
  • Text, Number, Email, Checkbox, Select, Country, State — standard inputs.
  • Date, Signature — custom nooQ fields.
  • Heading, Paragraph, Divider — layout-only, no input.
  • Calculation — derived value from other fields (e.g. fee × players).
  • Repeater — let users add multiple instances (e.g. a list of players).
• Confirmation type — Message (show a thank-you) or Redirect (send to a URL).
• Confirmation message — the thank-you text.
• Redirect URL — used when confirmation type is Redirect.
• Emails — automatic emails to send on submission (e.g. notify the secretary, email a receipt to the submitter).

Common tasks

Build a membership enquiry form

1. Communications > Forms, Create New.
2. Title: "Membership Enquiry". Name: membership-enquiry.
3. Add fields: Full Name (Text), Email (Email), Phone (Text), Membership Type (Select with options Junior/Full/Senior), Notes (Text, multi-line).
4. Confirmation = Message: "Thanks — we'll be in touch within two days."
5. Email: To = membership@yourclub.com, Subject = "New enquiry from {{fullName}}".
6. Save.
7. On the Membership page, add a Form block and pick this form.

See submissions

1. Communications > Form Submissions.
2. Filter by Form, by date, or by submission status.
3. Open a submission to see the full payload.

Gotchas

• Don't wrap the embed inside a <form> tag — the form already submits via its own button. Nested forms cause the wrong submit to fire.
• Calculation fields are evaluated client-side — they're shown to the user but the value isn't trusted on the server. Validate fees on the receipt email if money is involved.
• Submission data is plain JSON — no encryption at rest. Don't collect anything sensitive (full DOB, passport, bank).
• Forms aren't versioned — editing a published form changes how new submissions look. Old submissions still reference their original fields.

Related

• Contact Settings
• Page builder