Event Capacity + Waitlist
Description
3 steps
- 1
Read the new response
Review form capacity, registration rules, and operator-confirmed waitlist evidence. Do not treat waitlist rows as response records.
- 2
Decide the next action
Decide the next action from the response, score, date, or category.
- 3
Apply to operations
Confirm access, targets, and copy before execution. Keep results separate from schedules and append business tags or notes while preserving existing values.
Prompt Example
Goal: Switch event registration between accepted, waitlisted, and closed when capacity is reached. Fields: Respondent email address, Response body, and Target date and time. Read party size and requested slot from the response body. Rules: Confirm the registration if capacity remains, waitlist it if capacity is full, and close it if the registration deadline has passed. Actions: Read capacity, deadline, and registration settings with get_form; configure update_form and set_waitlist only for operator-confirmed rules. Capacity counts responses in one form; do not infer available seats across party sizes or multiple slots. Native waitlist entries have no response ID and are not returned as responses by get_responses; never target them with reply_to_respondent or update_response. The configured native waitlist mechanism handles offer notices from actual capacity and expiry. Use reply_to_respondent only for ordinary registrants with a verified existing response ID, and append verified business tags to those responses. Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them. Records: update_response accepts only new / in_progress / resolved / spam for status. Use status="in_progress" for new open work; do not reopen existing resolved/spam responses, and use resolved only when the work is verified complete. Immediately before changing business tags or notes, read their current values with search_responses. Pass the deduplicated full set of existing plus added tags (at most 20 tags, 50 characters each), or the full existing notes with the addition appended. If current values cannot be read or limits would be exceeded, ask instead of overwriting. Keep schedules and drafts separate from verified sends, writes, and attendance.
For you
- steps
- 3 steps
- Required plan
- Free
- Required integrations
- FORMLOVA
What this workflow solves
Form responses arrive, but capacity and waitlist management for event registration forms still depends on manual checking, causing delayed or missed follow-up.
Best for
- event operations
- registration management
Expected outcome
When you run the prompt in chat, each reviewed response moves into a clear capacity and waitlist management for event registration forms state, so the team can focus on the next required action.
Setup notes
- Connect FORMLOVA MCP in your AI client and confirm permission to read and update responses for the target form.
- Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them.
- Response review, organization, and ordinary individual replies are available on Free. Check AI client and external service terms separately.
- Business labels are not response statuses. Read current tags/notes immediately before updating and preserve them when appending; tags allow at most 20 values of 50 characters each. Ask if values cannot be read or limits would be exceeded.
- Native waitlist rows do not have response IDs. Distinguish native shared-capacity offers from ordinary replies to existing response IDs. Verify waitlist sends and acceptance from operator-confirmed records.
FAQ
Can this work with an existing form?
Yes. Map the existing response fields to the required slots and adjust the notification or record destination.
Read the background
More in this category
Event Reminder + Follow-up
EventsStandard+An official workflow for confirmation, reminders, and post-event follow-up for registrations.
Seminar Registration to Survey
EventsStandard+An official workflow for seminar registration, day-of reminders, and post-event survey.
Slack Notification + Google Sheets Log
EventsFreeAn official workflow for sending form responses to Slack while keeping a Google Sheets operations log.
