Does Microsoft Bookings support webhooks?

Your options#

This page covers the event source itself. If you already know the destination, connecting Bookings to Zapier and sending bookings to HubSpot, Salesforce or Dynamics cover those routes.

Power Automate connector#

The connector has three triggers: "When a appointment is Created" (spelled that way in the connector), "When an appointment is Updated" and "When an appointment is Cancelled". The payload is rich: customer details, custom question answers, attendees of group bookings, staff, service, times, the Teams join URL, tracking data and the cancel reason. The catches:

• Only Bookings administrators of that calendar can create flows with these triggers. Tenant admin rights aren't enough.
• Five flows per booking mailbox, shared by everyone.
• Update events don't say what changed, and users report the Updated trigger not firing at all for some edits.
• There are no actions to create or change appointments.

To turn it into a webhook for your own system, end the flow with an HTTP step that posts the trigger body to your endpoint, after checking that your Power Automate licence covers the HTTP action. The Power Automate CRM guide builds a complete flow, and why the Bookings trigger isn't firing covers the failures. If all you want is a message in a chat channel, the flow can post there directly: see Bookings notifications in Slack and new booking alerts in a Teams channel.

Poll Microsoft Graph#

Graph has no createdDateTime filter on appointments, so you can't ask for "new since my last check". The workable pattern:

1. Every few minutes, request a rolling window of upcoming appointments:

GET https://graph.microsoft.com/v1.0/solutions/bookingBusinesses/{id}/calendarView?start={now}&end={now+90 days}

2. Store each appointment's id with a hash of the fields you care about.
3. New id means a new booking. A changed hash means an update. An id that disappears from the window before its start time was probably cancelled.
4. Fire your own webhook for each difference.

Keep requests sequential per booking mailbox: the Graph throttling limits allow four concurrent Bookings requests per app ID and mailbox. The Graph Bookings API only covers shared booking pages, not "Bookings with me".

Calendar-level events#

Bookings appointments land on staff members' Outlook calendars, and Outlook calendar events are a supported Graph change-notification resource. Some teams subscribe to staff calendars, or use an automation tool's Outlook calendar trigger, and treat new events as a signal. You get a generic calendar event, not the Bookings record, so custom answers, service IDs and tracking data are missing unless you look the appointment up in Graph afterwards.

Doing this with BookingsXP#

If bookings come in through the BookingsXP widget on your site and you switch on Store bookings for it, BookingsXP sends signed booking.created and booking.failed webhooks (HMAC-SHA256, with retries and a delivery log) to Zapier, Make, n8n, Power Automate or your own URL, and can post each booking to a Microsoft Teams or Slack channel. No Bookings admin role, flow quota or Graph polling is involved. It only sees bookings made through the widget: not bookings created by staff in the Bookings calendar, made on the booking page Microsoft hosts, or cancelled from the email links. Webhooks are on the Pro and Business plans; see webhooks and pricing. BookingsXP is independent and not affiliated with or endorsed by Microsoft.