Put event registrants on a dedicated event list
Registrants land on their own Constant Contact list with an event tag, so reminders and follow-ups go only to people who booked.
New submission on your event registration form
Add the registrant as a contact to a dedicated event list and apply an event tag in Constant Contact
One-directional. A submission triggers the action — nothing is written back into your form.
Reminder emails go wrong when they go to everyone. Keeping registrants on their own list means the "doors open at nine" note reaches the people holding a place and nobody else, and the thank-you afterwards has the same clean audience.
Course providers, community venues and anyone running a recurring workshop series use this. Because the event name comes off the form itself, one registration form can feed several event lists as the calendar moves on, rather than needing a fresh Zap each season.
Setting it up
- 1
Create the event list in Constant Contact first — "Spring Workshop 2026", not a general "Events" list — so the Zap has something specific to point at.
- 2
Publish the workshop registration form in formformform with the workshop question set to single choice rather than free text, so the tag value stays consistent.
- 3
In Zapier, choose formformform "New Submission", select the registration form, and pull in a test submission that has a workshop actually selected.
- 4
Add the Constant Contact "Create or Update Contact" action and set the target list to the event list you just created.
- 5
Map Email Address to the contact email and Full Name to the name fields, or to first name alone if your audience mostly types one word.
- 6
Apply the workshop name as a tag on the contact, so you can filter attendees inside Constant Contact without relying on list membership alone.
- 7
Send Experience Level and the dietary answer to custom contact fields — they are useful when you write the pre-event email, and Constant Contact will not hold them as tags.
- 8
Register once through the live form, confirm the contact appears on the event list carrying the tag, then turn the Zap on.
What maps where
Using the Workshop Registration Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Constant Contact |
|---|---|
| Full Name | Contact name in Constant Contact |
| Email Address | Contact email address — the match key for repeat registrants |
| Workshop You're Registering For | Tag on the contact, and the value that picks the event list |
| Experience Level | Custom contact field, for tailoring the pre-event email |
Variations worth knowing
Add Zapier paths keyed on the workshop answer and give each path its own Constant Contact list. The form stays as a single embed on your events page while every workshop keeps a clean audience of its own.
Run a short attendance form after the event and let it update the same contact with an "attended" tag. Constant Contact matches on the email address, so both submissions land on one record rather than two.
If something isn't arriving
Constant Contact only applies tags that already exist on the account when the Zap runs; it will not create one mid-flow. Add the tag by hand before the first registration, spelled exactly as the form's answer choice.
Create or Update overwrites custom fields with the newest submission but keeps earlier tags. Read the tag list on the contact rather than the workshop custom field when you need their full booking history.
Frequently asked questions
Can I stop registrations once the workshop is full?
Not from the Zap. Close the form in formformform, or use conditional logic to hide the booking questions and show a waitlist message instead. Constant Contact has no way to signal capacity back, since nothing is read into the form.
Do I need a separate form for every workshop?
No. One registration form with a single-choice workshop question covers a whole season. Route on that answer inside Zapier to pick the right Constant Contact list, and add each new workshop as a choice when the calendar changes.
What happens to the answers I do not map?
They stay in formformform, where you can search, filter and export them with the rest of the submission. Only mapped fields reach Constant Contact, which keeps the contact record down to what the marketing side actually uses.
Related automations
- Add buyers to a customers list after each order
Each order form submission adds the buyer to a Customers list in Constant Contact for updates and repeat-purchase emails.
- Add newsletter signups to your main email list
Every newsletter signup lands in Constant Contact on your main list, with the topics they picked carried across as tags.
- Move survey respondents to a follow-up list
A satisfaction survey reply updates the contact in Constant Contact and moves them to a follow-up list with a score tag.
- Segment webinar sign-ups by the session they picked
Webinar registrants join a webinar list in Constant Contact, tagged by the session topic they chose, ready for matched follow-up.
- Tag contacts by the guide they asked for
Each gated download creates a Constant Contact contact tagged with the asset requested, so nurture emails match the interest.
- Add newsletter signups as tagged Kit subscribers
A signup on your site lands in the Kit form you chose, carrying a newsletter tag and the topics the reader picked.
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