Integrations / NexHealth
NexHealth AI receptionist that fills open slots by phone
The agent finds open slots and books the patient through NexHealth, which writes to the practice's record system, and hands clinical calls to staff.
Practice front desk agent
Books appointments for existing patients.
Instructions
Ask what the visit is for and which day suits them. Offer two open slots and book the one they pick after confirming their name and date of birth. Do not give clinical advice. Transfer pain, medication, insurance and billing questions to the front desk.
- Handoff
- Front desk
Connected tools
- Find open slotsWebhook
- Book appointmentWebhook
- Transfer to front deskTransfer
What a NexHealth AI voice agent can do
Open one to watch a call. The grey lines are the tools the agent calls mid-sentence.
Your service calls NexHealth's /available_slots for the appointment type, and the agent offers the patient two times that fit.
Your service finds the patient by name and date of birth and posts the appointment, and NexHealth writes it to the practice's system.
Pain, medication and insurance questions are not the agent's to answer. A transfer rule sends them straight to the front desk.
Tool definitions
Webhook tools go to POST /v1/agents/tools. Transfers are a system tool on the agent. Replace the placeholder values in capitals with your own.
Find open slots
Asks your service for open slots for a visit type.
Show the JSON definition
Book appointment
Asks your service to find the patient and book the slot.
Show the JSON definition
Transfer to front desk
Cold transfer to the front desk.
Show the JSON definition
Set it up
No native connector. Webhook tools call a service of yours, which holds the NexHealth API key and requests a fresh bearer token every hour. Vendor details read in November 2026.
Build in the sandbox
Create a NexHealth developer account and a sandbox API key. It comes with a demo practice, and calls go to
https://nexhealth.infowithNex-Api-Versionv3.0.0.Run the service
It exchanges the API key for a bearer token at
POST /authenticates, then callsGET /available_slots,GET /patientsandPOST /appointmentswith the subdomain andlocation_id.Onboard the practice
Switch to production, create the practice's institution, and have the office connect its record system. Confirm the sync is active before going live.
Book a real test appointment
Book a test patient, wait for the
appointment_insertion.completewebhook, and have the office confirm it on their schedule and remove it.
Documentation
- NexHealth quickstart (checked November 2026)docs.nexhealth.com docs
- View available slots (checked November 2026)NexHealth docs
- Create appointment (checked November 2026)NexHealth docs
- View patients (checked November 2026)NexHealth docs
- NexHealth go-live checklist (checked November 2026)docs.nexhealth.com docs
- Webhook toolsCartesia docs
- System tools and transfersCartesia docs
Before you build
Patient data
Names, dates of birth and visit reasons are PHI. Settle a BAA with NexHealth, the practice and anyone else in the path before real patients call.
Accepted is not the same as written
A 201 from POST /appointments means NexHealth accepted the booking. The appointment_insertion.complete webhook tells you it reached the practice's system.
Tokens last an hour
A production bearer token from /authenticates lasts one hour, and a webhook tool cannot request a new one. Your service refreshes it before it expires.
Watch the sync
A server-based sync pauses when the office server is off. Subscribe to the sync status webhooks and transfer callers when writes are down.
Use cases for teams on NexHealth
More integrations
Enterprise-grade security
HIPAA compliant

SOC 2 Type 2

GDPR
NexHealth AI voice agent FAQs
Can an AI voice agent book appointments through NexHealth?
Yes. A Cartesia agent calls a service of yours, which holds the NexHealth API key, reads /available_slots, finds the patient by name and date of birth, and posts the appointment. NexHealth writes it to the practice's record system. There is no native connector, and clinical calls go to staff by transfer.
Is a NexHealth voice agent HIPAA compliant?
It can be, once the agreements are in place. Names, dates of birth and visit reasons are PHI, so settle a BAA with NexHealth, the practice and anyone else in the path, including any service that stores call data. Cartesia offers BAAs on its Enterprise plan. The healthcare guide lists what to check.
Which record systems can the agent book into?
The ones NexHealth's Synchronizer supports for that practice. NexHealth lists the supported systems in its docs. A server-based sync pauses when the office server is off, so transfer callers when writes are down.
How do I know the booking reached the practice's system?
Wait for the appointment_insertion.complete webhook. A 201 from POST /appointments only means NexHealth accepted the booking. The webhook tells your service it reached the practice's record system. If it doesn't arrive, have your service flag the booking for the office to check.
Can the agent book new patients in NexHealth?
Yes. NexHealth has a POST /patients endpoint, so your service can create the patient before it books. Many practices prefer to send new patients to the front desk instead.
Get started today
Talk to an expert.
Connect with a member of our team and learn how Cartesia can help you build world-class voice experiences.
Start building.
Access our models via API and bring a voice agent into production in minutes.
