Google Calendar
via OAuth 2.0 · gated on verification
Real-time free/busy sync. Auto-create the booking event on the user's calendar.
Integrations · the protocols we speak
No proprietary lock-in. iCal for calendars, HMAC-signed webhooks for automation, a single restricted Stripe key for payments. The boring choice on purpose — boring is interoperable.
via OAuth 2.0 · gated on verification
Real-time free/busy sync. Auto-create the booking event on the user's calendar.
via iCal feed URL · RFC 5545
Paste the public-feed URL from iCloud. No OAuth, no verification, no waiting on Google.
via iCal feed URL today · native OAuth in v1.1
Works at v1 via iCal feed export from Outlook Web. Native Microsoft Graph OAuth ships in v1.1.
via iCal feed URL
Anything that exports an RFC 5545 feed will work. We don't gate the calendar by brand.
via Restricted API key · BYO
Paste a restricted Stripe key. Member payments go straight to your account. We never sit in the path.
via HMAC-signed webhooks
Booking · reschedule · cancel · no-show events. Drop the URL, set the secret, done.
via HMAC-signed webhooks
Same webhook stream as Zapier. Build the scenarios you actually want.
via HMAC-signed webhooks · self-hosted ok
Self-hosted automation works the same way. The signature header is documented at /docs#webhooks.
via <script> embed · under 12 KB
One script tag. Inherits your Webflow typography. No iframe ceremony.
via <script> embed · under 12 KB
Code-component-friendly. Drop it into any Framer page; styles cascade from your design system.
via <script> embed
Same script tag works in any page builder that allows raw HTML embeds.
Slotsy doesn't keep an integration catalog the way some tools do — there's no "Zapier required" tier, no per-integration fees. If your tool exports an iCal feed or has a webhook endpoint, the wire is already in place.
Ask about a specific tool