Skip to main content

Reclaim 2.0 + Webhooks integration

Learn how to configure Webhooks in Reclaim 2.0 to send Scheduling Links, booking updates, and cancellation data to external systems and custom workflows.

This article refers to Reclaim 2.0 features and workflows. You can confirm your current app version in your User profile.

Connect Reclaim Webhooks to your external systems to trigger automated workflows when meetings are booked, rescheduled, or cancelled through Reclaim Scheduling Links.

With Webhooks connected, Reclaim can send Scheduling Link event data to CRMs, automation platforms, internal tools, or custom endpoints so teams can automate follow-up actions without manual updates.


How to set up Reclaim Webhooks

Webhook setup varies depending on the system receiving the data, but the Reclaim setup flow has two main parts: create a webhook endpoint, then attach it to one or more Scheduling Links.

To configure a webhook endpoint:

  1. Sign in to your Reclaim account

  2. Go to Team Settings

  3. Open Webhook Settings

  4. Click + New

  5. Enter a descriptive webhook name

  6. Add the endpoint URL that should receive webhook requests

  7. Save or generate the webhook secret

  8. Store the secret securely

To add a webhook to a Scheduling Link:

  1. Open the Scheduling Link you want to use with webhooks

  2. Edit the link settings

  3. Scroll to the webhook configuration section

  4. Add one or more webhook configurations

  5. Save the Scheduling Link

Once the webhook is attached, Reclaim can send a request when a meeting is booked, rescheduled, or cancelled through that Scheduling Link.

Note: Webhook endpoints must use https. Reclaim does not send webhook requests to localhost, localhost variants, or IP addresses such as 127.0.0.1. Webhook support is available on Business and Enterprise plans.

Developer implementation notes

Reclaim sends webhook events as POST requests with a JSON body to the endpoint configured in Team Settings.

Webhook receivers should:

  • Accept POST requests over https

  • Parse application/json request bodies

  • Respond within 10 seconds

  • Return a successful 2xx response after processing

  • Verify the webhook signature before trusting the payload

  • Handle duplicate or out-of-order events safely

Reclaim includes a signature header, x-reclaim-signature-256, which can be used with the webhook secret to verify that the request came from Reclaim.

Webhook payloads include Scheduling Link meeting details such as event type, meeting information, attendee information, organizer information, Scheduling Link metadata, and any supported custom data- parameters passed through the booking URL.

For full payload examples, signature verification code, and schema details, use the Reclaim Webhooks help documentation.


What you can do with Reclaim Webhooks

Category

Capability

Description

Example use cases

Setup

Create webhook endpoint

Configure the destination URL that receives Reclaim webhook requests.

“Send booking events to our automation endpoint.”

Setup

Attach webhook to Scheduling Link

Add a webhook configuration to one or more Scheduling Links.

“Trigger this workflow when someone books this link.”

Scheduling events

Meeting created

Send a webhook request when a new meeting is booked through a Scheduling Link.

“Create a CRM activity when a prospect books.”

Scheduling events

Meeting rescheduled

Send a webhook request when an existing Scheduling Link meeting is rescheduled.

“Update the meeting time in our CRM.”

Scheduling events

Meeting cancelled

Send a webhook request when a Scheduling Link meeting is cancelled.

“Notify the account owner when a meeting is cancelled.”

Custom workflows

Pass custom data

Include up to five data- query parameters on booking links and receive that data in the webhook payload.

“Pass campaign, source, or record IDs into the workflow.”

Security

Verify webhook signature

Use the shared secret and signature header to confirm the request came from Reclaim.

“Validate webhook authenticity before processing.”


Disconnecting or disabling webhooks

You can disable a webhook by removing it from the Scheduling Link or deleting the webhook configuration.

To stop a webhook from firing for a Scheduling Link:

  1. Sign in to Reclaim

  2. Open the relevant Scheduling Link

  3. Edit the link settings

  4. Remove the webhook configuration

  5. Save the Scheduling Link

To delete a webhook endpoint:

  1. Go to Team Settings

  2. Open Webhook Settings

  3. Select the webhook configuration

  4. Delete or remove the configuration

  5. Confirm the change

Once removed, Reclaim will no longer send Scheduling Link events to that endpoint.

Revoking endpoint access

Webhook access is controlled by the receiving system and by the webhook secret.

To revoke endpoint access:

  1. Remove the webhook from any active Scheduling Links

  2. Delete the webhook configuration in Reclaim

  3. Rotate or invalidate the secret in the receiving system

  4. Disable the endpoint if it should no longer receive requests

  5. Remove any connected automation workflows that process the webhook

Note: Existing webhook deliveries or records created in external systems may remain unless removed in those systems.

Existing calendar events created by Reclaim may remain on your calendar unless manually removed.

Did this answer your question?