NorthCore Labs

Med spa software integrations: the door your vendor opens decides whether the phone can book or only ask.

Med spa software connects to a growth system in one of four ways: an API, a webhook, a Zapier connector or a scheduled export. An API lets another system ask the record a question and get an answer now. A webhook lets the record announce an event the moment it happens. With a Zapier connector, a pre-built bridge carries a small set of those events and actions. The scheduled export is a file that leaves the record on a timer. Which of the four your vendor offers is a question for the vendor, and the order of preference is API, then webhooks, then a connector, then the export.

Updated 2026-10-26

CalculatorWhat does one treatment leave you?

Four connection types, and what each one is

  • An API is a door the vendor opens for other software. Through it a growth system can ask the record for today's calendar or for every patient whose last visit was before a date, or ask it to create a booking. The answer comes back in seconds. Access needs a key the vendor issues and the agreements your practice requires; confirm with counsel which ones.
  • A webhook is a doorbell. When something happens in the record, a booking, a cancellation, a checkout, the record sends a message to an address the growth system watches. It tells the system that something changed, so the system does not have to keep asking.
  • A Zapier connector is a bridge someone already built between the record and a catalog of other apps. It carries the events and actions the builder chose, which may be fewer than the API offers. It is the fastest to switch on, and it carries only what its builder included, so the list is the thing to check.
  • A scheduled export is a file: appointments, patients, services, payments, sent to an address or a folder every night or every week. It is a photograph of the record at the moment it left, and it goes stale until the next one arrives.

Three jobs, and what each connection type lets the growth system do with them

ConnectionRead visit dates for the comebackWrite a booking from the phoneLog texting consent where the sender reads it
APINow, for any patient, by askingYes, with the note attachedYes, to the field the vendor allows
WebhookEach visit, the moment it is checked outNot on its own; it announces and does not createNot on its own
Zapier connectorIf the builder included the eventIf the builder included the actionIf the builder included the field
Scheduled exportOnce per file, up to a day lateNo; the booking is keyed by handNo; the field is updated by hand

Six questions to put to your vendor in writing

  1. Which of the four do you offer, and is each one on my plan or on another? The figure stays on the vendor's pricing page; the answer you need is which.
  2. Through the API, can another system read the calendar and the visit dates, create a booking with a note, and update a consent field? Ask for the written list of what it reads and writes.
  3. Which events send a webhook: booking, cancellation, checkout, new patient? Ask for the list.
  4. If it is a connector, who built it, which events and actions it carries, and when it was last updated.
  5. If it is an export, which record types it covers, how often it runs, what format it comes in, and whether photos, consents and notes are inside it or outside it.
  6. Who signs the agreements my practice requires before patient data moves, and where the data lives once it has. Confirm with counsel which agreements those are.

Prefer the API, then the webhook, then the connector, then the export

Prefer the API, because it reads whatever the vendor exposes and writes the booking back where the front desk sees it. Add webhooks beside it, because a cancellation announced now is a slot that can be refilled today. Take a Zapier connector when the API is closed to you and the connector carries the events you need; check the list before you count on it. Take the scheduled export last, and make it nightly. A comeback timed from a file that is a day old still lands on time, while a booking keyed from a file does not. The export is where the numbers page starts for many practices, and that is a sound place to start.

NorthCore connects the same way through whichever door is open

The pattern is the same on every record. The growth system reads the calendar and the visit dates, so the phone agent can offer open times and the comeback can be timed from the last visit. It writes a booking and the note attached to it, so Priya sees the appointment the way she sees every other one. It never writes into the chart: no treatment notes, no photos, no consent to treat. Which door carries the reading and the writing depends on what the vendor offers, and you are told which before anything goes live. Where the door is an export, the numbers page runs nightly and the phone booking is confirmed by the front desk. Any system touching patient health information signs the agreements your practice requires; confirm with counsel which ones.

How to find out what you have on Monday

  1. Email your vendor the six questions above and ask for written answers.
  2. Log in as the owner and look for a settings page named integrations, API, webhooks or exports. Screenshot what is there.
  3. Run one export of appointments for last month and open it. Note whether the visit date, the service and the provider are columns.
  4. Write the four connection types on a page and mark each one yes, no or unknown. Unknown is a question for the vendor, not a no.

What to do next

NorthCore's Run the whole practice solution connects the phones, the comeback and the numbers to your record through whichever of the four doors its vendor opens, and never touches the chart. Scoped in writing and covered by the promise on this site: results in 90 days, or we keep working until you have them.

Have this built for your practice.

Run the whole practice is the solution this guide belongs to, one of ten jobs in the system we build and run on the software you already use. Scoped in writing. Results in 90 days, or we keep working until you have them.

Questions people ask.

Does my med spa software have an API?

Ask the vendor, in writing, and ask what it reads and writes, because an API that reads the calendar but cannot create a booking changes what gets built. Look in the owner's settings for a page named API or integrations while you wait for the answer.

Is Zapier enough to connect my EMR to a texting system?

If the connector carries the events you need: the visit checked out, the booking created, the consent field. Ask who built it and when it was last updated, and test it with one patient record before you rely on it. If the connector does not carry one of them, the API or an export fills the gap.

Can a growth system run on a nightly export alone?

Yes, for the comeback and the numbers, because a day of lag does not change who is due. Bookings from the phone are then confirmed by the front desk rather than written into the calendar. The export covering appointments, services and payments is the one to ask for.

Will the integration write into patient charts?

No. The pattern reads the calendar and the visit dates and writes a booking with its note, and the chart stays with the providers. Which fields are read and written is agreed in writing before the connection is switched on, with the agreements your practice requires signed first; confirm with counsel which.

Bring the system into your practice.

Walk us through how the practice runs today. We show you what we would build first and how fast. If nothing here fits, we say so on the call.

No card, no contract
A calendar invite and a Zoom link the moment you book.
Prefer email?
admin@northcorelabs.io
NorthCore Labs LLC
7901 4th St N, Ste 300, St. Petersburg, FL 33702