SimplyBook.me
Manage SimplyBook.me bookings, clients, services, providers and locations.
About
SimplyBook.me ships in the w6w first-party pack. It declares 14 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.simplybook- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Calendar & Scheduling
Overview
SimplyBook.me is an online booking system for service businesses — salons, clinics, consultants, fitness studios — that turns a public booking page into a filled calendar. This app brings the Admin REST API (v2) into a workflow: create, look up, cancel, approve and decline bookings; check open slots before offering a time; and read back the services, providers (staff/units), locations and clients behind a booking.
A common pattern is triggering a workflow off an external event — a form submission, a CRM stage change, a support request — and creating the booking directly, or checking availability before recommending a time elsewhere. Booking writes go through the same AdminBookingBuildEntity shape the SimplyBook.me admin panel itself uses, so a booking made here shows up exactly like one made by staff.
This app covers the booking lifecycle and the read-only catalog data around it; it does not touch invoicing, payments, memberships, packages or promotions, which stay specific to each company’s billing setup.
Build with SimplyBook.me
Three routes to the same 14 actions. The Workflow tab is generated from SimplyBook.me's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Approve Booking
booking-approve Approve a pending booking (PUT /admin/bookings/{id}/approve). Requires the "approve booking" custom feature.
Decline Booking
booking-decline Decline a pending booking (PUT /admin/bookings/{id}/decline). Requires the "approve booking" custom feature.
Check Available Slots
schedule-available-slots-get-many List available booking slots for a service/provider on a date (GET /admin/schedule/available-slots).
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying SimplyBook.me's real ids.
{
"manifestVersion": "2",
"name": "simplybook-example",
"steps": [
{
"id": "booking-approve",
"uses": {
"app": "io.w6w.simplybook",
"action": "booking-approve",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Approve Booking
performbooking-approve -
Create Booking
performbooking-create -
Decline Booking
performbooking-decline -
Get Booking
readbooking-get -
List Bookings
readbooking-get-many
+9 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for SimplyBook.me, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to SimplyBook.me. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "booking-approve",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action booking-approve --payload '{"id":"<value>"}'Give an AI agent SimplyBook.me — without giving it SimplyBook.me's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.simplybook#booking-approve",
"input": {
"id": "<id>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's SimplyBook.me connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
SimplyBook.me's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. SimplyBook.me itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
SimplyBook.me declares its own checks, so its health is a property of the app rather than something the host guesses at.