Automation integration
Native connector coming soonMake + WhatsApp via InfiQ
Make's visual scenarios and the InfiQ API are a natural pair — branch on customer data, iterate over order lines and schedule sends, all without a line of backend code.
How the data flows
Make
your system
InfiQ
rules + templates
You're all set! We'll keep you posted right here on WhatsApp.
✓✓
delivered · read
Live syncWhy connect
What syncing Make unlocks
Four flows teams typically wire up first when Make starts talking to WhatsApp.
Visual scenarios, real logic
Design WhatsApp flows on Make's canvas: routers branch by segment, filters gate by value, and the HTTP module calls the InfiQ API at each step.
Complex, multi-app flows
Combine your store, CRM and sheet in one scenario — enrich a lead, decide the right template, send it, then log the outcome, in a single run.
Two-way via webhooks
Make's custom webhook module receives InfiQ events — inbound messages, delivery states — so replies can drive the next branch of your scenario.
Batching and scheduling
Run scenarios on a schedule for digest-style updates, or use iterators to process a day's orders into individual, personalised messages.
How it works today
Connect today with webhooks and the REST API
No waiting on a connector: Make and InfiQ can talk today over the same rails the native integration will use.
- 1
Create your API credentials
Sign in to the InfiQ dashboard and generate a scoped API key — it takes about a minute.
- 2
Wire Make events to InfiQ
Point Make's webhooks or automation layer at the InfiQ REST API, and subscribe to InfiQ webhooks for replies and delivery states.
- 3
Send approved templates
Trigger pre-approved WhatsApp templates with live data, and handle inbound replies in the shared team inbox or your own system.
Example flows
- New row in a database → router by city → localised template via the InfiQ API
- InfiQ inbound webhook → Make scenario → CRM update + assignment + auto-reply
- Nightly schedule → iterate pending invoices → payment reminder per customer
Endpoint references, payload examples and sandbox keys are in the developer docs.
Native Make integration
A verified InfiQ app on Make with ready-made modules — send template, add contact, watch messages — replacing hand-built HTTP calls with dropdown configuration and built-in authentication.
Native integration coming soon — connect today via webhooks and the REST API. Flows you build now carry over unchanged when the connector ships: it replaces the wiring, not your templates or automations.
Where it fits
Teams that pair Make with WhatsApp
See how businesses in these industries run the flows above end to end on InfiQ.
Related
Where this integration fits
FAQ
Make integration — common questions
Is the Make integration available now?
You can build scenarios today using Make's HTTP and custom webhook modules with the InfiQ REST API — that path is fully supported. A verified InfiQ app with prebuilt Make modules is coming soon.
What can I automate between Make and WhatsApp?
Order and payment notifications with branching logic, lead nurture flows that react to replies, scheduled reminder runs over spreadsheets or databases, and inbound WhatsApp events fanning out to CRMs, helpdesks and chat tools.
Do I need developers to set this up?
Not necessarily. Make's HTTP module is configured visually; you paste the InfiQ endpoint and key from your dashboard. It helps to be comfortable with JSON for template variables — our docs at /developers have copy-paste bodies for the common calls.
When is the verified Make app coming?
It is part of our native connector rollout and we do not commit to dates we cannot keep. Scenarios built on the HTTP module today are safe — the app adds convenience, not a migration.
Put Make on WhatsApp this week.
Start with the API today and switch to the native connector when it lands. Our team will map the flow in a 20-minute call.