- Integrations
- /
- Acuity Scheduling
- /
- with Stripe
Connect Acuity Scheduling to Stripe in two minutes.
Real-time triggers from Acuity Scheduling, ready-made actions in Stripe. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Acuity Scheduling.
- Appointment CanceledWebhook
- Appointment CompletedWebhook
- Appointment RescheduledWebhook
- Appointment ScheduledWebhook
Workflows do something in Stripe, instantly.
- Cancel SubscriptionAPI
- Create ChargeAPI
- Create Checkout SessionAPI
- Create CouponAPI
- Create CustomerAPI
- Create Payment IntentAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Acuity Scheduling, do it in Stripe.
4 Acuity Scheduling triggers wired to 31 Stripe actions. Most-used pairing: Appointment Canceled → Cancel Subscription.
Or fire it the other way around.
10 Stripe triggers wired to 3 Acuity Scheduling actions downstream.
See Stripe → Acuity Scheduling →Common Acuity Scheduling → Stripe workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires the instant an appointment is canceled — by the client (via the rescheduling/cancel link), by the practitioner (via Acuity admin), or via API. Payload includes the appointment, client, and (for client-initiated) the cancellation reason if a reason field was configured. The hook for "free up the slot, notify the waitlist, refund deposit" workflows.
Fires the instant an appointment is canceled — by the client (via the rescheduling/cancel link), by the practitioner (via Acuity admin), or via API. Payload includes the appointment, client, and (for client-initiated) the cancellation reason if a reason field was configured. The hook for "free up the slot, notify the waitlist, refund deposit" workflows.
Fires the instant an appointment is canceled — by the client (via the rescheduling/cancel link), by the practitioner (via Acuity admin), or via API. Payload includes the appointment, client, and (for client-initiated) the cancellation reason if a reason field was configured. The hook for "free up the slot, notify the waitlist, refund deposit" workflows.
Fires the instant an appointment is canceled — by the client (via the rescheduling/cancel link), by the practitioner (via Acuity admin), or via API. Payload includes the appointment, client, and (for client-initiated) the cancellation reason if a reason field was configured. The hook for "free up the slot, notify the waitlist, refund deposit" workflows.
Fires when an appointment time has passed without cancellation — Acuity considers it completed. The right trigger for post-appointment follow-up workflows (thank-you email, review request, next-appointment booking nudge). Fires once per appointment, even for recurring series (each instance fires separately).
Fires when an appointment time has passed without cancellation — Acuity considers it completed. The right trigger for post-appointment follow-up workflows (thank-you email, review request, next-appointment booking nudge). Fires once per appointment, even for recurring series (each instance fires separately).
Fires when an appointment time has passed without cancellation — Acuity considers it completed. The right trigger for post-appointment follow-up workflows (thank-you email, review request, next-appointment booking nudge). Fires once per appointment, even for recurring series (each instance fires separately).
Fires when an appointment time has passed without cancellation — Acuity considers it completed. The right trigger for post-appointment follow-up workflows (thank-you email, review request, next-appointment booking nudge). Fires once per appointment, even for recurring series (each instance fires separately).
Fires when an appointment is moved to a different time — payload includes both the original time and the new time, plus client and appointment metadata. Useful for cascading workflows that need to update downstream calendars, reminder schedules, or capacity counts when timing changes.
Connect Acuity Scheduling and Stripe in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Acuity Scheduling and Stripe
Open Tiny Command, authorize Acuity Scheduling and Stripe once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Acuity Scheduling trigger
Drop the Acuity Scheduling → Appointment Canceled trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/acuity-scheduling.trigger-appointment-canceled - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Stripe action
Drop the Stripe → Cancel Subscription action below it. Map fields from the Acuity Scheduling payload into the Stripe inputs.
stripe.cancel-subscription - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Acuity Scheduling + Stripe.
How long does it take to connect Acuity Scheduling and Stripe on Tiny Command?
Is the Acuity Scheduling ↔ Stripe integration real-time?
Can I filter or transform data between Acuity Scheduling and Stripe?
What Acuity Scheduling events can trigger a Stripe workflow?
Do I need a paid plan to use Acuity Scheduling with Stripe?
What if I want Stripe → Acuity Scheduling instead?
Other apps that pair well with Acuity Scheduling.
Wire Acuity Scheduling to Stripe in 2 minutes.
Free tier available. No credit card. No onboarding call.