Connect WhatsApp to Make (Integromat) — send booking reminders

Use Make (formerly Integromat) to bridge any booking source into Google Calendar. Zellbox picks up the events and fires 24h + 2h WhatsApp reminders automatically.

Nacho Collby Updated 2 min read
Use Make (formerly Integromat) to bridge any booking source into Google Calendar. Zellbox picks up the events and fires 24h + 2h WhatsApp reminders automatically.

Editorial disclosure: I work at Zellbox. Make described from their product page as of August 2026.

Make (formerly Integromat) is the visual automation platform with strong branching + iterator logic. Zellbox layers on top of Google Calendar — anything Make writes there becomes a WhatsApp reminder source via Zellbox.

How it works

  1. In Make → create a Scenario: any booking source (webhook, HTTP, custom app) → Google Calendar → Create an Event.
  2. In Zellbox → Onboarding step 2 → connect the destination Google Calendar.
  3. Every triggered booking now appears on your calendar. Zellbox fires WhatsApp reminders at 24 h and 2 h.

Common recipes

  • Webhook (custom booking widget) → Make → GCal → Zellbox WhatsApp reminder
  • HTTP call from proprietary practice-management system → Make router → GCal → Zellbox
  • Airtable form submission → Make → GCal → Zellbox

What Zellbox adds beyond DIY Make WhatsApp

  • Ready template management — Make can call the WhatsApp Business Cloud API directly if you want to author your own templates, but that means owning Meta’s template-approval flow; Zellbox ships approved templates for common appointment patterns so there’s nothing to submit for review.
  • Signed consent PDFs on the customer record — the signed PDF attaches automatically as part of the same reminder flow, no separate paperwork step to build in Make.
  • Two-way replies land in your Zellbox inbox — when a customer replies to confirm or ask a question, the message shows up next to that customer’s record instead of scattered across a DIY webhook handler.
  • BSP relationship handled by Zellbox — a DIY Make setup still needs a Business Solution Provider relationship for the WhatsApp API; Zellbox owns that so there’s no separate BSP contract to negotiate.

Make vs Zapier for this specific flow

When Make’s branching wins

Make’s visual scenario builder handles multi-branch logic (for example, routing different booking sources to different Google Calendars based on service type) more cleanly than Zapier’s linear Zaps, often at a lower cost per operation for high-volume flows.

When to just use Zapier instead

For a single booking source flowing straight into one Google Calendar, Zapier’s simpler trigger-action model is faster to set up. Make earns its complexity once you’re combining more than one booking source or doing conditional routing before the event hits Google Calendar.

Free tier covers 100 reminders/mo.


About the author: Nacho Coll is the founder of Zellbox. He writes about WhatsApp Business automation for appointment-driven small businesses.

Frequently asked questions

How does Make connect to WhatsApp via Zellbox?
Make (formerly Integromat) bridges any of its 1,500+ integrations into Google Calendar. Zellbox reads Google Calendar and fires WhatsApp reminders on schedule.
How does Make compare to Zapier for this?
Make has more powerful branching + iterator logic, often at lower cost per operation. For simple booking source → GCal flows, both work; Make is better for complex multi-branch scenarios.
Common Make + Zellbox recipe?
Webhook from a booking form → Make → Google Calendar → Zellbox → WhatsApp reminder. Or: HTTP call from a custom app → Make router → GCal → Zellbox.
Nacho Coll

About the author

Founder & Engineer at Zellbox

Nacho founded Zellbox to give appointment-driven small businesses — clinics, salons, spas, physio, aesthetics, vets, mental-health, and fitness studios — a WhatsApp-first calendar and customer record system. Writes about WhatsApp Business automation, no-show economics, recall-cycle playbooks, and the operational realities of running visit-driven businesses at scale.

Related Posts

View All Posts »