Acuity Scheduling to StoryProof
Acuity Scheduling Review Request Automation
Acuity can tell another tool when someone books, but its own webhook only sends ID numbers, not the client’s email address. This guide routes each appointment through Zapier, which can read the client details, into a StoryProof automation, available from Pro, that waits until the session is over and then emails the review request.
- Why Acuity’s own webhook is not enough on its own
- Zapier’s Appointment Start trigger as the hand-off
- A test booking under your own email address
Setup checklist
From a booked session to one review request
Tick each item as you go. The Zapier parts come from Zapier’s and Acuity’s own documentation; the StoryProof parts stay inside what the automation builder is described as doing.
Ticks stay in your browser. Nothing is sent anywhere.
The problem, solved
What gets in the way after an Acuity session
Each fix stays inside what StoryProof automations are described as doing.
- Problem 1
Acuity’s webhook has no email in it
Point the native webhook straight at a review tool and it receives an appointment number, nothing it can send an email to.
How StoryProof solves it
Let Zapier or your own script add the client details, then call the automation’s own URL. From Pro, every automation gets one, and a Zapier step can start review requests from it.
- Problem 2
The request lands before the session ends
A trigger that fires near the start time would ask for feedback while the client is still in the chair.
How StoryProof solves it
Put a wait step between the trigger and the request. Waits run from minutes to weeks, or until a set weekday and time.
- Problem 3
Weekly clients get asked every week
Recurring appointments each fire the Zap, so a regular client could receive the same ask again and again.
How StoryProof solves it
Use a review request step that skips anyone who has already reviewed or was asked recently.
- Problem 4
Clients never open the first email
One unanswered message and the moment is gone, unless somebody remembers to chase it by hand.
How StoryProof solves it
A second automation can start when a request gets no response after the number of days you choose, and send one gentle reminder.
- Problem 5
We cannot tell if the Zap reached StoryProof
Zapier says the step succeeded, the client says nothing arrived, and nobody knows where it stopped.
How StoryProof solves it
Automation logs list every webhook that arrived and every step that ran, with the reason a run ended, for 30 days.
Three ways to get an Acuity appointment into StoryProof
In StoryProof
The order to build it in
Step 1 of 4
Create the StoryProof automation first
Start it from an inbound webhook, add a wait and a review request step, and leave it unpublished. Copy the URL and token.
Step 2 of 4
Build the Zap
Acuity Scheduling Appointment Start as the trigger, then a Webhooks by Zapier POST to the copied URL with the email and first name mapped.
Step 3 of 4
Book yourself and read the sample
Make a test booking with your own address, send the Zap, and check in StoryProof which fields were picked as email and name.
Step 4 of 4
Run one live test and publish
A test runs every step for real, so run it on your own contact, read the log, then publish and switch the Zap on.
Before you start
Where this setup stops
No Acuity integration in StoryProof
Nothing here is a built-in Acuity connection. The link is a webhook URL that Zapier, or your own code, calls.
Email only
StoryProof sends review requests by email and does not send SMS, so clients booked with a phone number alone are not reached.
Cancellations need checking
Zapier does not say whether a cancelled appointment still fires Appointment Start. Test it with a booking you cancel before relying on it.
Field names come from your sample
This page does not list what the payload must contain. The sample event you paste in StoryProof shows what it picked up.
Written from the vendors’ docs
The Acuity and Zapier steps follow their documentation as of 2026-11-18 and were not clicked through in a live account.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can I paste StoryProof’s URL into Acuity’s own webhook settings?
You can, but Acuity documents that its webhook sends only IDs, so StoryProof would have no email to send the request to. Put Zapier or a small script in between.
Why Appointment Start rather than New Appointment?
New Appointment fires at booking, which can be weeks early. Appointment Start fires close to the session, so a short wait in StoryProof is enough to land the request just after it.
Can different appointment types get different emails?
Possibly. Send the appointment type in the Zap, then check whether the automation builder offers it as a condition. Conditions allow up to eight named branches, each with its own email.
Will a test send a real email?
Yes. Running a test runs every step for real, so test with a booking and contact that use your own address.
Still have a question? Ask the StoryProof team or book a demo.
Ask every Acuity client after their session
Build the automation, connect it through Zapier and let review requests follow each appointment.
Sources
- Webhooks, Acuity Scheduling Developers. Checked 2026-11-18.
- Acuity Scheduling integrations, Zapier. Checked 2026-11-18.
- Send webhooks in Zaps, Zapier Help Center. Checked 2026-11-18.
Last updated 2026-11-18.