RIFT connects to Nookal through Nookal's API v3. Create a client in Nookal, assign the six read queries RIFT needs, approve your locations, paste the client's token into RIFT, and your practice's billing leak report runs from live data - appointments never invoiced, invoices still unpaid, and no-show or cancellation fees never raised. RIFT only ever reads: nothing in your Nookal account is changed. Older Nookal API keys still work too (see the note below), and a practice that would rather not share a credential can upload Nookal's reports instead.
Before you start
- A Nookal login that can open Setup > Connections > API v3.0 / GraphQL Client Config.
- No installation is required on either side - the whole setup is creating a client and pasting its token.
- New to RIFT? The first leak report is free and does not require creating an account.
Setup steps
Create an API v3 client in Nookal
In Nookal, open Setup > Connections > API v3.0 / GraphQL Client Config and add a new client. Give it a name you will recognise later, such as "RIFT".
Assign six queries, approve your locations, copy the token
A new client can run nothing until you assign queries to it. RIFT needs exactly these six:
locations, staff, clients, appointments, invoices and invoiceEntry.
Leave every other query unassigned, and nothing under mutations - RIFT never reads clinical notes, documents or files, and it never writes. Then approve every location your practice uses: the client can only see the locations that are approved. Save, and copy the client's token.
The invoices query matters more than it looks. Without it Nookal still lets a client read appointments but hands back no invoices at all. RIFT checks for that and refuses the token, rather than show every invoice you have ever raised as missing.
Paste the token into RIFT
For a first free report: go to rift.rapidintelligence.com.au/try, choose Nookal, and paste the token. The report runs on screen in minutes; for larger practices it is emailed when the analysis finishes. The token is used for that one read and discarded - it is never stored.
For an ongoing connection: in RIFT, open Settings > Data source, find the Nookal section, and paste the token into the field labelled Nookal API v3 client token (or an older API key) under Connect Nookal. RIFT checks it with Nookal straight away, shows Connected (API v3), and lists the locations the client covers.
Review your leak report
RIFT reads the billing side of your account and builds the leak report. A connected clinic then stays current automatically: RIFT re-syncs from Nookal daily, so an uninvoiced session surfaces in the week it happened rather than at the next audit.
If RIFT will not accept the token
RIFT tests a token before saving it and tells you which of these it found. A token that fails is never stored.
- "Nookal rejected this key" - the token was not copied in full, or the client has been deleted in Nookal. Open the client and copy the token again; if the client is gone, create a new one and assign the six queries.
- "This key doesn't cover any location yet" - no location is approved on the client. Approve every location and save.
- "This key can't read invoices" - the invoices query is not assigned to the client. Assign it, save, and connect again.
Using an older Nookal API key?
Keys from Setup > Connections > API Keys still work: paste one into the same field and RIFT tells the two apart by their shape. A new key starts with three things off - tick every location, tick Invoices under Additional Options, switch Status on, then Save Changes - and without them there is nothing to read. Leave Clinical Notes, Documents and Logos & Staff Photos unticked. Nookal does not offer read-only keys - Nookal's own page says an API key has full access to the account - but RIFT only ever calls Nookal's read requests, and you can delete the key in Nookal at any time.
No credential? Upload Nookal's reports instead
A practice that would rather not share a token or key can upload three of Nookal's report exports. In Nookal open Reports and export Uninvoiced Bookings (tick Include DNA), Ageing Debts (tick Show Expanded, date range 10 Years) and Cancellations as CSV, then zip the files. On the free report, open "Can't share an API key? Upload an export instead" on the Nookal tab; in RIFT, use Settings > Data source > Nookal > Upload an export instead. The numbers are a snapshot as at the day you upload, with no daily sync, and the files are read in memory and deleted. Full steps: Connect Zanda, Cliniko or Nookal to RIFT.
What syncs
RIFT reads appointments, invoices and their line items, practitioners, services and locations, plus the patient names and contact details it needs to name an item and, for chase emails, to address it. Treatment notes and documents are excluded outright - RIFT never requests them, which is why only the six queries above are assigned to the client. If your client covers more than one location, RIFT analyses them together as one practice.
One thing to know plainly: RIFT only ever sends read queries to Nookal; it never adds, edits or deletes anything, and a client that has no mutations assigned could not even if asked.
Some honest edges worth knowing. Overdue invoices are chased for what is still owing, because RIFT uses Nookal's own balance for each invoice, so a part payment is taken into account. Class bookings are not analysed yet - only consultations. Patient cases are not read yet, so funded sessions left unbooked are not tracked on Nookal. Medicare and health-fund claim outcomes are not in Nookal's API. And an invoice with no line items on it is ignored, so an appointment attached to an empty invoice still reads as uninvoiced. The full list is in what RIFT can and cannot detect from Nookal data.
Disconnecting
Two ways. In RIFT: Settings > Data source > Nookal > Disconnect - the stored token is removed and daily syncs stop until a new one is added; your items and history stay. Or in Nookal: delete the client under Setup > Connections > API v3.0 / GraphQL Client Config (or, for an older key, delete it under API Keys - switching its Status off is not enough on its own), no conversation required.
Security and privacy
Tokens and keys are held encrypted and never appear in logs; RIFT sends your credential in a request header or body, never in a web address. Data is hosted in Australia (Sydney) and encrypted at rest, and patient billing data is never sent to AI providers. Details: Trust & Security, Privacy Policy and the data agreement.
Need a hand?
Email contact@rapidintelligence.com.au - replies come from the person who built the integration.