Learn about the fields, workflows, triggers and actions in the PatientNow Essentials integration, and the EMR Appointments calendar.
Note: We also offer a PatientNow Pro integration, which is covered in a separate help article. The two integrations share the same custom fields and pipeline logic, but differ in which statuses PatientNow sends, how orders and memberships come through, and what's needed to create a patient. See the comparison table below.
Opportunity & pipeline automation to decrease manual data entry and drive reporting efficiency
Supports multiple pipelines for practices that operate both surgical and non-surgical services
An EMR Appointments calendar in Aesthetix CRM that mirrors PatientNow Essentials, so appointment reports match your schedule
Automate Google review collection after appointments
Automate post-appointment follow-up
Automate patient retention campaigns for specific treatment and service types
Collect data for better patient segmentation
Automated birthday campaigns
Patient lifetime value tracking from completed orders
Membership tracking and automation
Two-way sync to create patients in PatientNow Essentials from Aesthetix CRM
The integration uses AX Connect, a HIPAA-compliant middleware platform that runs all integrations between Aesthetix CRM and your EMR.
Your practice must have paid API access with PatientNow, which requires a monthly integration fee of $149/month paid directly to PatientNow.
Aesthetix CRM does not collect any additional integration fee and completely sets up the integration for you.
This is a two-way sync between PatientNow Essentials and Aesthetix CRM using PatientNow webhooks and Aesthetix CRM actions. Updates usually appear in Aesthetix CRM within about a minute of the change in PatientNow Essentials.
PatientNow Essentials is primarily used by medical spas and wellness clinics, though some plastic surgery practices also use it. For med spa-only practices, the integration works with the non-surgical lead-to-patient pipeline. For plastic surgery practices, we also use the surgical pipeline with appointment categorization for bookings and no-shows.
In October 2026 we rebuilt the PatientNow Essentials sync. PatientNow sends the same events as before (new patients, patient updates, appointments and orders), but every appointment change now goes through one update process for your practice. That process decides whether the change is real, puts it in the right order, and then updates the contact, runs your workflows and updates the EMR Appointments calendar.
Note on shared custom fields: PatientNow Essentials and PatientNow Pro share the same custom fields in Aesthetix CRM. You may see fields like PNOW Appointment Comments, PNOW Appointment Reason, or PNOW Event Type in your account. These are specific to the PatientNow Pro integration and are not used by the Essentials integration.
PatientNow Essentials often sends the same appointment several times, even when nothing about it has changed. We now only send a change to Aesthetix CRM when something that matters has changed:
the appointment status
the date, time or length
the provider
the service
the location
Editing only an appointment's comments or deposit sends nothing. This means you should no longer see the same appointment repeated in a contact's notes, or the same workflow running twice for one appointment.
If PatientNow sends an appointment's booking after that same appointment has already been checked out or marked as a no-show, the late booking is ignored, so the contact doesn't move backward in the pipeline.
PatientNow Essentials status | What happens in Aesthetix CRM |
|---|---|
Scheduled (booked) | Contact updated with Next Visit Date and Next Visit Service, and moved to the booked stage |
Checked In, Service Started, Service Completed | Shows as Showed on the EMR Appointments calendar only. The contact and pipeline don't change. |
Checked Out | Last Visit Date and Last Visit Service updated. No workflow runs and the pipeline doesn't move. For non-surgical visits, the move to Patient comes from the paid order (see New Order below). |
No-Show | Moved to the Cancelled / No-Show stage. PatientNow sends no-shows in a batch around midnight. |
Cancelled | PatientNow Essentials doesn't send cancellations (see below) |
PatientNow Essentials does not send a webhook when an appointment is cancelled. We checked this across thousands of appointment updates in October 2026 and never received one. This means a cancelled appointment doesn't move the contact to the Cancelled / No-Show stage, and it stays as Confirmed on the EMR Appointments calendar. This is a PatientNow platform limitation, not an integration limitation.
When one patient has several changes at once, we hold them for about a minute, then send them 20 seconds apart in this order: no-shows first, then checkouts, then bookings. Bookings go in pipeline order: pre-op, post-op and follow-up visits first, then other visits, and surgery last. The contact ends on their newest booking.
We check the email and phone number on each PatientNow patient before writing them to Aesthetix CRM:
Placeholder emails (such as a shared "noemail" address) and invalid emails are dropped. This stops unrelated patients being merged into one contact because they share a placeholder email.
Phone numbers are formatted with the +1 country code. International numbers are kept as they are.
A patient with a valid phone number but no usable email is matched and synced by phone.
A patient with neither a usable email nor phone is not synced.
The same checks apply to patient and order updates, not only appointments.
Best practice: Include both a mobile phone number and email address when adding a new client in PatientNow Essentials to ensure a complete sync.
What triggers it: A new patient is created in PatientNow Essentials.
What happens:
We check the email and phone number, then create or update the contact in Aesthetix CRM with core contact information.
If the patient already exists in Aesthetix CRM, we simply update their existing record.
Fields updated in Aesthetix CRM:
First Name, Last Name, Email, Phone
PNOW ID
PNOW Initial Visit (date of initial visit, if it exists; this field is Essentials-only)
PNOW Location
What triggers it: Any update to a patient record in PatientNow Essentials.
What happens:
We bring in the updated information and update the contact in Aesthetix CRM.
No workflow is triggered. This simply keeps the contact record in sync.
Fields updated in Aesthetix CRM:
First Name, Last Name, Email, Phone
PNOW ID
PNOW Initial Visit
PNOW Location
What triggers it: A new appointment is created in PatientNow Essentials (by staff or via online booking).
What happens:
We check that something has changed (see What counts as a change above).
We read the patient's details from PatientNow Essentials and check their email and phone.
We read the initial visit date (if available), location and provider.
For plastic surgery practices: we look up the appointment's category from your practice's appointment types, which decides the pipeline and stage.
We create or update the contact in Aesthetix CRM and add them to the PatientNow Appointments Update workflow.
We add or update the appointment on your EMR Appointments calendar.
Fields updated in Aesthetix CRM:
First Name, Last Name, Email, Phone
Next Visit Date
Next Visit Service
Appointment Category (for plastic surgery practices only)
PNOW ID
PNOW Initial Visit
PNOW Last Appointment ID
PNOW Location
PNOW Primary Employee (the appointment's provider)
About PNOW Primary Employee: PatientNow Essentials books appointments into schedule columns, and some columns are rooms or roles (for example, an "Injection" or "Lab" column) rather than a person. When an appointment is booked into a column that isn't a provider, PNOW Primary Employee is left as it was.
Important: For PatientNow Essentials, Next Visit Service and Next Visit Date are the primary fields for seeing what service was booked and when. The Pro-specific fields like PNOW Event Type and PNOW Appointment Reason are not used in the Essentials integration.
Workflow actions in Aesthetix CRM (Med Spa / Non-Surgical):
A contact note is added with appointment details for your audit trail.
The opportunity moves to the Booked stage.
Once a contact moves to Booked, they are automatically unenrolled from lead nurturing automations (email/SMS drips), preventing redundant follow-ups.
Workflow actions in Aesthetix CRM (Plastic Surgery):
For plastic surgery practices, bookings and no-shows follow the same appointment categorization and dual-pipeline logic as PatientNow Pro. Checkout works differently: see the Appointment Categorization section below.
What triggers it: An appointment status changes in PatientNow Essentials.
What happens:
Checked In, Service Started and Service Completed update the EMR Appointments calendar only.
Checked Out updates Last Visit Date and Last Visit Service (the service of the appointment that was checked out). No workflow runs, so the pipeline doesn't move at checkout. Non-surgical contacts move to Patient when the order is paid; surgical stages don't move (see Appointment Categorization below).
No-Show updates the contact and adds them to the PatientNow Appointments Update workflow, which moves them to the Cancelled / No-Show stage.
Next Visit Date and Next Visit Service are not updated on status changes, only on new bookings.
Fields updated in Aesthetix CRM:
PNOW ID
PNOW Location
PNOW Appointment Status
Last Visit Date and Last Visit Service (on checkout)
Appointment Category (for plastic surgery practices only)
Key Differences from PatientNow Pro:
No-show statuses arrive in batch around midnight. PatientNow Essentials sends no-show statuses all at once, typically around midnight, so no-show pipeline updates process overnight.
Cancellations are never sent. PatientNow Essentials does not send a webhook when an appointment is cancelled, so we cannot move contacts to a cancelled stage. This is a platform limitation.
What triggers it: An order is completed (checkout process) in PatientNow Essentials. This includes all services, memberships, gift cards, and any other transactions processed through the sales register.
What happens:
We receive the webhook when the checkout is completed and you navigate away from the sales register screen.
We read the customer's details, check their email and phone, and read the location.
We combine the order's line items into one list (for example, "Botox, Dysport, Hydrafacial") and save it as Last Purchase.
We check whether this order has already been counted. If PatientNow Essentials sends the same order again and the total hasn't changed, we stop here: nothing is updated and the contact isn't added to the workflow again. If the total has changed, only the difference is counted.
We update the contact in Aesthetix CRM with the invoice amount and order details.
The contact is added to the PatientNow Order Paid workflow.
Fields updated in Aesthetix CRM:
First Name, Last Name, Email, Phone
Invoice Paid Amount (the amount counted for this order: the full total the first time, then only the difference if the order's total changes)
Last Purchase (the order's line items)
PNOW Last Order ID
PNOW Location
What changed in October 2026: orders used to write Last Visit Date and Last Visit Service (from the line items) and the selling staff member to PNOW Primary Employee. Last Visit Date and Last Visit Service now come from the checked-out appointment, PNOW Primary Employee comes only from appointments, and the line items go to the new Last Purchase field. Last Purchase was added on October 29, 2026 and isn't backfilled: it fills in from each patient's next completed order.
Workflow actions in Aesthetix CRM:
A contact note is added with the order total, line items (from Last Purchase), and order ID. The order total in the note is the amount counted, so after an edited order it shows the difference, which can be negative.
The contact moves to the Patient stage of the non-surgical pipeline.
The Invoice Paid Amount is added to Patient Lifetime Value via a math function.
The opportunity value is updated to reflect the actual amount paid, enabling accurate ROI and revenue reporting.
Orders update the non-surgical pipeline only. They don't move or value surgical pipeline opportunities.
The contact is added to the Birthday workflow (see Birthday Field Sync section below).
Rebooking logic: If a patient is rebooked during checkout, their opportunity will automatically move back to the Booked stage, keeping your pipeline aligned with real-time actions.
What changed in November 2026: before November 2, 2026, an order that PatientNow Essentials sent more than once was added to Patient Lifetime Value each time, which could inflate lifetime value and the opportunity value. Each order now counts once, and an edited order counts only the change, so each order adds its final total. Lifetime values recorded before that date aren't recalculated.
What triggers it: A membership is purchased through the checkout/order process in PatientNow Essentials.
Note: Unlike PatientNow Pro (which has a dedicated membership webhook), PatientNow Essentials processes memberships through the same order trigger. Membership data is captured as part of the checkout flow.
Fields updated in Aesthetix CRM:
PNOW Membership ID
PNOW Membership Program Name
PNOW Membership Amount
PNOW Membership Sold Date
Workflow actions in Aesthetix CRM:
A Membership tag is added to the contact.
The membership amount is added to Patient Lifetime Value and the opportunity value.
For recurring memberships, the opportunity value is updated monthly as each order is processed.
Customization Available: You can use the Membership tag as a trigger in your own workflows to send automated communications, for example a thank-you SMS to the client or a notification to your team when a membership is sold.
What triggers it: A tag called pnow-create is added to a contact in Aesthetix CRM (either manually or via automation).
What happens:
The tag triggers a workflow in AX Connect that sends a create patient request to PatientNow Essentials.
The patient is typically created within 15 to 30 seconds.
Required fields in Aesthetix CRM:
First Name
Last Name
Phone
Recommendation: While the integration can be set to push contacts automatically, we typically recommend sending them manually (by adding the tag yourself) to avoid cluttering PatientNow with spam or unqualified leads.
Common reasons for errors:
Missing required fields (first name, last name, email, or phone)
The patient already exists in PatientNow Essentials (the system will not create a duplicate)
Your PatientNow Essentials appointments also appear on a calendar in Aesthetix CRM named EMR Appointments. The calendar went live for PatientNow Essentials practices on October 29 and 30, 2026.
Practices with several locations have one calendar per clinic, med spa and surgery center (for example, EMR Appointments ยท Downtown). Telehealth appointments and appointments at a location added later appear on your main location's calendar.
What it's for: The calendar lets the CRM's appointment reports show confirmed, showed and no-show counts that match PatientNow. It is a mirror of PatientNow Essentials, not a booking calendar.
How appointments appear:
PatientNow Essentials status | Calendar status |
|---|---|
Scheduled | Confirmed |
Checked In, Service Started, Service Completed, Checked Out | Showed |
No-Show | No-Show |
Cancelled appointments stay as Confirmed. PatientNow Essentials doesn't send cancellations, so the calendar can't show them. The calendar's cancelled count will be lower than PatientNow's.
No-shows appear overnight, when PatientNow sends its midnight batch.
Times are shown in your practice's time zone.
Patients with no usable email or phone don't appear on the calendar.
Only appointments created or changed in PatientNow Essentials since your calendar went live appear. Older future appointments appear the next time they change in PatientNow.
The calendar is silent. It sends no confirmations, reminders or cancellation messages to patients, and no alerts to your team. We check it every day to make sure it stays silent.
Please don't:
Book, edit, move or delete appointments on the EMR Appointments calendar. Make changes in PatientNow Essentials; the calendar follows.
Turn on notifications, reminders or Google invitations for this calendar.
Build a workflow with an Appointment Status trigger without a calendar filter. An unfiltered Appointment Status trigger fires for every synced PatientNow appointment, which can send patients duplicate messages. If you build appointment workflows, filter them to the calendars they are meant for.
For plastic surgery practices using PatientNow Essentials with dual pipelines, the integration uses the same appointment categorization system as PatientNow Pro. During setup, each appointment type is mapped to a category (Surgical Consult, Surgical Appointment, Non-Surgical Consult, Non-Surgical Appointment, Block, Post-Op or Pre-Op), and the integration looks up each appointment's category from that mapping. Block, Post-Op and Pre-Op don't move the pipeline.
Important for surgical appointments: checkout doesn't move the surgical pipeline. Bookings and no-shows do, but the integration doesn't set Consult Complete or Surgery Complete: PatientNow Essentials checkouts don't run a pipeline workflow, and orders update the non-surgical pipeline only. Move surgical contacts to those stages by hand, or ask us about a Custom Build Request.
Appointment Category | Status | Pipeline Stage |
|---|---|---|
Surgical Consult | Booked | Consult Booked |
Surgical Consult | Checked Out | No change (see above) |
Surgical Consult | No-Show | Cancelled / No-Show |
Surgical Appointment | Booked | Surgery Scheduled |
Surgical Appointment | Checked Out | No change (see above) |
Surgical Appointment | No-Show | Cancelled / No-Show |
Appointment Category | Status | Pipeline Stage |
|---|---|---|
Non-Surgical Consult / Appointment | Booked | Booked |
Non-Surgical Consult / Appointment | Order paid at checkout | Patient |
Non-Surgical Consult / Appointment | No-Show | Cancelled / No-Show |
For med spa and wellness practices without a surgical pipeline, the logic is straightforward:
Status | Pipeline Stage |
|---|---|
Booked | Booked |
Order paid at checkout | Patient |
No-Show | Cancelled / No-Show |
Existing patients maintain a single "won" status throughout the pipeline as they move between stages.
New leads keep an open status until their order is paid at checkout, at which point they're moved to the Patient stage.
The integration can't write the CRM's native Date of Birth field directly. To work around this, we bring the birthday from PatientNow Essentials into a custom field called PNOW DOB.
A dedicated Birthday workflow then copies the value from PNOW DOB into the native Date of Birth field, keeping them in sync. This ensures that any birthday automations you've built in the CRM work correctly using data from PatientNow Essentials.
The Birthday workflow runs when a contact enters the Order Paid workflow.
Several workflows in your Aesthetix CRM account are hidden and locked. This is intentional: these workflows contain the core integration logic, and modifications could break the integration. The locked workflows include:
PatientNow Appointments Update
PatientNow Order Paid
PatientNow Birthday
If you need custom automation built on top of any of these, let us know and we can either unlock specific workflows or help you build triggers off of the tags and fields these workflows create.
All PatientNow-specific fields are organized in a PatientNow folder within your custom fields. These fields are shared between the PatientNow Essentials and PatientNow Pro integrations.
Custom Field Name | Type | Custom Value |
|---|---|---|
PNOW ID | Text |
|
PNOW Appt Status | Text |
|
PNOW Initial Visit | Date |
|
PNOW Location | Text |
|
PNOW DOB | Date |
|
PNOW Unsubscribed | Single Options |
|
PNOW Last Order ID | Text |
|
PNOW Last Appt ID | Text |
|
PNOW Membership Sold Date | Date |
|
PNOW Membership Program Name | Text |
|
PNOW Membership ID | Text |
|
PNOW Membership Amount | Monetary |
|
PNOW Primary Employee | Text |
|
Note: You may also see fields like PNOW Appointment Comments, PNOW Appointment Reason, and PNOW Event Type in your account. These are specific to the PatientNow Pro integration and are not used by the Essentials integration.
In addition to the PatientNow-specific fields above, the integration also updates these standard Aesthetix CRM fields:
Next Visit Date and Next Visit Service (on new appointment bookings)
Last Visit Date and Last Visit Service (from the checked-out appointment)
Last Purchase (from the completed order's line items)
Invoice Paid Amount
Patient Lifetime Value
Appointment Category (for plastic surgery practices)
Gender
Contact Type
First Name, Last Name, Email, Phone
Cancellations are never sent. PatientNow Essentials does not send a webhook when an appointment is cancelled. Cancelled appointments don't move the pipeline and stay as Confirmed on the EMR Appointments calendar. This is a platform limitation.
No-show statuses arrive overnight. PatientNow Essentials sends no-show statuses in a batch around midnight. Pipeline and calendar updates for no-shows process overnight, not in real time.
Only real changes are sent. Editing an appointment's comments or deposit alone sends nothing to Aesthetix CRM.
Checked In, Service Started and Service Completed don't move the pipeline. They show as Showed on the calendar only.
Last Visit Date and Last Visit Service come from the checked-out appointment. The order's line items go to Last Purchase, which fills in from each patient's next completed order (no backfill).
Checkout doesn't move the pipeline. Non-surgical contacts move to Patient when the order is paid; if a patient is checked out but the order isn't completed, Last Visit updates but the pipeline doesn't move. Surgical contacts aren't moved to Consult Complete or Surgery Complete.
PNOW Primary Employee is the appointment's provider. Orders no longer change it, and appointments booked into a room or role column leave it as it was.
A usable email or phone is required. Placeholder and invalid emails are dropped. A patient with neither a usable email nor phone isn't synced and doesn't appear on the calendar.
Several changes for one patient take a little longer. They're held for about a minute and then sent 20 seconds apart: no-shows first, then checkouts, then bookings, surgery last.
The EMR Appointments calendar is a read-only mirror. Don't book or edit on it, and filter any Appointment Status workflow to the calendars it's meant for, or it fires for every synced appointment.
Next Visit Service is your primary field for booked service info. The Pro-specific fields (PNOW Event Type, PNOW Appointment Reason, PNOW Appointment Comments) are not used in the Essentials integration.
PNOW Initial Visit is Essentials-only. This custom field is not used in the PatientNow Pro integration.
Birthday uses a workaround. PNOW DOB is copied into the native Date of Birth field by a workflow, when an order is completed.
Memberships come through the order trigger. Recurring memberships update the opportunity value monthly.
Each order counts once toward Patient Lifetime Value. An order PatientNow sends again with the same total is ignored. An edited order adds only the difference, which can be negative. Each monthly membership order is a new order, so it's counted in full. Lifetime values recorded before November 2, 2026 aren't recalculated.
Only recent appointments move the pipeline. A change to an appointment that started more than 7 days ago updates the contact's fields and the calendar, but doesn't start a workflow or move the pipeline.
Feature | PatientNow Essentials | PatientNow Pro |
|---|---|---|
Sync method | Webhooks (about a minute) | Webhooks (about a minute; cancellations about 10 minutes) |
Cancelled status | Never sent by PatientNow | Sent (not always) |
No-show timing | Batch overnight (around midnight) | Immediate |
Reschedule detection | No | Yes |
Moves to Patient / completed stage | Non-surgical: when the order is paid. Surgical: Consult Complete and Surgery Complete aren't set | On appointment checkout |
Payment trigger | Order completed (checkout) | Patient bill completed |
Membership trigger | Part of the order | Dedicated membership webhook |
PNOW Initial Visit field | Used | Not used |
PNOW Appointment Comments, Reason, Event Type | Not used | Used |
Patient creation tag | pnow-create | pnow-create |
Patient creation fields | 4 required (first name, last name, email, phone) | Date of birth required; first name, last name and gender needed by PatientNow |
EMR Appointments calendar | Yes | Yes |
Pipeline logic | Identical | Identical |
How do I know the integration received an appointment? Check the contact's Notes tab. Every booking and no-show adds a note with appointment details. If there's no note, either we didn't receive the change or nothing that counts as a change was edited (see What counts as a change above).
Why didn't a cancelled appointment move the contact to the Cancelled stage? PatientNow Essentials doesn't send cancellations to any integration. Cancelled appointments don't move the pipeline and stay as Confirmed on the EMR Appointments calendar. If you need the contact moved, update their stage manually.
Why didn't a no-show update show up immediately? PatientNow Essentials sends no-show statuses in a batch around midnight. The pipeline and calendar update overnight, not in real time.
Why didn't checking in a patient move them in the pipeline? Checked In, Service Started and Service Completed only update the EMR Appointments calendar. The contact moves to Patient when the visit's order is paid at checkout.
Why don't surgical contacts move to Consult Complete or Surgery Complete? PatientNow Essentials checkouts don't run a pipeline workflow, and orders only update the non-surgical pipeline. Move surgical contacts to those stages by hand, or talk to us about a Custom Build Request.
Why doesn't the Last Visit Service field update when an appointment is booked? Last Visit Service and Last Visit Date come from the appointment that was checked out. The booking updates Next Visit Date and Next Visit Service instead. What was purchased is in Last Purchase, which started filling on October 29, 2026, so it's blank for a patient until their next completed order.
Why didn't PNOW Primary Employee change after a booking? If the appointment was booked into a schedule column that's a room or role (for example, an injection or lab column) rather than a provider, we leave PNOW Primary Employee as it was.
Why are there appointments on an EMR Appointments calendar I didn't book? That calendar mirrors PatientNow Essentials so your appointment reports match it. It's silent (no messages to patients), and changes belong in PatientNow, not on the calendar. Appointments from before your calendar went live appear once they next change in PatientNow.
Can I build custom automations off the integration? Yes. You can use the tags added by our workflows (for example, Membership) as triggers for your own workflows, or trigger automations off custom field changes. If you build on Appointment Status, filter the trigger to the calendars it's meant for. If you need a locked workflow unlocked, contact us.
Why do I see Pro-specific fields in my account? PatientNow Essentials and Pro share the same custom fields. Fields like PNOW Appointment Comments, PNOW Appointment Reason, and PNOW Event Type are from the Pro integration and are not used in Essentials.
How do recurring memberships work? When a recurring membership processes each month, a new order is created in PatientNow Essentials. This triggers the order workflow, which adds the monthly amount to the Patient Lifetime Value and updates the opportunity value accordingly.
Why does an Order Paid note show a small or negative order total? The note shows the amount counted for that order. When a completed order is edited in PatientNow Essentials and sent again, we count only the change, so the note shows the difference (for example, -$150 after a discount). Each order's contribution to Patient Lifetime Value then equals its final total. If PatientNow sends an order again without changing its total, nothing is added and no note appears.
Should I set up automatic patient creation or manual? We typically recommend manual (adding the pnow-create tag yourself) to avoid pushing spam or unqualified leads into PatientNow. Automatic creation is available if you prefer, but discuss it with your Aesthetix CRM team first.
If something isn't syncing the way you expect, contact Aesthetix CRM support with the contact's name and roughly when the change was made in PatientNow Essentials. For custom automation built on top of the integration, submit a Custom Build Request.