LandinChat
WhatsApp + Make

WhatsApp Make (Integromat) integration — visual WhatsApp automation at scale

Use LandinChat inside any Make scenario to send WhatsApp messages, listen to inbound replies and chain together 1,500+ apps with branching, loops and error handling.

Last updated: June 2026 · Automation

In short: Make is the power-user's automation tool. LandinChat plugs in as a first-class app so you can build advanced WhatsApp scenarios visually.
1,500+
Apps via Make
Visual
Scenario builder
Native
Make app
Official
Meta Tech Partner
What you can do

Top WhatsApp + Make (Integromat) use cases

Pre-built playbooks brands run on day one of the Make (Integromat) integration.

Complex multi-app flows

Branch a Make scenario on WhatsApp replies and update CRM, Sheets and Slack in one go.

Inbound WhatsApp → CRM

Listen to new WhatsApp messages, enrich with an API, then create a CRM lead.

Scheduled broadcasts from a DB

Pull contacts from a database (Postgres, MySQL, Airtable) and broadcast on a schedule.

Document parsing

Parse PDFs or invoices in Make and send the summary back on WhatsApp.

AI-powered replies

Combine LandinChat with OpenAI or Anthropic modules to draft AI replies on WhatsApp.

Error handling at scale

Use Make's retry and rollback logic to make WhatsApp scenarios production-grade.

What's inside

Everything the Make (Integromat) integration covers

  • Native LandinChat app inside Make
  • Instant triggers for inbound WhatsApp, new contact, flow completed
  • Action modules for send template, add to list, trigger flow, update contact
  • Iterator, Aggregator and Router modules fully supported
  • Error handlers with retry and rollback
  • Works with Make HTTP and Webhooks modules for custom events
  • Scenarios scale to thousands of operations per minute
  • Conversation data available for downstream apps
Triggers & actions

Events that fire WhatsApp messages

Triggers (from Make (Integromat))
  • Inbound WhatsApp message (instant)
  • New WhatsApp contact
  • Chatbot flow completed
  • Broadcast sent or delivered
  • Conversation tagged or assigned
Actions (in LandinChat)
  • Send WhatsApp template message
  • Send free-form WhatsApp message (in 24-hour window)
  • Add or update a LandinChat contact
  • Add contact to a broadcast list or segment
  • Trigger a no-code chatbot flow
Setup

How to connect Make (Integromat) with WhatsApp via LandinChat

  1. Step 1

    Open Make

    Search 'LandinChat' inside Make — the public app is listed in the catalog.

  2. Step 2

    Connect your workspace

    Authenticate with your LandinChat API key.

  3. Step 3

    Build a scenario

    Drag triggers and actions visually onto the scenario canvas.

  4. Step 4

    Add routers & iterators

    Branch on conditions and loop over arrays of contacts or messages.

  5. Step 5

    Schedule it

    Run on-demand, on a schedule, or instantly on inbound WhatsApp events.

Why teams choose it

Benefits of running Make (Integromat) on LandinChat

Power-user automation

Iterators, routers, error handlers — everything Zapier can't.

Production-grade scenarios

Built-in retry and rollback for safe at-scale automation.

Visual debugging

Inspect every operation step-by-step inside Make.

Unlimited agents

Shared inbox without per-seat fees.

Deep dive

The complete guide to WhatsApp + Make (Integromat)

Make (Integromat) for visual WhatsApp automation

Make's visual scenario builder is unbeatable for branching, looping and data-shaping workflows that would take 5 Zaps to express. LandinChat publishes a verified Make app with the same triggers and actions as the Zapier app, plus richer module-level field control for power users.

Common Make + WhatsApp scenarios

Airtable record updated → iterate over related records → send personalised WhatsApp template per row. Webhook from a custom app → router by region → send WhatsApp template in the right language. Google Calendar event 1 hr away → fetch attendees → WhatsApp reminder with custom merge fields. None of these need code; Make's visual flow makes them obvious.

Make vs. Zapier vs. native LandinChat

Use native integrations (Shopify, WooCommerce, HubSpot, Zoho, Razorpay, Shiprocket) for the high-volume systems — they're faster and cheaper. Use Make for complex multi-step branching, iterators and data-shaping. Use Zapier for simple two-step automations and apps Make doesn't cover.

