Skip to main content

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.

1. Decide the route
2. In StoryProof
3. In Zapier
4. Prove it with your own booking

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.

  • 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.

  • 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.

  • Problem 4

    Clients never open the first email

    One unanswered message and the moment is gone, unless somebody remembers to chase it by hand.

  • 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.

Three ways to get an Acuity appointment into StoryProof

Acuity details from its developer documentation and Zapier details from Zapier’s help center and integration page, read on 2026-11-18.
RouteCarries the client email?Good for
Acuity native webhook straight to StoryProofNo, only IDs as form dataNot enough on its own for a review request
Zapier: Appointment Start, then Webhooks by Zapier POSTYes, you map itMost practices, no code
Native webhook to your own script, which calls Acuity’s API and then StoryProofYes, after the lookupTeams with a developer who already uses the Acuity API

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.

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

  1. Webhooks, Acuity Scheduling Developers. Checked 2026-11-18.
  2. Acuity Scheduling integrations, Zapier. Checked 2026-11-18.
  3. Send webhooks in Zaps, Zapier Help Center. Checked 2026-11-18.

Last updated 2026-11-18.