CONNECT APP
Build with Microsoft Bookings
Business Management
- OAuth
MCP
Give your agent Microsoft Bookings tools
Every Microsoft Bookings action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Microsoft Bookings account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "microsoft_bookings",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Cancel Appointment:
const result = await mcp.callTool({
name: "microsoft_bookings-cancel-appointment",
arguments: {
businessId: "Business",
appointmentId: "Appointment",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "microsoft_bookings",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Cancel Appointment:
result = await session.call_tool("microsoft_bookings-cancel-appointment", {
"businessId": "Business",
"appointmentId": "Appointment",
})API PROXY
Call the Microsoft Bookings API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Microsoft Bookings API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://graph.microsoft.com/v1.0/solutions/bookingBusinesses",
})
// Any allowed Microsoft Bookings endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://graph.microsoft.com/v1.0/solutions/bookingBusinesses
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9ncmFwaC5taWNyb3NvZnQuY29tL3YxLjAvc29sdXRpb25zL2Jvb2tpbmdCdXNpbmVzc2Vz?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Microsoft Bookings actions from your backend
Connect a user's Microsoft Bookings account once, then run Cancel Appointment on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "microsoft_bookings-cancel-appointment",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
microsoft_bookings: { authProvisionId: "apn_xxxxxxx" },
businessId: "Business",
appointmentId: "Appointment",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="microsoft_bookings-cancel-appointment",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"microsoft_bookings": {"authProvisionId": "apn_xxxxxxx"},
"businessId": "Business",
"appointmentId": "Appointment",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "microsoft_bookings-cancel-appointment",
"configured_props": {
"microsoft_bookings": { "authProvisionId": "apn_xxxxxxx" },
"businessId": "Business",
"appointmentId": "Appointment"
}
}'TOOLS
Microsoft Bookings actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Cancel Appointment
actionCancels an appointment in a Microsoft Bookings business. See the documentationWritev0.0.1 -
Create Appointment
actionCreates a new appointment in a Microsoft Bookings business. See the documentationWritev0.0.1 -
Create Booking Business
actionCreates a new Microsoft Bookings business. See the documentationWritev0.0.1 -
Create Customer
actionCreates a new customer in a Microsoft Bookings business. See the documentationWritev0.0.1 -
Create Service
actionCreates a new service in a Microsoft Bookings business. See the documentationWritev0.0.1 -
Create Staff Member
actionCreates a new staff member in a Microsoft Bookings business. See the documentationWritev0.0.1 -
List Appointments
actionLists appointments in a specified date range for a Microsoft Bookings business. See the documentationRead-onlyv0.0.1 -
List Booking Businesses
actionLists all Microsoft Bookings businesses. See the documentationRead-onlyv0.0.1 -
List Services
actionLists all services in a Microsoft Bookings business. See the documentationRead-onlyv0.0.1 -
List Staff Members
actionLists all staff members in a Microsoft Bookings business. See the documentationRead-onlyv0.0.1
EVENTS
Microsoft Bookings triggers
Event sources your backend can deploy for users and receive through a webhook.
No Microsoft Bookings triggers are available yet.
MULTI-APP
Use Microsoft Bookings with other popular apps
Most products don't stop at one integration. Pair Microsoft Bookings with the other apps your users rely on, and ship use cases that span both.
REFERENCE
App details
Reference metadata for the Microsoft Bookings connector in the Pipedream registry.
- App slug
- microsoft_bookings
- Authentication
- OAuth
- Categories
- Business Management
- Actions
- 10
- Triggers
- 0
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed Microsoft Bookings OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- offline_access
- openid
- profile
- Bookings.Manage.All
- Bookings.Read.All
- Bookings.ReadWrite.All
- BookingsAppointment.ReadWrite.All
- User.Read