Integrations

Connect NextReply to the tools you already run on

Google Calendar on every plan. On Business, send every booking to HubSpot, Sheets or any CRM through Zapier, Make or a webhook.

Works with

  • WhatsApp Business Platform
  • Google Calendar
  • Zapier
  • Make
  • Google Sheets
  • HubSpot via webhook or Zapier

Google Calendar works on every plan. Zapier, Make, Google Sheets and HubSpot connect on the Business plan.

WhatsApp integrations that follow the booking

A booking made on WhatsApp is only useful if it lands where your team works. For most appointment businesses that means the calendar. For agencies, clinics groups and multi-site brands it also means a CRM, a spreadsheet or a team chat. NextReply's WhatsApp integrations cover both: every booking goes into Google Calendar on every plan, and on the Business plan every booking can also be sent anywhere else by webhook, through Zapier, Make, HubSpot or Google Sheets.

This page shows what connects, on which plan, and how. We would rather be clear about limits than promise a long logo wall: NextReply integrates with Google Calendar natively and with everything else through webhooks. That covers far more tools than a list of native apps ever could.

Bookings sent to your tools by webhook
  1. New booking: Name, service, date and time
  2. Webhook: Business plan
  3. Zapier / Make / HubSpot / Google Sheets

Integrations by plan

IntegrationWhat it doesStarterProBusiness
Google CalendarReads live availability, writes each booking, prevents double-bookingYesYesYes
WhatsApp Business app (Coexistence)Keep the app on your number while the AI repliesYesYesYes
Webhook on every bookingSends booking details to a URL you chooseNoNoYes
Zapier and MakeRoute bookings to thousands of apps without codeNoNoYes
HubSpotSend bookings to HubSpot contacts and deals via Zapier, Make or webhookNoNoYes
Google SheetsAdd a row for every bookingNoNoYes
Webhook testing dashboardSend test bookings and inspect what your tools receiveNoNoYes

See the full plan breakdown on the pricing page.

Smiling woman reading a reply on her phone

Google Calendar: the integration every plan needs

The calendar is the heart of the product. Before offering a time, the assistant reads your live Google Calendar, so anything already there, including appointments you added by hand, staff holidays and lunch breaks, blocks that time. When a customer confirms, the booking is written to the right calendar immediately. Each staff member, room, bay or technician can have their own calendar, and the assistant books into the right one based on the service.

That is why we include it on Starter: an AI receptionist that cannot see your diary is just an auto-reply. Set-up details, permissions and common questions are on the Google Calendar integration page, and the conversation side is on the appointment booking page.

From first message to confirmed booking
  1. Customer message: “Any slot tomorrow afternoon?”
  2. AI receptionist: Reads service, date and time
  3. Checks your calendar: Offers only free slots
  4. Confirms in the chat: Name, service and time
  5. Booked: In Google Calendar, owner alerted

WhatsApp webhook: every booking, sent where you need it

A webhook is a simple idea: when something happens, one system sends a message to another. On the Business plan, each new booking triggers a webhook to a URL you choose. The data includes the booking details, such as the customer's name and WhatsApp number, the service, the date and time and the staff member. Your developer can receive it directly, or you can point it at Zapier or Make and build the next steps without code.

Before you rely on it, use the webhook testing dashboard to send test bookings and see exactly what arrives. That avoids the classic problem of a broken automation that nobody notices for a month.

Zapier and Make: thousands of apps without code

Zapier and Make connect thousands of business apps. Once NextReply's webhook feeds a Zap or a Make scenario, you can do almost anything with each booking: add a row to Google Sheets, post to a Slack or Microsoft Teams channel, create a task in your project tool, add the customer to an email list they agreed to join, or send the booking to a clinic or property management system that accepts webhooks or has its own Zapier or Make app. Recipes and set-up steps are on the Zapier, Make and Sheets page.

