Calendly

The Calendly integration sends a waiver signing email to your client automatically when they book through Calendly. You connect once, map your event types to waivers, and every new booking triggers an email without any manual step.

Plan requirement: Starter or above.

Enabling the integration

1. In your WaiverChaser dashboard, go to Settings > Account
2. In the Integrations card, toggle Calendly on

This makes the Calendly page available in your sidebar.

Connecting your account

1. Go to Settings > Calendly in the sidebar
2. Click Connect Calendly
3. You'll be redirected to Calendly to authorize the connection
4. Approve the requested permissions and you'll be sent back to WaiverChaser

The connection uses OAuth 2, so WaiverChaser never stores your Calendly password. You can disconnect at any time from the Calendly page in your dashboard.

Once connected, the page shows your Calendly account name, connection status, and when the last booking event was received.

Mapping event types to waivers

After connecting, your Calendly event types appear in the Event type mappings section. Each mapping tells WaiverChaser which waiver to send when someone books that type of appointment.

To create a mapping:

1. Click Add mapping
2. Select a Calendly event type from the dropdown
3. Select the waiver to send
4. Optionally select a location (controls which branding appears in the email)
5. Click Save mapping

You can create one mapping per event type. If you have multiple event types (e.g., "Personal Training Session" and "Trial Class"), each can map to a different waiver.

To remove a mapping, click the trash icon next to it. Removing a mapping stops automatic emails for that event type. It doesn't affect waivers that have already been sent or signed.

What happens when a client books

When someone books through a mapped Calendly event type:

1. Calendly sends a webhook to WaiverChaser immediately
2. WaiverChaser looks up the mapping for that event type
3. If a mapping exists, WaiverChaser sends the waiver to the client's email
4. The client opens the email, taps the link, and signs on their phone or computer
5. The signed record appears in your Signatures page like any other

If no mapping exists for the event type, no email is sent.

Duplicate prevention

WaiverChaser checks before sending:

• If the client already has a completed signature for that waiver, no email goes out
• If the client already has a pending signing request for that waiver, WaiverChaser resends the existing link instead of creating a new one

This means clients who book multiple appointments won't get repeated waiver emails after they've already signed.

Connection status

The Calendly page shows the current connection status:

• Connected (green): the integration is active and processing bookings
• Error (red): something went wrong, usually a token refresh failure. Try disconnecting and reconnecting. If the error persists, contact support.

The Last event timestamp shows when the most recent booking webhook was received, so you can confirm bookings are flowing through.

Disconnecting

Click Disconnect on the Calendly page to remove the integration. This:

• Removes the webhook subscription from Calendly (no more events sent)
• Deletes your stored Calendly credentials from WaiverChaser
• Leaves all existing signed waivers and pending requests in place

You can reconnect at any time by going through the authorization flow again.

Calendly vs. the Zapier approach

The Zapier integration also supports a Calendly-to-WaiverChaser workflow using the "New Event" trigger and "Send Signing Request" action. Both approaches work, but they differ:

	Native Calendly	Zapier
Setup	Connect + map event types	Create a Zap with trigger and action
Duplicate prevention	Built in	Requires a search step in the Zap
Extra account needed	No	Yes (Zapier account)
Extra cost	No	Depends on Zapier plan
Event type mapping	Per-event-type waiver selection	One Zap per event type, or conditional logic

For most users, the native integration is the simpler option.