wiki/knowledge/integrations/lamarie-zapier-square-appointments.md Layer 2 article 846 words Updated: 2025-10-14
↓ MD ↓ PDF
client/la-marie-beauty project/bookly-integration square zapier integrations troubleshooting

LaMarie Beauty — Zapier-Square Appointment Sync Troubleshooting

Overview

During the October 14, 2025 progress call, Chris Ostergaard reported that the Zapier integration for creating Square appointments was not working consistently. Despite having valid team member IDs provided by the client, the Zap fails when attempting to create appointments — likely due to a mismatch between the selected team member ID and the test environment being used. The core blocker is that Chris lacks a personal Square team member identity to simulate a real booking environment.

See also: [1] and the broader [2] project.


Problem Description

The Zapier "Create Square Appointment" action is returning failures during testing. Symptoms and suspected causes:

"I think it's because the service I'm selecting, the team ID that I'm selecting, because I'm trying to sync it to my calendar, and because I don't really have a team member ID, the links, it kind of messes up there." — Chris Ostergaard


Root Cause Analysis

Factor Status
Team member IDs from client ✅ Valid and usable
Zapier Square integration enabled ✅ Confirmed
Chris has Square account/access ❌ Missing — blocked testing
Appointment creation API call succeeds ❌ Failing
Square Support contacted ✅ Done — bounced to Zapier/Bookly

The inability to simulate a real team member environment is the primary blocker. Without a personal Square team member record, Chris cannot confirm whether failures are due to the API call structure, timestamp formatting, or a permissions/identity issue.


Resolution Steps

Immediate: Grant Chris Square Team Member Access

Follow-up: Provide Service IDs and Variation IDs

Ongoing: Escalate to Zapier / Square if Needed


Square Environment Notes

La Marie Beauty has two locations configured in Square:

Location Status Usage
Madison Active All regular team member transactions
Milwaukee Inactive (legacy) New purchase links only — no team member transactions route through here

The Milwaukee location is a legacy artifact and does not affect team member appointment flows. This was confirmed by Katie on the call and is not a factor in the Zapier sync failures.


Key Decisions


This integration blocker is one of two major blockers on the Bookly launch. The other is the product page layout work required to support service variations — see [3] for that thread.

Until both are resolved, the team agreed to implement a temporary redirect: the "Book Now" button on the website will point directly to the full Square booking page, bypassing the partially-built Bookly widget. This reduces client-facing friction in the interim.


Participants (This Call)

Name Role
Chris Ostergaard Asymmetric — integration developer
Melissa Cusumano Asymmetric — project lead
Mark Hope Asymmetric
Katie Schueller La Marie Beauty — client contact, Square admin
Lisa Frommelt La Marie Beauty
Roxana Lopez La Marie Beauty — raised UX/mobile booking concern