Klaviyo logo

Put workshop registrations on their own reminder list

Each registration lands on a session-specific Klaviyo list and tracks a Registered event, so confirmations and reminders send themselves.

When this happens

New submission on an RSVP or workshop registration form

Do this

Subscribe the profile to an event-specific Klaviyo list and track a Registered event for reminder flows

One-directional. A submission triggers the action — nothing is written back into your form.

Free workshops fill up and then half the room does not turn up. Confirmation and reminder emails fix most of that, and they need a list holding this session's registrants and nobody else.

Studios and small venues run this per session: a Saturday breathwork class, a pottery evening, a beginners' run club. Each registration lands on a dedicated Klaviyo list, the reminder flow works off that list alone, and the marketing list stays separate from people who only wanted a seat.

Setting it up

  1. 1

    Set the session choice up as a dropdown of named sessions, so registrants pick from your options rather than typing a date you then have to interpret.

  2. 2

    In Klaviyo, create a list per session — Breathwork, 12 March, for example — instead of one Workshops list, so a reminder never reaches last month's attendees.

  3. 3

    In Zapier, create the Zap with the New Submission trigger and pick the workshop registration form.

  4. 4

    Add a Zapier Paths step keyed on Workshop You're Registering For, with one path per live session.

  5. 5

    In each path, use Subscribe Profile to List pointing at that session's list, with the consent status set to reflect what the form asked for.

  6. 6

    Add a Track Event step with the metric Registered, passing the session name and Experience Level as event properties.

  7. 7

    Build the Klaviyo flow on that list: a confirmation immediately, a reminder the day before, and a what-to-bring note on the morning.

  8. 8

    Register yourself for one session, confirm you appear on the right list with the Registered event, 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 fieldKlaviyo
Full NameFirst and last name attributes on the profile, used in the confirmation greeting and the door list
Email AddressThe profile identifier, and the address the confirmation and reminders are sent to
Phone NumberThe phone number attribute, held for a same-day text if a session moves — only usable if the form asked for that consent
Workshop You're Registering ForDecides which session list the profile is subscribed to, and rides along as a property on the Registered event
Experience LevelAn event property, so the pre-session email can tell a first-timer what to expect
Accessibility & AccommodationsA profile property the studio reads before the session, not something a flow acts on

Variations worth knowing

One list, many sessions

A path per session gets heavy past four or five. Keep a single Workshops list instead and put the session name on the Registered event. Flow filters on that property then decide who gets which reminder, and adding a session means editing a dropdown rather than rebuilding the Zap.

Ask for marketing consent separately

Booking a class is not agreement to a newsletter. Add a separate opt-in question to the registration form and use a second subscribe action, filtered on that answer, to add those people to your marketing list. The session list carries on working either way.

If something isn't arriving

Registrants get reminders for a workshop they did not book.

One list is serving several sessions. Check each path condition against the exact dropdown values in the form — a renamed option stops matching and falls through to the default path. Rename options in the form and the Zap together, or move the session name onto the event and filter there instead.

Somebody registered but no confirmation arrived.

The subscribe action ran without a consent status, so Klaviyo holds the profile on the list but will not email it. Set the consent on the action step and replay the task. If it still does not send, check the profile has not been suppressed by an earlier bounce.

Frequently asked questions

Do I need a new Klaviyo list for every workshop?

Only if the reminders differ. A list per session gives clean sends and an obvious headcount, but it multiplies fast. Past a handful of sessions a month, one list plus a session property on the Registered event is easier to keep tidy.

How do I see how many places are left?

The Klaviyo list count is the live number — it rises as each registration lands. Read it there rather than in the form, and close or unpublish the form once the session is full, since the count is not fed back into the registration page.

Can Klaviyo take someone off the list if they cancel?

Not through this connection, which only runs form to Klaviyo. Handle cancellations with a short second form that tracks a Cancelled event, then add a flow filter that skips the reminder for anyone who has one.

Related automations

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