Zapier, Make and Sheets
Send every WhatsApp booking wherever your team works
On Business, every WhatsApp booking fires a webhook to Zapier or Make, so it lands in Sheets, Slack or your CRM. Test it first.
WhatsApp Zapier integration for every booking
A WhatsApp Zapier integration answers one practical question: once the AI has booked a customer on WhatsApp, how does everyone else find out? On NextReply's Business plan, each new booking fires a webhook. Point that webhook at Zapier or Make and the booking can land in Google Sheets, Slack, HubSpot, your project tool, your dispatch system or nearly any app your team uses, within seconds of the customer confirming.
We built one webhook rather than a dozen thin connectors on purpose. It works with Zapier, Make and your own server equally well, you control exactly which fields go where, and you can test it in the dashboard before you trust it with real customers.
- New booking: Name, service, date and time
- Webhook: Business plan
- Zapier / Make / HubSpot / Google Sheets
How it works
- The assistant confirms a booking on WhatsApp.
- NextReply sends a webhook to the URL you set, with the booking details, such as the customer's name and number, the service, the date and time and the staff member.
- Zapier or Make catches it using their standard webhook trigger.
- Your steps run: add a row, post a message, create a contact, open a job. Whatever you build.
Nothing on the WhatsApp side changes. The customer gets the same confirmation; the webhook simply makes sure the booking also reaches the tools behind the scenes. The booking itself is already in Google Calendar on every plan.
WhatsApp to Google Sheets
The most popular first automation is the simplest: every booking becomes a row in a Google Sheet. Owners use it to see bookings by day, by service and by staff member, to share a running list with a partner or accountant, or to compare branches. Set up a sheet with one column per field, add a "Create spreadsheet row" step in Zapier or an "Add a row" module in Make, map the fields, and you are done. It takes about ten minutes and gives you a bookings log you can filter, chart and export.
Make WhatsApp integration for more complex flows
Make suits teams that want branches and conditions. A Make scenario can route bookings by service, for example sending AC repairs to one technician's task list and cleaning jobs to another, look up whether a customer already exists in your CRM before creating them, or format a daily summary at 6pm. Start the scenario with Make's custom webhook module, paste its URL into NextReply and send a test booking to define the data structure.
WhatsApp webhook to your CRM
For sales-led businesses, a WhatsApp webhook CRM connection is the main reason to choose Business. Each booked viewing, consultation or trial can create or update a contact, attach the appointment and notify the owner of that lead. HubSpot is common, and the integrations overview lists the main options. CRMs that are not on Zapier or Make can usually accept the webhook directly or through their own API, which a developer can set up in an afternoon.
Ready-to-copy automation ideas
| Goal | Trigger | Action |
|---|---|---|
| Bookings log | NextReply webhook | Add a row in Google Sheets |
| Team alert | NextReply webhook | Post to a Slack or Microsoft Teams channel |
| Lead capture | NextReply webhook | Create or update a HubSpot contact and deal |
| Job dispatch | NextReply webhook | Create a task in your project or field-service tool |
| Manager summary | Schedule plus sheet | Email a daily list of tomorrow's bookings |
| Branch routing | NextReply webhook plus filter | Send each booking to the right branch's sheet or channel |
Start with one. When it has run cleanly for a week, add the next.
Setting up your first Zap, step by step
- Create a new Zap in Zapier and choose "Webhooks by Zapier" with the "Catch Hook" trigger. Zapier gives you a unique URL.
- Add the URL to NextReply. In the Business dashboard, paste it into the booking webhook field and save.
- Send a test booking from the webhook testing dashboard. Back in Zapier, click "Test trigger" and you should see the booking fields arrive.
- Add your action. For a bookings log, choose Google Sheets and "Create Spreadsheet Row", pick your sheet and map each column to a field.
- Test the action, check the row appears, then publish the Zap.
- Make a real booking from your own phone on WhatsApp and confirm it reaches the sheet within a minute or so.
Make works the same way with a "Custom webhook" module at the start of a scenario. The labels differ; the steps do not.
What different businesses send where
- Real estate: every booked viewing creates a CRM contact with budget and area, and pings the listing agent in Slack.
- Home services: every booking opens a job in the dispatch tool with the address and time window, so the office does not retype it.
- Clinics: appointment requests go to a sheet the practice manager reviews each morning, without any clinical details.
- Salon groups: each branch's bookings go to its own tab, and the owner gets a weekly email comparing them.
- Tutoring centers: trial-lesson bookings land in the enrolment tracker, and the head of department gets an email for each new family.
In every case the WhatsApp conversation stays exactly the same for the customer. The webhook is invisible to them; it just means your team stops copying details from one screen to another.
Test it in the webhook dashboard first
Automations fail quietly. A renamed column, a changed field or an expired login can stop bookings flowing for days before anyone notices. The Business plan includes a webhook testing dashboard: send a test booking, see the exact data NextReply sent and whether your endpoint accepted it. Use it when you first connect, after every change to your Zap or scenario, and whenever someone says "I didn't see that booking in the sheet". Dedicated onboarding on Business means someone can walk through the first set-up with you.
When to skip Zapier and use the webhook directly
Zapier and Make are the fastest route for most teams, but not the only one. If you have a developer, or your CRM or booking system already accepts webhooks, you can send NextReply's webhook straight to it. That removes a monthly subscription and one more moving part. It also suits higher volumes, where per-task pricing on automation platforms adds up. A good rule of thumb: start with Zapier or Make to prove the workflow, then move it to a direct webhook once you know exactly what you need and the volume justifies a little development time.
What it costs
Webhooks, the testing dashboard and Zapier and Make connections are part of the NextReply Business plan, at $99 a month in US dollars, with a 7-day free trial like every plan. Local taxes may apply. Zapier and Make have their own plans and usage limits, which you pay to them directly; light use often fits their entry tiers. If your developer receives the webhook on your own server, there is no third-party cost at all. See the pricing page for what Business includes.
Keep the data lean
Every step copies customer data into another tool. Send only what each tool needs, limit who can open the sheet or channel, and mention the tools in your privacy notice. Clinics and other businesses with sensitive information should keep clinical details out of bookings and webhooks entirely.
One webhook today, and for new channels later
Every booking NextReply makes today comes from WhatsApp and goes through your webhook. Instagram DMs, Facebook Messenger and Telegram are coming soon, and the plan is for bookings from those channels to use the same calendar and the same webhook, so your sheet or CRM keeps seeing everything in one place. See the channels page for each channel's status.
- WhatsApp: Live / Instagram: Coming soon / Messenger: Coming soon / Telegram: Coming soon
- NextReply AI agent: Live on WhatsApp
- Google Calendar: No double bookings / CRM by webhook: Business plan / Your team: Takes over when needed
Next steps
Read how it works to see the whole set-up, check how the assistant books in the chat on the appointment booking page, browse every feature, see how integrations help with after-hours bookings, find your sector on the industries page or read guides on the blog. For the overview, visit the home page.
Questions people ask
Is there a free trial?
Yes. Every plan includes a 7-day free trial. Pick Business to try the webhook, send test bookings from the testing dashboard and check your Zap or scenario before any real customer books.
Which plan includes the Zapier and Make integration?
The Business plan. It includes the booking webhook, Zapier and Make connections, HubSpot and Sheets routes, the webhook testing dashboard and dedicated onboarding.
Can I send WhatsApp bookings to Google Sheets?
Yes. Point the webhook at Zapier or Make and add a step that creates a row for every booking.
Do I need to pay for Zapier or Make?
Zapier and Make have their own plans and limits, billed by them. Light use often fits their entry tiers. A direct webhook to your own server has no third-party cost.
What data does the webhook send?
The booking details, such as the customer's name and number, the service, the date and time and the staff member. Use the testing dashboard to see the exact fields.
Can I test without a real customer?
Yes. The webhook testing dashboard sends test bookings so you can check your Zap or scenario before going live.
Can one booking update several tools?
Yes. One webhook into Zapier or Make can run several steps, such as a sheet row, a Slack message and a CRM contact.
Will Instagram and Messenger bookings trigger the webhook?
Those channels are coming soon. Today all bookings come from WhatsApp; when Instagram, Messenger and Telegram launch, they are planned to use the same webhook.
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.