What is Registration and event forms?
Registration and event forms collect structured attendee details for webinars, workshops, conferences, and cohort onboarding. Combine Contact Info, Date, and Legal consent; optionally add Payment for deposits or Schedule for booking-related flows, then publish and share a public link or embed.
How it works
- Create a form for your event or program and add Contact Info for registrant identity.
- Add Date fields for preferred sessions, arrival dates, or program start preferences as needed.
- Add a Legal block for terms, privacy, or waiver consent.
- Optionally add Payment (fixed Stripe amount) or Schedule (Calendly) when the registration requires fees or a booked slot.
- Publish and distribute via public link or embed; review registrants in Results.
Key capabilities
Contact, Date, and Legal
Capture who is registering, relevant dates, and required consent in one structured flow.
Optional Payment
Add a Payment block for deposits or registration fees when Stripe Connect is connected and your plan allows payment forms.
Optional Schedule
Add a Schedule block with Calendly when registration should also book calendar time.
Benefits
- One form covers identity, timing preferences, and consent for events and cohorts.
- Extend the same registration with payment or booking when the event requires it.
- Share a single published link or embed across email and landing pages.
Use cases
- Webinar and workshop registration
- Conference or meetup signup
- Cohort and program onboarding
- Paid event deposits with intake questions
Example workflow
An events team builds a workshop registration with Contact Info, a Date preference for session day, and Legal consent for the code of conduct. They add Payment for a fixed deposit via Stripe Connect on an eligible plan, publish, and share the public link in the invite email. Submissions list attendees and payment status in Results.
Tips and best practices
- Put Legal consent near the end so registrants see full details before agreeing.
- If capacity is limited, keep the form short and close the published version when full.
- Use Statement blocks to summarize agenda, location, and what happens after signup.
Limitations and plan notes
- Payment and Schedule are optional add-ons with their own connection and plan requirements.
- Formit does not replace a full event-management platform (ticketing tiers, seat maps, etc.).
- Stripe payments are separate from Formit SaaS billing for your workspace subscription.
Frequently asked questions
- What fields are typical for event registration?
- Contact Info for identity, Date when timing matters, and Legal for consent. Add Payment or Schedule only when fees or calendar booking are required.
- Can registrants pay a deposit in the same form?
- Yes. Add an optional Payment block with Stripe Connect for a fixed amount on an eligible plan. Respondent payments are separate from your Formit subscription billing.
- Can I book a call as part of registration?
- Yes. Add a Schedule block and connect Calendly so respondents pick a slot as part of the flow.
- How do attendees access the form?
- After publishing, share the public link or embed the form on an event landing page. Submissions stay bound to that published version.
Try it in FormitAI
Open the builder, configure this in a real form, publish a version, and share a link or embed. Start free - paid features stay honest about plan gates in the product.
Open FormitAI