Plan event logistics from each registration
Every sign-up creates a task in the Event ops List carrying guest count, dietary needs and accessibility requirements.
New submission on your event registration form
Create a task in the "Event ops" List, set a due date matching the event, and map dietary and session preferences to custom fields
One-directional. A submission triggers the action — nothing is written back into your form.
Catering numbers and accessibility requests are the two things an events team finds out too late. Feeding registrations into the Event ops List keeps both in front of the people planning the room, updated with every new sign-up rather than at the Friday count.
Conference organisers and internal comms teams run this alongside their ticketing. The task is not the ticket; it is the logistics record for one attendee, sitting on the same board as the run sheet and the supplier chase-ups.
Setting it up
- 1
Publish the Event Registration Form template and drop the embed into your event page with two lines of HTML.
- 2
In ClickUp, create the Event ops List inside your events Space, with a status for each stage: Registered, Confirmed, Checked in.
- 3
Add custom fields to that List for ticket type, guest count, dietary restrictions and accessibility requirements.
- 4
In Zapier, pick formformform's New Submission trigger and select the registration form.
- 5
Add the ClickUp Create Task action, choose the Event ops List, and set the task name to Full Name so the board reads as an attendee list.
- 6
Set the due date to the event date on the action step as a fixed date rather than a mapped field, since every attendee shares it.
- 7
Map Dietary Restrictions and Accessibility Requirements to their custom fields, then group the List by the dietary field to read the caterer's numbers in one view.
- 8
Register once through the live form, confirm the custom fields populated, then set the Zap live.
What maps where
Using the Event Registration Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | ClickUp |
|---|---|
| Full Name | Task name |
| Ticket Type | Ticket type dropdown custom field |
| Number of Additional Guests | Guest count number custom field |
| Dietary Restrictions | Dietary custom field, grouped for the catering count |
| Accessibility Requirements | Accessibility custom field flagged to the venue lead |
| Emergency Contact Phone | Emergency contact custom field on the task |
Variations worth knowing
For a multi-track day, add a multi-select sessions question to the form and use a looping step to create a subtask under each session's own task in Event ops. Room sizing then comes from the subtask count instead of a spreadsheet.
Add a path that runs only when Accessibility Requirements is not empty. That branch creates the task and assigns it to whoever talks to the venue, so a step-free access request is seen on the day it arrives rather than the week before.
If something isn't arriving
That is expected when the due date is the event itself. Add a second date field for the action each attendee needs — badge printed, meal confirmed — and sort the Event ops List by that field instead of the deadline.
Number of Additional Guests excludes the registrant. Either total that column in ClickUp and add the task count to it, or use a Formatter step to add one to the value before it reaches the custom field.
Frequently asked questions
Can attendees change their dietary choice after registering?
Not on the existing task. The form sends one submission and reads nothing back from ClickUp, so publish a short amendment form that creates a follow-up task, or edit the custom field in ClickUp by hand before the catering deadline.
How do I handle registrations for several events at once?
Add an event question to the form and use paths to choose the List, or run one Zap per event against the same form with a filter on that answer. Either way you keep one form to maintain and one place to read numbers.
Is there a limit on how many sign-ups this can handle?
During early access, forms and responses are both unlimited and free. The practical ceiling is your Zapier plan's task count, since each registration consumes one Zapier task for every action step in the flow.
Related automations
- Create a candidate task for each new applicant
Every application creates a task in the Candidates List, titled with the applicant and role and set to New Applicant.
- Open a tracked task for every support request
Each help desk submission opens a task in your Support List, tagged by issue type and set to Open for the duty agent.
- Route demo requests to a rep as sales tasks
New demo requests open a task in the Sales pipeline List, assigned round-robin with a follow-up due date attached.
- Send new orders to a fulfilment list
New orders open a task in the Fulfilment List with the item, quantity and shipping address on sortable custom fields.
- Turn bug reports into triaged dev tasks
Each bug report opens a task in your Bugs List with the steps to reproduce in the description and severity on a custom field.
- Add every RSVP to your confirmed guest list
Each RSVP creates a card on the "Confirmed guests" list with the ticket type as a label and dietary notes in the description.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free