Dhairyashil Shinde
26b4385679
* feat: ooo message on booking page * make ooo days selectable even when no redirect booking * handle long notes * remove unused i18n key * Private notes stay private on the server, No accidental data leaks through client-side payloads * address cubics comments * fix: replace toggle with checkbox for OOO note visibility - Replace Switch with Checkbox for "show note publicly" option - Remove "OOO Message:" prefix from displayed notes on booking page - Update i18n text to "Show note on public booking page" - Remove unused ooo_message i18n key * fix the accessibility issue by using proper htmlFor and id association * only allow selecting OOO dates when the note is public
Zapier Integration – Developer Guide
Note: This is a redirect app. End users should connect Cal.com to Zapier directly via the Zapier Integrations page: https://zapier.com/apps/calcom/integrations
The Zapier app in Cal.com now functions as a redirect app that takes users directly to Zapier's integration page. No local setup or OAuth configuration is required.
How It Works
- User clicks "Visit" → Opens Zapier integrations page
- User sets up automation → Directly on Zapier's platform
- No Cal.com credentials needed → Users authenticate directly with Zapier
For Developers
This app uses the link-as-an-app template and requires no additional configuration beyond the redirect URL.
Legacy API Endpoints
The following API endpoints are maintained for backward compatibility with existing Zapier integrations:
GET /api/integrations/zapier/listBookings- List user bookingsGET /api/integrations/zapier/listOOOEntries- List out-of-office entriesPOST /api/integrations/zapier/addSubscription- Subscribe to webhooksDELETE /api/integrations/zapier/deleteSubscription- Unsubscribe from webhooksGET /api/integrations/zapier/me- Get user/team information
Note: These endpoints support both API key and OAuth authentication for existing integrations. The endpoints are dynamically routed through /api/integrations/[...args].ts.