Booking HandbookAcuity Scheduling integrations
Connect Salesforce through Zapier, take payments with Square, or use an API for a custom connection. Start by choosing what information needs to move and which system should own it.
Choose the connection for the job
Accept a payment
Connect a supported processor to the booking flow. Check deposits, later balances and refunds.
See the Square connectionUpdate another system
A connector or custom integration moves booking information. Define the destination record and what should happen after a change.
See CRM and automation optionsAcuity Scheduling and Salesforce
Acuity lists Zapier as a way to connect to Salesforce. This uses a separate automation service; confirm the required Salesforce action, account access and Zapier plan before committing.
Acuity’s CRM connection options- Name the record to update
For example, decide whether a new booking should create a lead or update an existing contact. Agree how the automation will find the same person next time.
- Map a small set of fields
Choose only the booking information the destination needs. Include a stable appointment reference so a later reschedule can be matched.
- Test changes as well as new bookings
Use made-up data. Rebook, reschedule and cancel, then check for duplicate contacts, stale times and missing updates before enabling the workflow.
Zapier limits and support
Acuity documents up to 25 zaps per contributor, counted towards its webhook limit. Acuity support covers connecting the account; Zapier supports building and running the automation. Budget for any separate subscriptions.
Read Acuity’s Zapier setup guideAcuity Scheduling and Square payments
Square is a supported Acuity payment processor for booking payments, deposits and later balances. This connection does not by itself establish that bookings will synchronize with a separate Square Appointments calendar.
Choose the processor before building the checkout flow. Acuity does not allow Stripe and Square to be connected at the same time; it does allow PayPal alongside either one.
Compare Acuity payment processorsWhat should I check with a deposit?
Use an example $100 service with a $20 deposit. Before collecting the remaining $80, check which appointment the deposit belongs to and where the final payment is recorded. Repeat after a reschedule and a refund. These amounts are only a rehearsal example.
Connect an outside calendar
Acuity supports connections to Google, iCloud and online Outlook calendars. Check two jobs separately: showing appointments outside Acuity, and using outside busy time to block new bookings.
During setup, add an outside meeting and attempt to book the same time. Then reschedule from Acuity and inspect the external event. Account permissions, calendar selection and update delays all matter.
Read Acuity’s calendar-sync instructionsWork through calendar conflictsAcuity APIs, webhooks and custom connectors
Webhooks send an event
Acuity documents webhooks on every plan, with up to 25 per contributor. Your receiving service still needs to process the event and handle failures.
APIs perform a request
Acuity lists API access on Premium or the legacy Powerhouse plan. A developer can connect your software; a working integration also needs monitoring and maintenance.
What if the connector I need is not listed?
Ask for its exact supported actions, fields, plan requirements and support owner. A name in an app directory does not establish how it handles cancellations, retries or matching existing records. If a capability remains unclear, request a demonstration before choosing that route.
Before you rely on the connection
- Book and match
Make one test appointment and find the corresponding record in every connected system.
- Change and repeat
Reschedule and cancel. Retry an interrupted handoff and check that it does not create a second booking or payment.
- Give someone the recovery job
Decide who checks failures, how they spot stale records, and how the team keeps booking if a connection stops.
What if the booking rules still do not fit?
If a must-have workflow cannot be configured or connected reliably, write down the gap before commissioning a build. Include who will handle maintenance, payments and recovery.