BookingsXP

Alerts & automation

Microsoft Bookings in Make (make.com)

Make has no Microsoft Bookings app, so a scenario can't watch Bookings directly (as of October 2026). Make is a good fit when a booking should fan out to several places at once: a CRM, a spreadsheet, a follow-up email and an internal alert. BookingsXP gives the scenario a starting point that Microsoft Bookings lacks: a webhook the moment a booking made through your widget is confirmed.

Try it with your linkWebhook docs
Integration
Make
Plan: Pro
Needs Pro ($9 a month or $90 a year), Business ($29 a month) or Enterprise.
In short
A Make scenario that starts from Webhooks → Custom webhook on every booking, with the data structure learned from a real one.
Microsoft Bookings
Stays your system of record. Bookings land in Outlook and Teams and Microsoft sends the invites and reminders.
Trademarks
Make is a trademark of its owner. BookingsXP is independent and not affiliated with or endorsed by Make.

What happens with Make

  • Make's Webhooks app creates a Custom webhook with a unique URL on a regional host, such as hook.eu1.make.com.
  • BookingsXP posts the booking.created envelope there. Make learns the data structure from the first request it receives, then exposes each field to later modules.
  • Make answers 200 as soon as it queues the request, so a slow scenario does not trigger BookingsXP retries.

Set up Make

5 steps. Names of menus and buttons are as they appear today; vendors rename things, so look for the closest match.

  1. Step 1: Turn on Store bookings

    Dashboard → widget → Data & access → "Store bookings in BookingsXP".

  2. Step 2: Add the trigger

    In a new scenario, click + and choose Webhooks → Custom webhook. Click Add, name the hook, save, and copy the address Make shows.

  3. Step 3: Add the endpoint in BookingsXP

    Dashboard → Integrations → Add an endpoint → Webhook (JSON). Paste the Make address and pick the widgets.

  4. Step 4: Let Make learn the structure from a real booking

    While Make shows it is waiting for data, make a test booking in the widget (the Test button's ping only contains a message). Make then shows fields such as data.booking.customer.email. Use "Redetermine data structure" if you need to repeat this.

  5. Step 5: Build the rest and schedule it

    Add a filter on type = booking.created, then your modules. Set the scenario to run immediately as data arrives and switch it on.

Outcomes and caveats

What you get

  • One booking fanned out to as many apps as you like in a single scenario.
  • Attribution fields and the BXP reference available to every module.
  • Retries from BookingsXP if Make's webhook cannot be reached, plus Make's own execution history.

Limits and caveats

  • BookingsXP Pro is needed for webhooks. Make's operation limits depend on your Make plan.
  • Make does not check the BookingsXP-Signature header for you. Treat the webhook address as a secret.
  • Make learns the structure from the first request. If that was a test ping, run "Redetermine data structure" and send a real booking.
  • Only widget bookings are sent; later changes in Microsoft Bookings are not.

Make questions

Something not covered? Email hello@bookingsxp.com.

Start free, no card

Start on Free with the widget and GA4 events, then move to Pro when you want ad conversions, webhooks and chat alerts.

Start freeTry it with your link

No Microsoft sign-in or admin consent. Free plan, no card.