Event registration command center for Fillout signups

Build me an event registration command center that my ops team opens every day in the run up to an event and works out of during the event itself. People register through a Fillout form, and today we end up exporting that to a spreadsheet to track who actually showed up. I want one screen instead.

The main view is a registration table. Load every registration with the Fillout List Form Submissions operation against my registration form, and show one row per registrant with their name, email, chosen session, ticket type, dietary requirements, accessibility notes, and current check in status. Keep the dietary and accessibility answers visible in the table itself rather than hidden behind a detail click, because catering and venue staff are the people scanning this. Add filters for session, ticket type, and dietary needs, plus a free text search on name and email. Across the top, show headline counts: total registered, confirmed, checked in, no show, and still awaiting confirmation, and a per session breakdown. The counts must reflect the current filters and update immediately when someone changes a status.

Important constraint: Fillout submissions cannot be modified through the API. So check in status, attendance, and everything the agent drafts must live in a Zite table (Fillout's database product) keyed by the Fillout submission id, and never be written back onto the submission. Use Fillout Create Record to add a status row the first time a registrant's status is set, Update Record when it changes after that, and List Records to read the whole status table back and join it to the submissions by submission id on every load. On first run, if the table does not exist yet, create it with Create Table (or Create Database if needed) with fields for submission id, registrant name, registrant email, session, status, checked in at, and notes.

Staff should be able to set status straight from the row without opening anything: confirmed, checked in, or no show, as inline buttons or a small dropdown. Each change writes to the Zite table and the headline counts update live. Clicking a registrant opens a detail panel showing their full submitted answers from Fillout Get Submission by ID, so an organizer can see every question they answered, alongside their current status, when they were checked in, and any reminder drafts written for them.

Add a "Draft the reminder wave" button that kicks off a background agent. The agent should segment the registrants who have not confirmed yet by comparing the submissions from List Form Submissions against the status rows from List Records, then draft a personalized reminder email for each one that references their chosen session, the session time, and any special requirements they flagged such as dietary needs or accessibility. It writes each draft into the Zite table with Create Record, storing the submission id, recipient email, subject, body, and a draft status, so the app can read them back.

Those drafts show up in a drafts panel where an organizer reviews them one by one. They can edit the subject and body, approve, or discard. Approving sends the email with the Gmail Send a Message operation and then marks that draft row as sent with Update Record, including the sent timestamp, so nobody double sends. Keep this draft then approve rather than auto sending, because these go to real attendees and organizers want the review step. Show a count of pending drafts on the button so it is obvious when there is a wave waiting for review.

Finally, add a per session action in the session breakdown: a button that creates the calendar hold for that session with the Google Calendar Create Event operation, using the session name, its start and end time, and the room or location, and invites everyone whose status is confirmed for that session as attendees. Confirm before creating, show the resulting event link in the app, and record on the session that the hold has been created so it is not made twice.

Let me set the Fillout form id, the Zite database and table, the list of sessions with their times and locations, and the calendar to use in a small settings area, so the app can be pointed at the next event without rebuilding it.