---
title: Zapier Integration Failure — Bookly to Square
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2025-11-04-la-marie-beauty-project-call-99122506.md
tags:
- integrations
- zapier
- bookly
- square
- booking-system
- failure-analysis
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Zapier Integration Failure — Bookly to Square

## Overview

During technical investigation for the [[wiki/clients/la-marie-beauty/_index|La Marie Beauty]] booking system project, the Zapier-based integration between Bookly and Square was found to be unworkable. The data Zapier pulls from Square does not match what Square requires to create an appointment, making the integration path a dead end in its current form.

This failure was a primary driver of the architectural review that followed, and ultimately prompted a go/no-go decision on Bookly itself.

## What Failed and Why

Zapier's Square connector pulls data from Square, but the fields it surfaces do not align with what Square's Appointments API requires to write a booking back:

- **Availability data is incorrect** — the availability Zapier retrieves does not reflect actual bookable slots in Square.
- **Product/service IDs are wrong or missing** — some IDs returned by Zapier are not identifiable or do not match the IDs Square expects when creating an appointment.
- **Round-trip data mismatch** — in effect, Zapier reads from Square but cannot write back to it in a way Square will accept. The data pulled out is not the data needed to push in.

> *"The data that Zapier pulls from Square doesn't necessarily seem to match what we need to create an appointment in Square, which is weird. So the data it pulls from Square doesn't match what is required in Square."*
> — Chris Ostergaard, integration specialist

The investigation also surfaced that resolving this would likely require direct API/webhook work beyond standard Zapier configuration — a scope and skill-set mismatch for the integration role on this project.

## Contributing Factors

- **Bookly cannot capture card details without an immediate charge.** Working around this requires tokenization and custom WordPress backend scripting — not a native Bookly capability and not achievable through Zapier.
- **No native Square ↔ Bookly connector exists.** Zapier was the attempted bridge, but it is not fit for purpose here. Square is an established platform; the absence of a reliable connector suggests this combination is genuinely unsupported, not merely undiscovered.
- **AI-assisted field ID matching was attempted** as a workaround for the ID mismatch problem. This raised additional reliability concerns and is not a production-safe approach.

## Architectural Implication

The failure of this integration path exposed a broader problem: the proposed architecture involved five systems — Square, Bookly, Zapier, WooCommerce, and Google Calendar — with circular dependencies and no clear single source of truth.

The core principle established during review: **Square must remain the single source of truth** for inventory, payments, staff schedules, and availability. Any integration architecture that requires Zapier to mediate between Bookly and Square introduces unacceptable risk to in-store appointment operations.

See [[wiki/knowledge/integrations/overengineered-booking-architecture|Over-Engineered Booking Architecture Risk]] for the broader architectural analysis.

## Alternative Path Under Investigation

The WooCommerce route — **Bookly → WooCommerce → Square** — was identified as a potential alternative. WooCommerce already has a working native connection to Square for products (no Zapier involved). The open question is whether Bookly can reliably hand off scheduling data to WooCommerce for checkout, without requiring Zapier as an intermediary.

This path was assigned for further investigation. See [[wiki/clients/la-marie-beauty/booking-system-technical-review|La Marie Beauty — Booking System Technical Review]] for action items and owners.

## Generalizable Lesson

Zapier's read and write field sets for a given platform are not always symmetric. A connector that can successfully *trigger* on Square events may not expose the correct fields to *create* records in Square. Before committing to a Zapier-mediated integration between two platforms, validate both directions of data flow against the target platform's write API requirements — not just the fields Zapier surfaces in its UI.

## Related

- [[wiki/clients/la-marie-beauty/booking-system-technical-review|La Marie Beauty — Booking System Technical Review]]
- [[wiki/clients/la-marie-beauty/_index|La Marie Beauty Client Index]]
- [[wiki/knowledge/integrations/overengineered-booking-architecture|Over-Engineered Booking Architecture Risk]]
- [[wiki/knowledge/scope/service-variants-scope-creep|Service Variants as a Scope Creep Vector]]