Integrations and the API

7 articles Account, integrations and support

Webhooks (send queue events to Zapier, Make or your own system) Add a webhook in Connect Apps and NextUp Walk-in sends a real-time HTTP POST to your web address whenever something happens in the queue. Webhooks are on the paid plans, not the Free plan.

Add a webhook in Connect Apps and NextUp Walk-in sends a real-time HTTP POST to your web address whenever something happens in the queue. Webhooks are on the paid plans, not the Free plan.

Steps

Step 1 of 4

Open Connect Apps in the dashboard sidebar and click Add a webhook.

The Connect Apps page in the dashboard of a made-up hair salon.
The Connect Apps page in your dashboard.
Step 2 of 4

Enter a label (so you remember what it does) and the destination URL, such as your app's endpoint or Zapier's webhook URL.

Step 3 of 4

Choose which events to send.

Step 4 of 4

Click Add webhook.

Fix it

  • Not sure it works? Each webhook can send a test event. Click Send test event first.
  • A delivery failed? The delivery history shows the HTTP status code and the error, and you can retry it.
  • Want to know a message really came from NextUp? Check the signature (see Test, check and secure below).
More detail

Use webhooks to connect NextUp Walk-in to Zapier, Make, your CRM, Google Sheets, Slack or any custom system.

Available events

  • Line: someone joins the line, someone is called, a visit starts, a visit is finished, someone called doesn't show up, someone leaves the line, a location starts or stops taking walk-ins.
  • Appointments: an appointment is booked, canceled, or moved to a new time or person, someone with an appointment arrives, and someone with an appointment doesn't come.
  • Job tickets (auto service, device repair, car wash, tax returns, grooming): a ticket is opened, moves to another stage, or reaches its last stage (ticket.created, ticket.stage_changed, ticket.closed). Each carries the ticket's number (like T-1042), the kind of job, the stage's id and name, and the customer's first name. The customer's status link, phone number and email address are never sent, because a webhook log would keep a link anyone could open.
  • Bills: a bill is paid in full (checkout.paid), sent once with the amounts in cents (paid, tip, tax, total), the currency and how it was paid (cash, link, reader, gift card and so on). No name, phone number, email address or card detail is sent.

Tax offices: send stage changes to your portal

A tax office can keep its portal or practice software and still have the front desk move a client along. In Zapier or Make, make a trigger that catches a webhook (in Zapier, Webhooks by Zapier, Catch Hook) and copy its URL. In NextUp Walk-in add a webhook with that URL for ticket.stage_changed. Then add an action in your portal or practice software that reads the stage (documents_in, preparing, review, ready_to_sign, filed) and the number, for example moving that client's job to Ready to sign or sending your portal's own message when the stage is ready_to_sign. Put the ticket number in the job's name on your side so the action can find the right client. Use Send test event first to see the message, then check the delivery history.

Test, check and secure

  • Each webhook can send a test event.
  • It shows a delivery history with the HTTP status code; if a delivery failed you can see the error and retry it.
  • Payloads are signed with a secret (an HMAC signature in the NextUp-Signature header) so your server can check they came from NextUp Walk-in, and you can rotate the secret.
API keys (programmatic access for developers) An API key gives a developer long-lived access to your NextUp Walk-in account. API keys are on the paid plans, not the Free plan.

An API key gives a developer long-lived access to your NextUp Walk-in account. API keys are on the paid plans, not the Free plan.

Steps

Step 1 of 4

Open API Keys in the dashboard sidebar.

The API Keys page in the dashboard of a made-up hair salon.
The API Keys page in your dashboard.
Step 2 of 4

Click Create key and, in the Create API key dialog, give it a name that says what it's for (for example "Analytics export").

Step 3 of 4

Copy the key immediately. It is shown in full only once. Store it somewhere safe, like a password manager or your server's environment settings.

Step 4 of 4

Send the key as a Bearer token in the Authorization header of your requests.

Fix it

  • Lost the key? It is shown in full only once. Create a new key.
  • Need to revoke a key? Delete it. Any app using it stops working immediately, so create and switch to a new key first.
  • Key shared by mistake? Delete it and make a new one.
More detail

Use API keys for custom dashboards, automated reporting, or an integration that webhooks alone can't cover.

