Public form
AvailablePlace a simple name-and-email form on an event-specific public page. Bloomod sends the verification magic link after submission.
API referenceBloomod does not create a global customer table. Attendees belong to the event where they registered or were imported, so each event starts with a clear, separate list.
Product launch / Attendees
148 attendees · 5 shown
| Attendee | Added through | Verification | Calendar automation | Invite | Last activity |
|---|---|---|---|---|---|
| Maya Patel | Public event form | Verified | Enabled | Sent | Verified 2h ago |
| Arun Mehta | CSV import | Verified | Enabled | Sent | Imported yesterday |
| Neha Shah | Event landing page | Unverified | Not sent | Manual only | Registered 3d ago |
| Rohan Das | XLSX import | Verified | Enabled | Sent | Imported 5d ago |
| Sana Khan | Public event form | Unverified | Not sent | Manual only | Registered 5d ago |
Add Bloomod’s public form to an event page, or use the event’s own Bloomod landing page. An attendee enters their name and email, submits, and is saved only to that event.
Public event form
Product launch · 22 August
Every input creates an attendee record for the selected event, never a reusable global contact.
Place a simple name-and-email form on an event-specific public page. Bloomod sends the verification magic link after submission.
API referenceUse a dedicated Bloomod landing page for an event when you do not have a page of your own.
Import a list into one event and mark each attendee Verified or Unverified during the mapping step.
Add one attendee directly to the selected event and set their verification status deliberately.
Verification is event-specific. A public-form attendee becomes Verified by clicking their email magic link. Imports and direct entries let the event owner set the status.