Square Appointments
Your receptionist can find a caller in Square or add them as a customer, then create an appointment in Square Appointments for a time the caller asks for. Square’s booking API expects nested objects that webhook tools can’t send, and Square’s MCP server requires an OAuth sign-in, so Reception connects through Zapier.
Zapier’s Square app can’t check open times, so your receptionist can’t offer free slots or tell whether a time is taken. For real-time booking, use Reception’s own booking with Google Calendar, Calendly, or Cal.com.
Set up
Add the Square actions
In your Zapier MCP server at mcp.zapier.com, add the actions below and sign in to Square when Zapier asks. For each field, either set a fixed value or let the AI fill it in, as listed.
Assign the tools
In Reception.ai, open the Zapier integration’s Tools tab, select Refresh tools, and assign each action to the Client (receptionist).
Test it
Test your receptionist as a new caller who asks for an appointment. The customer and the appointment appear in Square.
Actions
Find the caller
Add a new caller
Create an appointment
If you offer several services, also add Find Service with Location set to a fixed value, and let the AI fill in Appointment Service ID from its result.
Add a procedure for bookings: find or add the caller, agree on a time, read the date and time back, then create the appointment.
Limitations
- Your receptionist can’t check availability. It books the time the caller asks for without seeing your calendar.
- With Team Member ID fixed, every appointment goes to the same team member. Your receptionist can’t choose between staff.
- Your receptionist can’t reschedule or cancel appointments.
- Each action your receptionist runs uses tasks from your Zapier plan. Zapier currently counts two tasks per successful call; failed calls aren’t counted. When the plan runs out, the actions stop until it resets.