Integrations Overview
How Nabu reads appointment, sales and client data from the booking and point-of-sale software you already run, rather than replacing any of it.
Why integrations matter
Nabu is a financial intelligence layer on top of your existing business operations. It doesn't replace your booking software, it reads from it. Before Nabu can calculate revenue, profitability, or break-even, it needs raw activity data: which appointments were booked, which services were performed, what payments were collected, and which providers delivered each service.
That data lives in your booking and POS software. Integrations are how it gets into Nabu.
Four ways in
Nabu asks two separate questions during onboarding: which software you run, and how Nabu should read it. The second question is asked for every platform.
Direct connection (API)
Nabu calls your booking software's API and syncs automatically. Once connected, appointment, sales, and client records flow in without any manual work. A newly completed appointment shows up in Nabu on the next sync.
Currently supported: Zenoti
Export bucket (S3)
Nabu reads the S3 bucket your platform writes data exports into. Same automatic result as an API connection, for accounts where the export bucket is what's available.
Currently supported: Zenoti. See Zenoti S3 export bucket for the setup walkthrough.
CSV import
You export data from your software, fill in Nabu's templates, and upload them. This gives Nabu the same underlying records; it just requires periodic manual exports rather than an automatic connection.
Available on every platform. Nabu's import templates are generated from its own schema rather than from any vendor's export format, so they are identical whatever software your data came out of.
See the Data Import section for full details on CSV formatting and upload.
Manual setup
You enter your numbers directly, with no exports involved. Practical for a single location, or as a way to get real answers out of Nabu before you have exports ready.
Available on every platform, including "No booking software."
Switching later
None of these is a one-way door. Any method can be changed to any other from Settings → Integrations after onboarding.
What data Nabu pulls
Whichever method you use, Nabu works with the same types of records:
| Data type | What it includes |
|---|---|
| Appointments | Date, service performed, provider, duration, room, status (completed, cancelled, no-show) |
| Sales/payments | Invoice amounts, payment methods, discounts, credits applied |
| Clients | Name, client ID, contact info |
| Providers | Name, employee ID, role |
| Services | Name, price, duration, category |
What Nabu does NOT pull
Nabu only pulls financial and operational data. It does not access, store, or process:
- Clinical notes or SOAP notes
- Intake forms
- Medical records or treatment protocols
- Any HIPAA-protected health information
If your booking software stores clinical records, Nabu connects only to the scheduling and billing layer, not the clinical layer.
Where to manage integrations
Integrations are configured during onboarding. After that, you can view connection status and trigger manual syncs from Settings → Integrations.
Common Import Issues
The CSV upload errors Nabu reports most often, what each message means, why it happens, and the exact fix. Scan the bold headings for yours.
Connecting Zenoti
How to connect Zenoti to Nabu by API key or S3 export bucket, which method suits your account, and what appointment and sales data gets synced.