What exactly triggers the Vagaro integration?
Vagaro appointment.updated with the appointment status Service Completed.
Vagaro direct integration
Send Google review follow-up after a completed Vagaro service.
Turn a completed Vagaro service into an eligible review-request handoff without retyping the customer. This is a signed provider webhook with explicit setup and testing, not a one-click marketplace install.
Vagaro businesses that mark appointments Service Completed and have the API and webhook access required for a read-only customer lookup.
Exact accepted Vagaro trigger
Vagaro must show that the visit is complete
ReviewsRelay accepts only an appointment update whose bookingStatus is exactly Service Completed. Scheduled, checked-in, canceled, no-show, and other appointment states never become review-request handoffs.
Vagaro direct uses a signed webhook plus a read-only customer lookup. It is not a password-based login or a universal one-click install: the business needs Vagaro API access, webhook access, a client ID, client secret, and the correct API region.
Required customer handoff
- A stable Vagaro appointment event ID
- The completed appointment status
- A customer record with name and email
- The completed appointment timestamp
Automatically ignored
- Appointments not marked Service Completed
- Duplicate event IDs
- Customers without a usable email address
- Opted-out contacts
- Customers contacted within the previous 90 days
Provider-specific setup
Connect Vagaro, prove one event, then enable live intake
- Create the Vagaro direct connection
Save the signing secret, client ID, client secret, and API region in the private ReviewsRelay setup.
- Register the appointment webhook
Add the private ReviewsRelay URL to the Vagaro webhook configuration for appointment updates.
- Complete one controlled appointment
Use a customer record and email address you control, then move the appointment to Service Completed in Vagaro.
- Verify lookup and queue behavior
Confirm that ReviewsRelay verifies the signature, retrieves the customer, records the service and business location, and accepts the event only once.
Go-live checks
Confirm the provider evidence, customer data, and duplicate behavior
- The payload identifies appointment.updated
- bookingStatus is Service Completed
- The business ID and customer ID are present
- The read-only customer lookup returns a valid name and email
- A duplicate appointment update remains suppressed
Operational controls
- Signed webhook verification is required
- Read-only customer lookup uses the configured Vagaro client credentials and region
- Only the completed service state enters the request queue
- The connection can be tested, paused, rotated, or disconnected in ReviewsRelay
Vagaro Webhooks documentation is the official provider source for the webhook contract.
- Compare all connection pathsDirect providers, Zapier, Make, secure webhooks, CSV, and manual entry
- Preview the downstream workflowSee what happens after an eligible customer reaches ReviewsRelay
Practical outcomes
- Trigger from Service Completed
- Resolve the Vagaro customer and service
- Keep other appointment states out
- Verify the region and lookup before launch
Workflow
- Create the Vagaro direct connection
- Register the appointment webhook
- Complete one controlled appointment
- Verify lookup and queue behavior
Safety guardrails
- Signed webhook verification before payload processing
- Appointments not marked Service Completed
- Duplicate event IDs
- Customers without a usable email address
- Opted-out contacts
Frequently asked questions
What customer data does ReviewsRelay need from Vagaro?
A stable Vagaro appointment event ID. The completed appointment status. A customer record with name and email. The completed appointment timestamp.
Which Vagaro events are ignored?
Appointments not marked Service Completed. Duplicate event IDs. Customers without a usable email address. Opted-out contacts. Customers contacted within the previous 90 days.
Is the Vagaro connection a one-click install?
Vagaro direct uses a signed webhook plus a read-only customer lookup. It is not a password-based login or a universal one-click install: the business needs Vagaro API access, webhook access, a client ID, client secret, and the correct API region.
Can I test the Vagaro connection before enabling it?
Yes. Use contact details you control and verify these checks: The payload identifies appointment.updated; bookingStatus is Service Completed; The business ID and customer ID are present; The read-only customer lookup returns a valid name and email; A duplicate appointment update remains suppressed.
Does ReviewsRelay need my Vagaro password?
No. ReviewsRelay never asks for your Vagaro sign-in password. The direct connection uses a private signed webhook and the minimum configured credentials needed for customer lookup.
Related review automation pages
- IntegrationsReview request automation
- SquareSquare Google review request automation
- MindbodyMindbody Google review request automation
- SafetySafe Google review automation
- Free toolsFree Google review tools
- Profile auditGoogle Business Profile audit tool