Keep it safe

  • API keys have the same permissions as an owner, so treat them like a password and never put them in website code or share them.
  • To revoke a key, delete it. Any app using it stops working immediately, so create and switch to a new key first.
Google Calendar sync for team members Each team member can connect their Google Calendar, so personal events close those times for bookings and their NextUp Walk-in appointments appear on their calendar.

Each team member can connect their Google Calendar, so personal events close those times for bookings and their NextUp Walk-in appointments appear on their calendar.

Steps

Step 1 of 3

The team member signs in with their own login and opens their profile from the Team page .

The Team page with three team members and the field to add another.
Add a name, then click a card to add their photo.
Step 2 of 3

Connect their Google Calendar.

Step 3 of 3

Follow the Google sign-in prompt to allow access to their calendar.

Fix it

  • Owner can't connect it for them? Only the team member can connect their calendar. An owner or manager can see that it is connected and disconnect it.
  • Want it to stop? Disconnect it from their profile. Their appointments stop syncing, and the ones still ahead come off their calendar.
More detail
  • It is set per person, so one person connecting their calendar doesn't affect anyone else.
  • It works alongside their weekly hours and blocked time in NextUp Walk-in.
  • Customers booking online then only see times when that person is actually free.
  • Disconnecting also happens when they leave the business or their sign-in is removed.
Sign in with Google, Apple, Facebook or Microsoft Owners, managers and team members with their own sign-in can use an email and password, an emailed sign-in code or link, Google, Apple, Facebook or Microsoft.

Owners, managers and team members with their own sign-in can use an email and password, an emailed sign-in code or link, Google, Apple, Facebook or Microsoft.

  • Clients can use Google, Apple, Facebook or Microsoft too, in the client app and on the sign-in page.
  • Emailed sign-in codes last 15 minutes.
  • An emailed sign-in link only works when you press Continue on the page it opens, so an email security scanner can't use it up.

Steps

Step 1 of 2

On the sign-in page, choose Google, Apple, Facebook or Microsoft, or ask for an emailed sign-in code or link (no password needed).

The NextUp Walk-in log in page, with the Google, Apple, Facebook and Microsoft sign-in buttons circled.
Sign-in buttons on the log in page.
Step 2 of 2

Follow the provider's prompt, or enter the code or press Continue on the link's page.

Fix it

  • Signed up with Google and want a password too? Set one on your Account page without removing Google sign-in.
  • Code expired? Emailed sign-in codes last 15 minutes. Ask for a new one.
More detail

Two-factor authentication, if you turn it on, applies to every sign-in method.

Single sign-on (OpenID Connect or SAML 2.0) and SCIM 2.0 user provisioning are on the Pro plan and up, turned on on request. SCIM covers people and the groups your company's system pushes (roles can follow them).

AI assistants (ChatGPT, Claude and others) NextUp Walk-in has a public, read-only connection (an MCP server) that AI assistants supporting MCP can use. It is on for every plan, with nothing for you to set up.

NextUp Walk-in has a public, read-only connection (an MCP server) that AI assistants supporting MCP can use. It is on for every plan, with nothing for you to set up.

The Connect Apps page in the dashboard of a made-up hair salon.
The Connect Apps page in your dashboard.
  • An assistant can find NextUp Walk-in businesses by city and trade, read a business's live wait, services, hours and times open for booking, and hand the customer the link to check in or book.
  • It shows only what your public Check-in Page already shows, needs no sign-in, and can't join anyone or change anything: the customer finishes on your own page.
  • It covers all business types.
More detail

Listings in the assistants' own app directories are still pending, so say assistants "can connect" rather than that NextUp Walk-in is listed in their stores.

Zapier and Make recipes Each recipe starts the same way: catch a webhook in Zapier or Make, add its URL in NextUp Walk-in, and pick the event the recipe names. Webhooks are on the paid plans.

Each recipe starts the same way: catch a webhook in Zapier or Make, add its URL in NextUp Walk-in, and pick the event the recipe names. Webhooks are on the paid plans.

Steps

Step 1 of 3

In Zapier (Webhooks by Zapier, Catch Hook) or Make (Custom webhook), create a trigger that catches a webhook and copy its URL.

Step 2 of 3

