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:
- Symptom: Zapier test calls to Square's appointment API do not return a positive response.
- Suspected cause: The team member ID being passed in the Zap does not correspond to a real, calendar-linked identity in the test context. Chris is attempting to sync appointments to his own calendar but has no Square team member record, causing a mismatch at the timestamp/team-member validation step.
- What works: The list of team member IDs provided by Katie (the client) is valid and can be queried from the database. The IDs themselves are not the issue.
- What fails: Linking a service + team member ID + timestamp into a successful appointment creation call.
"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
- Action owner: Katie Schueller (client)
- Access level: Normal team member (not developer/admin access)
- Purpose: Allows Chris to have a real team member ID in Square, enabling him to test the full Zapier → Square appointment creation flow against his own calendar entry
- Status: Katie confirmed she would add Chris on the day of the call (2025-10-14)
Follow-up: Provide Service IDs and Variation IDs
- Action owner: Katie Schueller
- Deliverable: Add a column to the existing shared spreadsheet with all Square service IDs, service names, and any variation IDs
- Purpose: Chris needs these to correctly map WooCommerce/Bookly service selections to Square appointment types in the Zap
- Status: Agreed on call; Katie to complete
Ongoing: Escalate to Zapier / Square if Needed
- Chris has already contacted Square Support; they redirected him to Zapier and Bookly
- Next step if personal access doesn't resolve the issue: contact Zapier support, then return to Square with evidence that the failure is on their end
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
- Chris will be added as a normal team member in Square (not developer access) to enable realistic environment testing
- Service IDs and variation IDs will be added to the shared client spreadsheet for Zap mapping
- If Square access does not resolve the issue, escalation path is: Zapier support → Square support (with evidence)
Related Issues
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 |