Webhooks scheduling integration guide
Receive booking, response, cancellation, and finalization events. The intended connection would let product teams create, read, and react to scheduling state through stable authenticated interfaces.
PROVIDER SETUP GUIDE. This page documents the provider workflow. It does not claim that a Webhooks account is connected until authorization and lifecycle tests succeed.What the Webhooks connection is designed to do
For api and connectors workflows, the important job is to let product teams create, read, and react to scheduling state through stable authenticated interfaces. Receive booking, response, cancellation, and finalization events. A dependable connection must also make authorization, retries, lifecycle changes, and administrator-visible failures understandable.
Webhooks-specific integration decisions
Deliver signed, versioned events with object and delivery identifiers while supporting duplicates, delay, retries, replay, secret rotation, and state lookup.
Verify these provider-specific assumptions against current primary documentation, the exact account edition, administrator policy, and a non-production test. Record the required permission, authoritative identifier, fallback state, and owner for reconnects. The Meetin.gs verification standard explains how change-sensitive provider claims are treated.
Webhooks provider review points
- Deliver signed. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- Versioned events with object. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- Delivery identifiers while supporting duplicates. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- Secret rotation. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- State lookup. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
Scheduling data and actions in the workflow
The connection should exchange only what the scheduling job requires. For Webhooks, review these three data groups before granting access:
- Events, slots, participants, and lifecycle identifiers. Document its source, destination, owner, and behavior after a cancellation or deletion.
- Signed webhook payloads and delivery timestamps. Document its source, destination, owner, and behavior after a cancellation or deletion.
- Scoped credentials and request metadata. Document its source, destination, owner, and behavior after a cancellation or deletion.
Common Webhooks scheduling use cases
Building scheduling inside another product
This use case should be tested from the organizer's action through the guest-facing result. Include a changed meeting and a failed downstream action, not only a successful new booking.
Synchronizing a proprietary system
This use case should be tested from the organizer's action through the guest-facing result. Include a changed meeting and a failed downstream action, not only a successful new booking.
Reacting to booking, response, finalization, and cancellation events
This use case should be tested from the organizer's action through the guest-facing result. Include a changed meeting and a failed downstream action, not only a successful new booking.
Webhooks setup and verification checklist
- Verify signatures before processing webhook data.Record the expected result and the person responsible when it does not occur.
- Store delivery IDs and make consumers safe to retry.Record the expected result and the person responsible when it does not occur.
- Use separate credentials and callback endpoints for test and production.Record the expected result and the person responsible when it does not occur.
Availability, permissions, and limits
API and webhook availability is contract-specific. Consumers must handle rate limits, version changes, retries, and deleted records safely.
Meetin.gs currently lists this connection as part of its integration architecture. Use the connection request to confirm current production status, supported accounts, scopes, pricing, and rollout timing. This avoids designing a critical workflow around an unverified roadmap item.
Map the Webhooks workflow before connecting it.
Bring the trigger, required data, failure path, and desired guest outcome.
Discuss the connectionWebhooks in one clear flow
Webhooks sends the needed scheduling state to the right system. It keeps the organizer and guest on one record. This prevents a booking change from becoming a silent data mismatch.
Compare this flow with the CRM scheduling integration requirements. Then use the API and webhook help guide to plan retries and recovery.
Simple rule: one booking creates one stable identity. Every later change updates that identity instead of creating a second record.
Webhooks lifecycle acceptance criteria
Use a non-production Webhooks account and one disposable meeting to prove the full connection. Record provider object identifiers beside the Meetin.gs event or booking identifier so every later change can be traced to the same relationship.
| State | Webhooks expectation | Failure to prevent |
|---|---|---|
| Authorization | The intended account grants only the scopes required to let product teams create, read, and react to scheduling state through stable authenticated interfaces. | A personal, test, or former employee account silently owns production records. |
| Confirmation | One provider object is created or updated with the required scheduling data. | A retry creates duplicates or exposes fields that the provider does not need. |
| Reschedule | The original Webhooks relationship moves to the new time and preserves identity. | Old and new records both appear active. |
| Cancellation | The provider reaches the documented cancelled, refunded, removed, or inactive state. | The guest receives stale details or capacity remains blocked. |
| Connection failure | The booking stays understandable, the failure is visible, and retry is safe. | A connected action disappears without an owner or participant-facing fallback. |
Provider-specific boundary
Deliver signed, versioned events with object and delivery identifiers while supporting duplicates, delay, retries, replay, secret rotation, and state lookup. This is the configuration most likely to distinguish a dependable Webhooks connection from a generic successful API response.
Minimum data review
Confirm the purpose and retention of events, slots, participants, and lifecycle identifiers, signed webhook payloads and delivery timestamps, and scoped credentials and request metadata. Do not copy free-text responses, calendar descriptions, participant identifiers, or internal links when the stated connection job does not require them.
Webhooks integration questions
Provider-specific answers for teams planning a Webhooks scheduling connection.
Why did the same webhook arrive twice?
Delivery is at-least-once, so duplicates are expected. Make consumers idempotent on the event identifier — this is the single most important webhook design decision.
How do I verify a webhook is genuine?
Validate the signature against the raw request body before parsing. Middleware that reformats JSON is the usual cause of verification failures.
What should my endpoint return, and how fast?
A success status as soon as the event is safely stored, then process asynchronously. Slow endpoints get retried, and persistently slow ones get disabled.
Before you commit to this connection
Whatever the provider, four checks decide whether a connection is dependable. Test authorization with the identity that will own it in production, one normal confirmation, one reschedule, and one cancellation. Then break it deliberately: revoke access, send a duplicate, and simulate a provider outage.
The meeting must stay visible and manageable even when the connected action fails. Preserve the booking record, show the participant something useful, alert a named owner, and make retry safe. The API and webhook guide covers idempotency and retry design, and the integration directory lists every connection reviewed to the same standard.
A Webhooks operator brief
Deliver signed, versioned events with object and delivery identifiers while supporting duplicates, delay, retries, replay, secret rotation, and state lookup.
Building scheduling inside another product needs a named Webhooks object, authoritative identifier, permitted data set, expected lifecycle result, and recovery owner before it belongs in a production workflow.
Synchronizing a proprietary system needs a named Webhooks object, authoritative identifier, permitted data set, expected lifecycle result, and recovery owner before it belongs in a production workflow.
Reacting to booking, response, finalization, and cancellation events needs a named Webhooks object, authoritative identifier, permitted data set, expected lifecycle result, and recovery owner before it belongs in a production workflow.
The operator should be able to trace a guest action from Meetin.gs to the exact provider response and back again. That trace is more useful than a green connection badge because it also explains delayed, duplicated, rejected, and cancelled work.