Bookings sent to your tools by webhook
  1. New booking: Name, service, date and time
  2. Webhook: Business plan
  3. Zapier / Make / HubSpot / Google Sheets

WhatsApp CRM integration for sales-led businesses

Real estate agencies, car dealers, education providers and clinic groups often live in a CRM. For them, a WhatsApp CRM integration is non-negotiable: leads that do not reach the CRM do not get followed up. On the Business plan, each booking can create or update a contact and log the appointment. HubSpot is the most common choice, and the HubSpot integration page shows how to map fields. Other CRMs work through Zapier, Make or a direct webhook.

Cafe owner in an apron smiling at a customer message on his phone

Why one webhook beats twenty half-finished apps

Many messaging tools advertise long lists of native integrations. In practice, a lot of those are thin connectors that sync one or two fields and break quietly when the other app changes. We chose a different approach: one native integration where it matters most, Google Calendar, which we build and maintain deeply, and one reliable, testable webhook for everything else.

The webhook route has practical advantages for a small business. You can connect tools we have never heard of, including local CRMs and industry software that only exist in your country, as long as they accept webhooks or have a Zapier or Make app. You control exactly which fields go where. And when something changes, you can see it in the testing dashboard instead of discovering it weeks later.

Questions to ask before you connect anything

A little planning makes integrations far more useful. Before you build, answer these with your team:

  • Who needs to know about a new booking, and how quickly? An instant Slack post suits a dispatch team; a daily sheet suits an owner.
  • Which system is the source of truth for customers? Send bookings there first so you do not end up with three different customer lists.
  • What happens to a booking after it arrives? If nobody acts on it, the integration is decoration.
  • Who will check that it still works next month? Give one person that job.

Simple answers to these four questions usually point to one clear first integration, which is exactly where to start.

What teams actually build

  • A lettings agency sends every booked viewing to HubSpot with budget and area, and posts it to the agents' Slack channel.
  • A salon group adds every booking to a Google Sheet per branch so the owner can compare locations each Monday.
  • A home-services company creates a job in its dispatch tool from each booking, with the customer's address and requested time.
  • A tutoring center adds trial-lesson bookings to its enrolment spreadsheet and notifies the head of department.
  • A clinic group logs appointment requests in its CRM so the call center can see them alongside phone bookings.

Your first integration in five steps

  1. Decide the one outcome you want. For example: "Every booking appears as a row in our bookings sheet." Start with one; add more later.
  2. Create the receiving end. In Zapier or Make, start a new Zap or scenario with a "catch webhook" trigger and copy the URL it gives you.
  3. Paste the URL into NextReply. In the Business dashboard, add it as your booking webhook.
  4. Send a test booking. Use the webhook testing dashboard, then check that Zapier or Make received the fields you expect: name, number, service, date, time and staff member.
  5. Map the fields and switch it on. Point each field at the right column, property or message, run one more test with a real booking from your own phone, and turn the automation on.

Business plan customers also get dedicated onboarding, so someone can walk through this with you the first time.

Business owner answering customer messages on her smartphone

Reporting ideas once bookings flow out

Once every booking reaches a sheet or a CRM, simple reports become possible without anyone typing data. Owners commonly track bookings per day and per hour, which shows how many arrive outside opening hours; bookings per service, which shows what customers actually ask for; bookings per staff member or branch; and, where your set-up records it, which channel each booking came from. A Monday-morning look at those numbers tells you where to add staff, which services to promote and whether your evening coverage is paying off.

Data handling when bookings leave NextReply

Every integration copies customer data into another system, so treat it with the same care as your customer list. Send only the fields each tool needs. Restrict access to sheets and Slack channels that receive bookings. Check where each tool stores data, and mention the tools you use in your privacy notice. Clinics and other businesses handling sensitive information should keep clinical detail out of bookings and webhooks entirely, and review their set-up against the data protection law that applies to them, such as the GDPR in the UK and EU or the UAE's federal data protection law.

