Skip to content
Automations

The follow-ups that used to fall through the cracks

Trigger emails, texts, tags, and lead-stage updates from any event in your studio. New form submission? Welcome email goes out. First class booked? Tag the customer. Membership lapsed? Reactivation flow fires. Set it once, watch it run forever.

Book a Demo See Pricing
  • ✓ 7 trigger types covering every studio event
  • ✓ 5 action types — email, SMS, tags, customers, leads
  • ✓ Immediate, delayed, or event-relative timing
Triggers

7 events that matter in your studio

Pick from seven entity types: form submission, class registration, event registration, appointment booked, product purchased, customer added, lead moved. Filter to any type or specific entities — "any class" or "only Power Reformer," your call.

  • Any or specific — broad coverage or surgical targeting.
  • Lead-stage triggers for sales pipeline moves.
  • Multi-trigger automations coming together in one flow.
Trigger types7 supported
Form submitted
Contact form, lead form, intake form
Class registration
Member books a class
Appointment booked
Private, duet, semi-private
Product purchased
Membership, pack, drop-in
Customer added
New roster entry
Lead stage moved
Pipeline progression
Actions

5 actions, chained however you want

Send an email. Send an SMS. Tag the customer. Create a customer record. Update a lead's pipeline stage. Chain them together — when a lead form is submitted, send an email, tag the lead "warm," and move them to "qualified." All in one automation.

  • Multiple actions per automation in sequence.
  • Per-action timing — fire the email now, the tag in 3 days.
  • Conditional execution based on tag or attribute.
Action typesChain any
Send email
→
Send SMS
→
Assign tag
→
Create customer
→
Update lead state
→
Timing

Immediate, delayed, or relative to the event

Some actions should fire instantly (welcome emails). Some need a delay ("3 days after first class"). Some should fire relative to an event date ("2 days before the workshop," "1 week after the retreat"). All three modes are first-class.

  • Immediate — fire the moment the trigger event lands.
  • Delayed — X days after the trigger.
  • Relative to event — X days before/after the actual class or event date.
Trigger timing
Immediate
Fire instantly when triggered
Delayed
3 days after trigger
Relative to event
1 day before the class starts
Only run once
Per customer · prevents duplicate sends
Execution history

See every fire, every action

Every automation logs a row per execution. See who triggered it, what actions ran, when each landed, and whether each succeeded. If something failed, the error is right there with a re-run button — no guessing why a welcome email never arrived.

  • Per-recipient log across every action.
  • Failure reason & retry for any action.
  • Filter by automation, status, or date for audit.
Recent activity96 fires today
Welcome email · Cara Hill
Success
Just now
SMS reminder · Devon Park
Success
2m ago
Tag assigned · Lila Chen
Success
8m ago
Welcome email · Sam West
Failed · invalid email
14m ago
Lead moved · Mia Rivera
Success
24m ago
Safety nets

Validation that catches infinite loops before they ship

Zipper validates your automation graph at save time. If your "send email" action would trigger another automation that triggers your first one again, the editor flags it before you save. The "Only run once" flag prevents repeated sends for one-time moments. You can't accidentally email someone 800 times.

  • Save-time validation for circular dependencies.
  • Run-once enforcement per customer.
  • Rate limits on burst sends to protect deliverability.
ValidationIssue detected
Possible infinite loop
"Add tag VIP" would trigger "Welcome VIP" which would assign the same tag again.
Suggested fix
Enable "Only run once" on Welcome VIP — or use a different tag in the second automation.
Why Zipper

All of it. In one place. Built for studios.

Automations connect to your booking, marketing, and CRM data — so triggers fire on what's actually happening in your studio.

Reliable execution
Every fire logged, every failure surfaced, every re-run one click away.
Time-aware triggers
Fire on the trigger, X days after, or relative to the event date.
One platform, one bill
Triggers from booking, payments, CRM, and marketing — no integrations to babysit.

Common questions

What is an automation?
A trigger plus one or more actions. When something happens in your studio (a form submitted, a class booked, a lead moved to a new stage), Zipper fires the actions you configured — send an email, text, assign a tag, create a customer, advance the lead.
What can trigger an automation?
Seven trigger types: form submitted, event registration, class registration, appointment booked, product purchased, customer joined the roster, or lead moved between workflow stages. Pick "any" of a type or specific entities.
What actions can I run?
Send email, send SMS (via Twilio), assign a tag, create a customer record, or update a lead's workflow stage. Chain multiple actions — send a welcome email, tag the customer "first class booked," advance the lead to "active member."
Can actions run on a delay?
Yes. Set timing to immediate, delayed (X days after the trigger), or relative to an event date (X days before/after the class itself). Useful for "send a follow-up 3 days after the first class" or "remind 2 days before the workshop."
Can I prevent the same email from firing twice?
Yes. Toggle "Only run once" per customer — useful for welcome emails, "first class booked" celebrations, or any single-fire moment. Off by default for things like reminders that should fire every cycle.
Can I see whether automations are working?
Yes. Every automation has an execution history — every fire, every action, every recipient, success or failure. If a welcome email didn't go out, you can see why and resend.
How do I avoid creating infinite loops?
Zipper validates automation graphs at save time. If your "send email" action would trigger another automation that triggers your first one again, the editor blocks it with a clear error. You'll never accidentally email someone 800 times.
Can I trigger automations on lead-form submissions?
Yes. Pick "form submission" as the trigger and select either a specific form ("Contact Us") or any form. Combined with the run-once setting, perfect for inbound lead workflows.
Do automations work with my Zipper website?
Yes. Forms on your Zipper site (or a Zipper widget on an external site) trigger automations the same way. Submit the form → automation fires → email/SMS/tag goes out without manual processing.
Can I segment automation recipients?
Yes. Apply tag-based filters so a specific automation only fires for customers with a specific tag, membership tier, or location — useful when running locations on different schedules or message cadences.

See automations built for your studio

A 30-minute walkthrough is the fastest way to see what to put on autopilot first.

Book a Demo