Prerequisites
GHL Calendar created
Example baseline settings:
Slot interval: 30 minutes
Duration: 30 minutes
Seats per class: 10
Working SYNX integration with Mariana Tek and GHL connected.
You can use one “catch-all” calendar for everything or separate calendars per class type. The method below works either way.
Part 1 — Build the Booking Workflow in GHL
1) Create the workflow
Go to Automations → Create Workflow → Start from Scratch.
2) Add the trigger
Trigger:
SYNX → Reservation Created
(often shown as “Empty Reservation Created”).Filters: Optional. You can filter by Membership, Tags, or Home Location ID, but a catch-all is simplest to start.
3) Update/Create the contact
Action: Create Contact (recommended over “Find Contact” to avoid branching clutter).
Map fields from the trigger payload (SYNX → Reservation Created):
Full Name
Email
Phone
Next Class (custom field, optional)
Class Payment Name (membership or credit)
Add two mappings so one always resolves:
Membership Name
Credit Name
(Only one can be true; the other stays empty.)
Credits Remaining (if available)
Credit Expiration Date (if available)
Why these fields? They power upsells and timing logic—for example, 1 credit left + expires in 7 days → trigger membership upgrade offers.
4) Book the appointment in GHL
Action: Book Appointment
Calendar: Your bookings (or catch-all) calendar
Start time: Dynamic →
SYNX → Reservation Created → Class Session Start Date
(or “Start Date” + “Start Time” concatenation)Team Member: As needed
Force book switch: ON
Force Book = Guaranteed Write. Even if the class is an hour and your calendar uses 30-minute slots, or the class is over capacity (e.g., 40 people into a 10-seat class), GHL will still record the reservation. This prevents classic API “slot unavailable” errors.
5) (Optional) Tag for downstream logic
Action: Add Tag
Examples:
First Reservation
Reservation via Membership
Reservation via Credit
SYNX • Reservation Created
(dynamic system tag)
Publish the workflow.
Part 2 — Test the Flow
In Mariana Tek, create a test reservation (e.g., Abraham Lincoln → class 11:00–12:00).
In GHL → Contacts, confirm:
Appointment is created for the correct date/time
Fields like Class Payment Name, Credits Remaining, Credit Expiration Date are populated when applicable
Tags (e.g., First Reservation) are applied
In GHL → Automations, verify the run shows Create Contact → Book Appointment succeeded.
Part 3 — Build Follow-Ups & Segmentation
A) First-reservation journeys
New workflow:
Trigger:
Appointment Status → Confirmed
And filter: Has Tag =
First Reservation
Actions: onboarding SMS/email, pre-class instructions, new-member nurture, etc.
B) Branch by class or level (If/Else)
If/Else on
SYNX → Reservation Created → Class Name
(or Class Session ID):“Hot Yoga” → Path A
“Pilates” → Path B
Or category buckets using “Contains any of”:
Beginner: “Beginner, Youth, First Timer, Intro”
Pro: “Pro, Advanced, Experienced”
Route each branch to unique reminders, coach notes, or post-class offers.
Tips & Best Practices
Keep one calendar as a “catch-all” when starting. It simplifies reporting/automations keyed to Appointment Start Date/Time, show/no-show, reviews, etc.
Don’t over-branch early. Use dynamic fields + tags to stay flexible.
Credits strategy: Use Credits Remaining + Credit Expiration Date to trigger:
Refill nudges (e.g., ≤2 credits left)
Membership upsell when usage is high or expiry is near
Troubleshooting
Reservation didn’t trigger anything in GHL
Common cause: the trigger was added before SYNX was fully connected.
Fix: Edit the workflow → Delete the SYNX trigger → Re-add
Reservation Created
→ Save/Publish → retest.
Fields are blank
Some values (e.g., Credits Remaining) only populate when applicable. That’s normal.
Monitoring: SYNX Activity Log
Use SYNX → Activity Log to audit events:
Filter by Status (Finished / Failed / Pending)
Search by Client Name
See payload details for verification and debugging
You’re Done!
With Force Book + smart field mapping, your class bookings will reliably write to GHL and feed powerful automations—without micromanaging calendar rules.