Connect Any Scheduler (Webhook Bridge)
Connect Any Scheduler (Webhook Bridge)
If you do not use a native FullSlot integration yet, you can still connect your existing scheduler with the Webhook Bridge. Most businesses use Zapier, Make, or another webhook tool to do this. Setup usually takes about 5 minutes.
Step 1: Generate your Webhook Bridge URL
Go to Integrations → Other Schedulers and click Set up Other Schedulers. Copy the URL and Secret.Step 2: Build the workflow
Use your automation tool of choice.- Trigger: `Appointment Canceled` (or the closest cancellation event your scheduler exposes)
- Action: send a `POST` request to your FullSlot Webhook Bridge URL
Many teams use `Zapier` or `Make`, but any tool that can send a signed webhook request will work.
If your scheduler does not expose a direct `Appointment Canceled` event, use the closest equivalent event that fires when a booking is canceled or removed.
Step 3: Map fields to FullSlot
Build this JSON body and map fields from your scheduler:```json { "event": "cancellation", "start_at": "2026-04-08T15:00:00Z", "end_at": "2026-04-08T16:00:00Z", "schedule_name": "Botox 60", "location_name": "Main Clinic", "provider_name": "Dr. Patel", "external_appointment_id": "apt_123", "cancelled_by_email": "[email protected]" } ```
Step 4: Add webhook signature headers
FullSlot verifies a signed request. Your automation flow must send these headers:- `X-FullSlot-Timestamp` = current unix timestamp
- `X-FullSlot-Signature` = `sha256=
`
The signature is an HMAC-SHA256 of:
```
Typical flow:
1. Build the JSON body you plan to send. 2. Generate a unix timestamp. 3. Compute the HMAC-SHA256 signature using the Webhook Bridge secret. 4. Pass the timestamp, signature, and raw JSON body into the final webhook POST step.
Step 5: Test it
Send a test cancellation through your automation flow. You should see a new slot appear in Open Slots within seconds.Related
- Need the exact field list? Use the JSON examples above or ask support for the current payload spec.