In NextUp Walk-in open Connect Apps, click Add a webhook, paste the URL and pick the event named in the recipe.

The Connect Apps page in the dashboard of a made-up hair salon.
The Connect Apps page in your dashboard.
Step 3 of 3

Click Send test event so Zapier or Make can see the message, then build the action.

Fix it

  • Zapier or Make sees nothing? Use Send test event, then check the delivery history on the Connect Apps page for the HTTP status code.
  • Expecting data to flow back into NextUp Walk-in? Zapier and Make only receive what NextUp Walk-in sends; nothing flows back in from them.
More detail

Recipe 1: add every new walk-in to a Google Sheet

Event: visit.joined. Action: add a row to a Google Sheets spreadsheet with the customer's first name, the time and the team member. Add visit.completed in a second webhook if you also want a row when the visit is finished.

Recipe 2: post to Slack when someone arrives for an appointment

Event: appointment.checked_in. Action: send a message to a Slack channel, such as the front desk channel, so the next team member sees the arrival. Add appointment.no_show to the same webhook if you want a message when someone doesn't come.

Recipe 3: keep your calendar or CRM in step with bookings

Events: appointment.booked, appointment.rescheduled and appointment.cancelled. Action: create, update or delete the matching event or contact in your own calendar or CRM. Use the appointment's id from the message to find the right entry on your side. Make one webhook per event if you want a separate action for each.

Recipe 4: tell a customer when their job moves on

Event: ticket.stage_changed, for auto service, device repair, car wash, tax returns and grooming. Action: send your own message or update your own tracker when the stage is the one you care about, for example ready_to_sign. The customer's phone number and email address are not sent, so look the customer up on your side by the ticket's number.

Before you rely on a recipe

  • Use Send test event, then check the delivery history on the Connect Apps page for the HTTP status code.
  • Zapier and Make only receive what NextUp Walk-in sends; nothing flows back into NextUp Walk-in from them.
Using NextUp Walk-in next to practice-management software (vet clinics) NextUp Walk-in does not connect to veterinary practice-management software, and it is not a medical record or an insurance-claims system. Many clinics run both: your practice software keeps the patient record, and NextUp Walk-in runs the front desk line, check-in, appointments and customer messages.

NextUp Walk-in does not connect to veterinary practice-management software, and it is not a medical record or an insurance-claims system. Many clinics run both: your practice software keeps the patient record, and NextUp Walk-in runs the front desk line, check-in, appointments and customer messages.

The Connect Apps page in the dashboard of a made-up hair salon.
The Connect Apps page in your dashboard.
  • To keep the two in step, send webhook messages to a tool that can receive them.
  • To get your history out, download the Excel visit export from the Insights page .
  • Keep diagnoses, treatment notes and anything a regulator asks you to keep in your practice software.

Fix it

  • Need your practice software to receive the events? NextUp Walk-in does not write into it. Ask your software's vendor whether it accepts incoming webhooks before you plan around this, or catch the message in Zapier or Make and send it on to a tool you already use.
More detail

What NextUp Walk-in sends

With a webhook, NextUp Walk-in sends a message to a web address you choose each time something happens in the line: visit.joined when someone checks in, visit.called when they are called, visit.seated when the visit starts, visit.completed when it is finished, visit.no_show and visit.left. Appointment events (appointment.booked, appointment.rescheduled, appointment.cancelled, appointment.checked_in and appointment.no_show) work the same way. Webhooks are on the paid plans.

What you do with it

NextUp Walk-in does not write into your practice software. Someone has to receive the message: your software's vendor or an IT person can accept a webhook, or you can catch it in Zapier or Make and send it on to a tool you already use. Ask your software's vendor whether it accepts incoming webhooks before you plan around this.

Getting your visit history out

On the Insights page , the Excel download gives one row per visit with the name, join time, wait time, service, team member and outcome, for up to about 400 days. A CSV visit export is also available. Owners can always download, and owners choose whether managers can.

Keep medical records where they belong

Vaccine dates and a photo of the paperwork can be kept under Health Records for the front desk. Keep diagnoses, treatment notes and anything a regulator asks you to keep in your practice software.

Was this helpful?

Didn't find your answer?

Email support@nextupwalkin.com, or send us a message and we'll get back to you.