Which Make region should I use?

Whatever region your Make organisation is in. BookingsXP posts to any public HTTPS address, so hook.eu1, hook.us1 and other regional hosts all work.

Can Make react to failed bookings?

booking.failed exists for upstream errors from Microsoft. Filter on the type field in your scenario so booking.created and booking.failed take different routes.

How do I loop over the answers to my Bookings questions?

data.booking.answers is an array. Use an Iterator on it, or map a specific item if your service always asks the same questions in the same order.

Alerts & automation

Make scenarios for Microsoft Bookings

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.

Start free Webhook docs

Plan: Plan: ProNeeds Pro ($19 a month) or Business ($49 a month).
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.

How it works

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.

Setup

Set up Make

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

Step 1: Turn on Store bookings
Dashboard → widget → Data & access → "Store bookings in BookingsXP".
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.
Step 3: Add the endpoint in BookingsXP
Dashboard → Integrations → Add an endpoint → Webhook (JSON). Paste the Make address and pick the widgets.
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.
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.

What you get

The result

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.

Good to know

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.

FAQ

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 free Try it with your link

What happens with Make

Set up Make

Step 1: Turn on Store bookings

Step 2: Add the trigger

Step 3: Add the endpoint in BookingsXP

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

Step 5: Build the rest and schedule it

Outcomes and caveats