BookingsXP

Alerts & automation

Microsoft Bookings alerts in Teams channels

Microsoft Bookings emails the customer and staff member, but it does not post to a shared Teams channel, and it has no webhooks you could wire up yourself. BookingsXP posts an Adaptive Card to the channel of your choice when a widget booking is confirmed, using the Workflows app built into Teams.

Start freeWebhook and alerts docs
Plan
Plan: ProNeeds Pro ($19 a month) or Business ($49 a month).
In short
An Adaptive Card in a Teams channel for each booking: who, what, when, and the campaign that brought them.
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 Microsoft Teams

  • In Teams you create a Workflows flow from the template "Post to a channel when a webhook request is received". Teams gives you a URL.
  • You add that URL in BookingsXP as a Microsoft Teams endpoint. On each booking.created event, BookingsXP posts an Adaptive Card (version 1.4) to it.
  • The card's title reads "New booking: <customer> · <service> · <time>", followed by facts for Service, When (in the booking's time zone), With (staff), Source (source / medium · campaign), Customer (name and email) and Reference (BXP-…).
  • Failed deliveries are retried with backoff up to 8 times over about two hours, and every attempt is listed in the dashboard's delivery log.

Setup

Set up Microsoft Teams

4 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 for the widget

    Alerts carry customer details, so they only fire for widgets that keep a copy of bookings. Dashboard → widget → Data & access → "Store bookings in BookingsXP".

  2. Step 2: Create the Workflows flow in Teams

    In the channel, open the ••• menu → Workflows, and pick "Post to a channel when a webhook request is received". Name it, confirm the team and channel, and finish. Teams shows the webhook URL; copy it.

  3. Step 3: Add the endpoint in BookingsXP

    Dashboard → Integrations → Add an endpoint → Microsoft Teams. Give it a name (for example "Sales channel"), paste the URL, and choose All widgets or one widget. Click Add endpoint.

  4. Step 4: Send a test

    Click Test next to the endpoint. The channel should show "BookingsXP test notification — your endpoint is connected." The dashboard shows the HTTP status and time taken.

Outcomes and caveats

What you get

The result

  • A channel card within seconds of each confirmed website booking.
  • The campaign behind the booking on the card, which Microsoft Bookings itself never records.
  • One endpoint per channel: sales in one, a clinic's front desk in another, filtered by widget.
  • A delivery log with status codes and a Retry button for anything that failed.

Good to know

Limits and caveats

  • Pro plan (5 endpoints across webhooks, Slack and Teams); Business has 25.
  • Requires "Store bookings" on the widget, because the card includes the customer's name and email. Think about who is in the channel.
  • Only bookings made through a BookingsXP widget are posted. Bookings made on the standard Microsoft Bookings page or entered by staff are not.
  • Workflows posts are attributed to the account that created the flow, and the flow stops if that account loses access. Consider creating it under a shared account.
  • Older Office 365 Connector incoming-webhook URLs accept the same card, but Microsoft is retiring those connectors. Use Workflows for new setups.

FAQ

Microsoft Teams 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