Create Event

The event wizard is the one-page flow for creating a new event: basics, date and time, location, tickets, cover image and publishing, all in a single form. Reach it from My Events via Create Event, or by choosing a saved template.

Before you start

• Your plan's event limit is checked first — if you are already at the maximum events your plan allows, you are sent back to My Events with an error instead of the form.
• If you have events saved as templates, they appear as quick-pick chips above the form. Choosing one pre-fills title, description, dates, location, currency, timezone, custom fields and ticket types from that event.

What the sections cover

Event Basics

• Event type — Single Day, Multi-Day, Recurring, Series or Hybrid. This choice changes what the rest of the form asks for: only Hybrid requires a streaming/meeting URL, and only Recurring shows the recurrence pattern. Single Day, Multi-Day, Series and Hybrid all ask for a physical venue; Recurring does not.
• Title, category, description — description is rich text; an optional Write with AI button (shown only when AI features are enabled on the platform) drafts a description from a few bullet points you provide.
• Currency & timezone — default to your organizer payment currency and your account timezone, but can be overridden per event. This is the event's timezone for the rest of its life — see Good to know.

Date & Time

• Start and end date/time fields are enhanced by a consistent date-time picker (flatpickr) across browsers; the underlying value is a plain local date and time, not a UTC instant.
• Start must be in the future and end must be after start.
• For a Recurring event, set the frequency (weekly or monthly), the interval, which days of the week it repeats on, and an end condition — either an end date or a maximum number of occurrences (up to 52). Instances are generated as soon as the event is created.

Location, tickets, extras

• Location — physical venue name, address, city, state and country for every type except Recurring; a virtual/stream URL, required for Hybrid.
• Tickets — at least one type, each with a name, price and quantity (a price of 0 is treated as free). You can add as many types as your plan allows; once you hit the limit the Add Type button disappears.
• Cover image — optional, but feeds the Event Intelligence readiness check on the Overview page.
• Custom fields — optional text/number/URL/email attributes saved against the event record.
• Save as Template — stores this event, with its ticket types, so future events can be pre-filled from it.

Publishing

• Save as Draft — nothing is visible publicly.
• Publish Now — the event is created directly as Live.
• Schedule — pick a go-live date/time; a background job flips the event to Live automatically once that time passes (see Good to know).
• Visibility — Public (listed in browse/search) or Private (link-only, hidden from discovery). This is independent from the lifecycle status.

Good to know

• Event date/times are stored and shown as the wall-clock time you enter, in the event's own timezone — not converted per viewer. Someone in another timezone sees the same displayed time, not a converted local equivalent, so the timezone you pick here is what every later schedule comparison uses internally.
• Paid events need Stripe Connect first. If any ticket is priced above zero and you choose Publish Now (or Schedule) before Stripe Connect verification is complete, the event is created as Draft instead, with a warning — it is never silently published unable to take payment.
• Starting from a template pre-fills everything except the cover image file itself: the preview shows the template's image, but a browser cannot pre-fill a file input, so the new event is created with no image until you upload one again.
• A Scheduled event only goes live once the scheduled-publish job runs and the go-live time has passed in the event's own timezone — not the instant you save it.

Troubleshooting

• “Your plan allows a maximum of N events” — you are at your plan's event limit; remove an existing event or upgrade.
• Publish Now was chosen but the event saved as Draft — one of your tickets is priced above zero and Stripe Connect is not yet verified for payouts.
• The recurrence fields are not visible — they only appear once Event Type is set to Recurring.
• My new event has no cover image even though I picked a template — re-upload it; templates do not carry the image file itself forward.

Related

• My Events
• Event Overview
• Stripe Connect
• Ticket Types