Create a record in Airtable when a new booking in Square

What each client fills in

Airtable: Base ID

From the base’s URL: airtable.com/appXXXX/…

Airtable: Table

For example Leads

The accounts it needs

Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.

• Square

  developer.squareup.com → the client’s application (their own account) → Credentials → Production access token. A personal access token for the client’s own account needs no Square review.

• Airtable

  airtable.com/create/tokens → Create token → scopes data.records:write and data.records:read (lookups and the triggers) → add the client’s base → copy the token.

After you install it

It lands switched off. The client’s checklist holds exactly this:

1. Connect the client’s Square, for “A new booking”
2. Connect the client’s Airtable, for “Create a record”
3. Fill in Airtable: Base ID (From the base’s URL: airtable.com/appXXXX/…)
4. Fill in Airtable: Table (For example Leads)
5. Confirm with the client: The client is on Square Appointments Plus or Premium. On the free Appointments plan, bookings made in Square’s own dashboard or booking site send no event: only bookings made through the API do.
6. Match Airtable’s fields to the client’s own: Starts, Status, Customer ID, Customers note