Forms Overview

Forms are multi-step, conversational data-collection flows: contact forms, lead-gen quizzes, surveys, intake forms, job applications. They feel like a modern one-question-at-a-time experience, support branching logic, and capture clean, typed data.

What a form is

A form is a sequence of typed fields grouped into a flow. It can:

  • ask one question at a time or show fields together,

  • branch based on answers (logic),

  • open with a welcome screen and end on a thank-you screen,

  • carry hidden fields prefilled from the URL (for example campaign tags),

  • write submissions straight into your CRM.

Forms and booking share the same underlying model — a booking flow is a form wired to a calendar.

Field types

Forms support a wide range of field types so the data you collect is structured, not free text:

  • Basics — short text, long text, email, phone, number, date, time, dropdown select, checkboxes, consent.

  • Choice and rating — picture choice, star/heart/thumb rating, opinion scale, Net Promoter Score (NPS).

  • Statement — a non-input screen for instructions or a message.

  • File upload — collect documents or images.

  • Smart fields — website/URL, country, region, postal code, full address, currency, and a Google Places location picker.

Each field can be required, validated (length, range, pattern), and mapped to a column in your CRM.

Where forms render

Every form has one canonical URL:

https://<your-site>/f/<flow_id>

That single URL works as a standalone page, and the same form can be embedded inside your pages. See Embedding Forms.

Starting from a template

SpiderPublish ships ready-made form templates you can clone and adapt:

  • Contact form

  • Lead-gen quiz

  • NPS survey

  • Event RSVP

  • Job application

When to use a form

Reach for a form when you want to collect structured, typed input from visitors:

  • Contact, lead-gen, survey, and intake flows where you need clean, validated answers.

  • Branching experiences — quizzes and qualifying flows that adapt to earlier answers with logic.

  • Submissions that flow into your CRM automatically, mapped field by field.

If you instead need visitors to pick a time and get a calendar invite, use a booking flow — it shares the same model but is wired to a calendar.

Next steps