Practice Better
Run a health and wellness practice on Practice Better: client records, sessions, packages, invoices, tags, reminders and webhook subscriptions.
About
Practice Better ships in the w6w first-party pack. It declares 26 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.practicebetter- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Calendar & Scheduling · Finance & Accounting
Overview
Practice Better is the practice-management platform a nutritionist, health coach or wellness clinic runs on, and this app covers the day-to-day a workflow is asked to answer for: who the clients are, what is on the calendar, what they have bought, and what they owe.
The client side is the spine. A workflow can list and read client records with the filters the practice actually uses — active or archived, child or clinician records, and everything modified inside a window — create a record from a profile, and update one. Update is a full-replace fragment in Practice Better’s own words, so the action documents that a partial body erases the fields it omits and points the caller at reading the record first.
The scheduling side books and unwinds sessions: list them filtered by consultant, client, service and date window, read one (scoped to a single enrollee for group sessions), book a session with its duration, service type, fee, office location, time zone and telehealth settings, then cancel or delete it. Two vendor list endpoints feed those calls — the practice’s bookable services, and the time-zone names the timeZone field expects.
Money and packaging are read where the spec allows it: the base package templates a practice offers, the instances its clients have purchased, and invoices with their due, paid, payable, refunded and written-off amounts. Tags and reminders round out organization and follow-up, and webhook subscriptions let a workflow react to Practice Better’s own events instead of polling for them — including the event-type catalogue the subscription body needs and a handshake token Practice Better verifies before events start flowing.
Everything here talks to the public Practice Better API over a machine-to-machine OAuth2 client-credentials token, so it keeps working in scheduled and background runs, and the health surface reads Practice Better’s own status page scoped to its Practice Better API component.
Build with Practice Better
Three routes to the same 26 actions. The Workflow tab is generated from Practice Better'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.
Cancel Session
cancel-session Cancel a session, optionally notifying the client and cascading to its pending bookings and recurring automations.
Create Client Record
create-client-record Create a client record from a profile. Returns 409 if a conflicting record already exists.
Create Package
create-package-instance Sell a package template to a client: creates the client's own instance of it with its allowances, expiry and notification choices.
Book Session
create-session Book a session for a client record. Returns 409 on a scheduling conflict unless `ignoreConflict` is set.
Create Webhook Subscription
create-webhook-subscription Subscribe an HTTPS endpoint to Practice Better events. Practice Better verifies the endpoint with `verificationToken` before events start flowing. Requires only the `read` scope, as written in the API document.
Delete Client Record
delete-client-record Delete a client record. Returns the HTTP status; the endpoint has no response body.
Delete Session
delete-session Delete a session from the schedule. Returns the HTTP status; the endpoint has no response body. Use `cancel-session` instead if the session should remain visible as cancelled.
Delete Webhook Subscription
delete-webhook-subscription Remove a webhook subscription. Returns 204 with no body on success, which this action handles explicitly rather than expecting JSON.
Get Client Record
get-client-record Read one client record by id — its active flag, timestamps and the nested `client` details.
Get Consultant Profile
get-consultant-profile Read the authenticated consultant's profile — email, activation status, owner/assistant flags and the company object.
Get Invoice
get-invoice Read one invoice by id, with its client record, consultant, currency and its due/paid/payable/refunded/written-off amounts.
Get Session
get-session Read one session by id: its schedule, participants, location and confirmation status. Pass `recordId` to scope a group session to one enrollee.
List Client Records
list-client-records List client records, optionally filtered by kind (child/client), modification window and status.
List Invoices
list-invoices List invoices, filtered by consultant, client record, payment status and invoice-date window.
List Package Instances
list-package-instances List the package instances clients have purchased, filtered by consultant, package, client record, expiry and status.
List Packages
list-packages List the package templates the practice offers (name and pricing) — not the instances clients have purchased.
List Reminders
list-reminders List reminders (the document's summary calls this operation "List Tasks"), filtered by completion, consultant, client record, team recipient and type.
List Services
list-services List the practice's bookable services — the ids `create-session` takes as `serviceId`.
List Sessions
list-sessions List booked sessions, filtered by consultant, client record, service, group/booked kind and date window.
List Timezones
list-timezones List Practice Better's time zones. Each entry's `name` is the value to send wherever a time zone is expected, such as a session's `timeZone`.
List Webhook Event Types
list-webhook-event-types List every webhook event type Practice Better supports, grouped by category — the valid values for a subscription's `eventTypes`.
List Webhook Subscriptions
list-webhook-subscriptions List webhook subscriptions, filtered by event type, active flag and status. This endpoint's filters are its own, not the standard id/date set the other lists take.
Update Client Record
update-client-record Replace a client record (PUT). This is a FULL REPLACE: read the record with `get-client-record` first, change what you need, and send the whole record back — any field you omit is erased.
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 Practice Better's real ids.
{
"manifestVersion": "2",
"name": "practicebetter-example",
"steps": [
{
"id": "create-client-record",
"uses": {
"app": "io.w6w.practicebetter",
"action": "create-client-record",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"profile": "<profile>"
}
}
]
}Here are some of the things you can do
-
Create Client Record
performcreate-client-record -
Create Package
performcreate-package-instance -
Book Session
performcreate-session -
Create Tag
performcreate-tag -
Create Webhook Subscription
performcreate-webhook-subscription
+21 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 Practice Better, 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 Practice Better. 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: "create-client-record",
payload: {
profile: "<value>",
// isActive: "<value>",
// parentRecordId: "<value>",
// formIds: "<value>",
// sendInvitation: "<value>",
// documentsFolder: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action create-client-record --payload '{"profile":"<value>"}'Give an AI agent Practice Better — without giving it Practice Better'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.practicebetter#create-client-record",
"input": {
"profile": "<profile>"
}
}
}
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 Practice Better 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
Practice Better'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. Practice Better itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Practice Better declares its own checks, so its health is a property of the app rather than something the host guesses at.
Practice Better platform status
The `Practice Better API` component on status.practicebetter.io (id hg7zsrq27t7g) — the component that speaks for api.practicebetter.io. Web Portal, Telehealth, Faxing, Email/SMS delivery, Help Desk, Community and the Integrations group are reported as detail but never drive the verdict.