Proof

Why WhatsApp + Make (Integromat) works

2,000+
Apps reachable from LandinChat via the Make app
Source: Make marketplace, 2025
1,000 ops/min
Make's per-scenario throughput — sufficient for most WhatsApp broadcast use cases
Source: Make documentation, 2025
95%+
WhatsApp Business API open rate within 3 minutes
Source: Meta Business benchmarks, 2025
Honest take

Where the Make (Integromat) integration shines — and where to plan ahead

Pros
  • Verified Make app — appears in Make's marketplace
  • Bi-directional triggers and actions
  • Iterators and routers support complex branching that's painful in Zapier
  • No additional LandinChat per-operation fee
  • Works on every Make plan including Free
Watch out for
  • Make itself counts operations against your Make plan limit
  • For high-volume systems (Shopify, HubSpot, Zoho) the native LandinChat integration is faster and cheaper
Pricing notes

LandinChat does not charge per scenario or per operation — you pay your normal Make subscription plus your LandinChat monthly platform fee. Meta WhatsApp conversation fees pass through at cost.

Glossary

Make (Integromat) + WhatsApp terms, explained

Scenario
A Make automation, equivalent to a Zap but visual and supporting branches, loops and routers.
Operation
A unit Make counts toward your plan. Each LandinChat WhatsApp send through Make consumes one operation.
Router
A Make module that branches a scenario into multiple paths based on conditions.
Iterator
A Make module that loops over an array. Useful for sending WhatsApp messages to multiple recipients from a single trigger.

Make + LandinChat replaced a tangle of Apps Scripts and webhooks. The visual scenario for our event-reminder flow now shows the whole journey on one canvas — iterators, routers, error handlers — and the WhatsApp send is just another module.

Elena Costa, Automation Lead, a global event-ops agency
FAQs

Make (Integromat) + WhatsApp — frequently asked questions

Is the LandinChat Make app publicly available?

Yes — search 'LandinChat' in the Make app catalog. No private invite required.

What Make plan do I need?

Any Make plan works, including Free for simple scenarios. Higher tiers unlock more operations per month and faster polling.

Can I listen to inbound WhatsApp messages in Make?

Yes — 'New inbound message' is an instant trigger via webhook.

Does Make support multi-step WhatsApp flows?

Yes — scenarios can chain dozens of modules with Routers, Iterators, Aggregators and HTTP calls.

Can I use the OpenAI or Anthropic Make modules with WhatsApp?

Yes — combine LandinChat with any AI module in Make to draft, classify or summarize WhatsApp messages.

Is this on the official WhatsApp Business API?

Yes — LandinChat is an Official Meta Tech Partner. All messages are sent on Meta-approved WhatsApp Business API templates.

Will scenarios respect WhatsApp's 24-hour window?

Yes — free-form messages are only sent inside the 24-hour customer service window; outside it, only approved templates can be used.

How does pricing work?

Make pricing is separate. LandinChat is one transparent monthly plan with unlimited agents; Meta conversation fees are passed through at cost.

Is the LandinChat Make app verified or community-built?

It's a fully verified Make app, published by LandinChat and listed in Make's official marketplace. No private repo or self-hosted module required.

Does it support Make's iterators and routers?

Yes — the LandinChat action modules are designed to work cleanly inside iterators (for per-row broadcasts) and routers (for branching by contact attributes, language or region).

Can I trigger a Make scenario from an incoming WhatsApp message?

Yes — the LandinChat 'Watch messages' trigger fires on every inbound WhatsApp message with the contact, body, media URL and any quick-reply button payload exposed as separate variables.

How do I handle errors and retries?

Use Make's built-in error handler routes on the LandinChat module. Common patterns: retry on Meta rate-limit, fall back to a Utility template if a Marketing template is rejected, and notify a Slack channel on permanent failures.

Start replying to customers in seconds
— set up by tomorrow.

Join 500+ businesses worldwide using LandinChat to reply faster, sell more, and never miss a customer on WhatsApp.

Official Meta Tech Partner GDPR · ISO 27001 Cancel anytime