Pabau is positioned by its vendor as an all-in-one practice management system for clinics, medical spas, and related healthcare settings. The platform brings together booking, patient records, payments, marketing, and staff management, with the stated goal of reducing the number of disconnected tools a practice must operate. Vendor pages describe native integrations for payments, accounting, prescribing, labs, and marketing, while support documentation outlines an App Marketplace and API for custom connections. This profile focuses on documented product functions, configuration steps, and implementation boundaries rather than clinical outcomes or regulatory status. [1][3][5]

Core Practice Management Functions

Pabau's feature pages describe a broad set of practice management capabilities. These include scheduling and rota management, digital client records, payment processing, stock management, video conferencing, waitlists, and staff permissions. The vendor also lists marketing functions such as email and SMS campaigns, promo codes, smart surveys, and staff profiles. Pabau states that practices can manage multiple locations, calendars, and teams from one account, with staff permissions, reporting, and scheduling working across sites. [3][5]

Service configuration is documented in the Pabau knowledge base. A service can be created as a standard one-to-one appointment, a virtual session using Pabau's online video conferencing, or a class booked by multiple clients. The setup process includes tabs for general details, location and staff assignment, pricing, online booking appearance, forms, and add-ons. Services can be offered as book and sell, book only, or sell only, depending on whether they appear in the calendar, online booking, or point of sale. [7]

Integration Architecture and App Marketplace

Pabau's integrations page lists connections with payment providers, accounting software, prescribing services, labs, and marketing platforms. Documented examples include Stripe, Xero, Klarna, CloudRx, SignatureRx, Healthcode, Fullscript, Clynxx, Labcorp, Quest Diagnostics, Parchment Health, DoseSpot, HubSpot, GoHighLevel, Business Central, Google Calendar, Google Tag Manager, Meta Pixel, and BNF. The vendor notes that some integrations are region-specific, such as Australian eScripts via Parchment and EPCS-ready US e-prescribing via DoseSpot. [1]

The App Marketplace is accessed through Setup, Integrations, and App Marketplace in Pabau. Users can search for apps by name, category, or supplier, and browse tabs for all apps, installed apps, popular apps, and categories such as Financial, Marketing, Care, Sales, and Other. App cards show category, install count, developer, languages, and privacy information. Some partner-built apps open a consent screen showing exactly what data the app can access before installation, and uninstalling removes access immediately. [4]

Configuring a Service in Pabau

The knowledge base provides a step-by-step process for creating a service. Users select a service type—Service, Virtual, or Class—then work through tabs for General, Assign, Pricing, Online Booking, Forms, and Addons. In the Assign tab, users select which locations offer the service, which employees can perform it, and which rooms and equipment it requires. Only employees assigned to the service can be booked for it online. The Pricing tab determines whether the service is available for booking, selling, or both. The Forms tab manages messages and forms sent before and after appointments, while the Addons tab handles optional extras with their own price and time. The service must have the Active toggle turned on before clicking Create. [7]

API Capabilities and Custom Connections

Pabau provides API documentation through a Postman-hosted reference. The knowledge base states that the documentation includes endpoint references, authentication setup instructions, example requests and responses, and usage limits. The API can return free appointment slots through a List Available Time Slots endpoint, which accepts service IDs and optionally employee IDs and location IDs. Date parameters can be a single day, a month, or ranges such as next7, week-next, or month-this. [2]

Treatment notes are accessible through the API as client forms of the treatment type. The List Client Forms endpoint accepts a form_type parameter, with treatment, consent, questionnaire, prescription, and epaper as documented values. Free-text notes on a client record are returned by List Client Notes. The API can also mark leads as won, lost, or reopened, move leads to existing pipeline stages, and list pipelines and stages. However, the API cannot create pipelines or stages; those must be set up in Pabau first. [2]

Automation and Workflow Configuration

Pabau's vendor blog describes automation workflows that connect booking, intake, billing, and documentation. A booking can trigger reminder sequences and intake forms, with completed forms landing in the patient record and invoices raised against the same appointment. Pabau Scribe is described as drafting treatment notes for clinician review. The vendor states that every subscription includes every feature, so adding automation means switching it on rather than purchasing another tool. [8]

The same blog outlines evaluation dimensions for healthcare workflow automation software. These include integration depth, trigger flexibility, and compliance readiness. The vendor recommends auditing current manual steps before selecting automation tools, separating high-frequency, low-complexity tasks suited to rules-based automation from high-judgment tasks such as triage and complex clinical notes suited to AI. A 30-day post-launch audit is suggested to check whether triggers fired on eligible events and whether outputs matched expectations. [8]

Implementation Boundaries and Regional Scope

Several documented limitations affect how Pabau can be deployed. The App Marketplace notes that which apps users see depends on their region and account, so available integrations may differ from published screenshots. The vendor's FAQ states there are no immediate plans for further integrations, and Pabau does not integrate with Mailchimp, instead directing users to built-in email marketing features. The API cannot create pipelines or stages, and API keys need appropriate access to client records or leads for certain requests. [1][2][4]

The vendor's blog identifies general EHR integration challenges that may apply to Pabau deployments. These include high initial costs, complex setup, staff learning curves, data migration risks, and ongoing maintenance. The blog also notes that automations depending on live data from legacy systems can break silently when field formats change. Pabau's own materials do not provide a formal compatibility matrix for all integrations, and regional prescribing integrations such as Parchment Health and DoseSpot are described for specific markets. [6][8]