Channels are connections too

WhatsApp is the channel NextReply works on today, on every plan. Instagram DMs, Facebook Messenger and Telegram are coming soon. When they launch, each will connect from the dashboard with the platform's own login, and the plan is for their bookings to go into the same Google Calendar and, on Business, through the same webhook. Until then, WhatsApp buttons on your Instagram and Facebook profiles send those customers to the assistant. See the channels page for each channel's status.

WhatsApp live now, Instagram, Messenger and Telegram coming soon
  1. WhatsApp: Live / Instagram: Coming soon / Messenger: Coming soon / Telegram: Coming soon
  2. NextReply AI agent: Live on WhatsApp
  3. Google Calendar: No double bookings / CRM by webhook: Business plan / Your team: Takes over when needed

What we do not integrate with yet

Being specific saves you time. NextReply books into Google Calendar only, so if your diary lives in Outlook, Apple Calendar or a practice management system's own calendar, you will need to use Google Calendar for NextReply bookings or bring bookings back with a webhook. We do not connect to restaurant POS systems, payment gateways or e-commerce stores. The assistant does not take payments. If an integration you need is not here, the Business plan's webhook is usually the route, and our team can advise during onboarding.

Support specialist with a headset smiling while helping a customer

Test your integrations during the free trial

Every plan starts with a 7-day free trial, and that week is the right time to prove an integration before customers depend on it. On Starter or Pro, connect Google Calendar on day one, send yourself three or four booking requests on WhatsApp and check that each one lands on the right staff member's calendar with the right duration. On Business, open the webhook testing dashboard, send a test booking and follow it through Zapier or Make into your CRM or sheet. Check field by field: name, number, service, date, time and staff member. Fix any mapping problems while the volume is low, then let real bookings flow. Plans are $29, $59 and $99 a month in US dollars, and local taxes may apply. If something does not map the way you expect, email support@nextreply.io with a screenshot of the test payload and we will help you sort it out.

How to choose your set-up

If you are a single location and your team works from a calendar, Google Calendar on Starter or Pro is everything you need. If bookings need to reach a CRM, a dispatch tool or a reporting sheet, choose Business and start with a single webhook into Zapier or Make. You can add more steps once the first one is reliable. For a walk-through of the whole product, read how it works, review every capability on the features page, see how it handles after-hours replies or go back to the home page.

Questions people ask

Which WhatsApp integrations are included on every plan?

Google Calendar booking and WhatsApp Coexistence with the WhatsApp Business app are on every plan. Webhooks, Zapier, Make, HubSpot, Google Sheets and the webhook testing dashboard are on Business.

Does NextReply have a WhatsApp webhook?

Yes, on the Business plan. Every new booking sends its details to a URL you choose, which can be your own server, Zapier or Make.

Can I connect WhatsApp bookings to my CRM?

Yes, on the Business plan. HubSpot is common; other CRMs work through Zapier, Make or a direct webhook.

Does it work with Outlook or Apple Calendar?

Not at the moment. NextReply books into Google Calendar only.

Can I test integrations before going live?

Yes. The Business plan includes a webhook testing dashboard where you send test bookings and inspect what your tools receive.

Do I need a developer to use webhooks?

No. Most customers connect the webhook to Zapier or Make and build the rest with point-and-click tools. If you have a developer, they can receive the webhook directly on your own server.

Can I send bookings to more than one tool?

Yes. One webhook into Zapier or Make can fan out to several apps, such as a sheet, a CRM and a Slack channel, from the same booking.

Is there a free trial?

Yes. Every plan has a 7-day free trial. Google Calendar booking is on every plan; pick Business during the trial to test webhooks, Zapier, Make and HubSpot with the testing dashboard.

Every WhatsApp message answered, every free slot offered

Start your 7-day free trial, connect your WhatsApp number and add your services and hours. NextReply answers and books around the clock.