Resources · Make integration

Z-API Make integrationAutomate Z-API with Make.

Can Make send your WhatsApp messages through Z-API while you work on something else? The Z-API Make integration gives you 48 modules: 43 actions and 5 searches. This guide shows how to link your instance and build a first scenario that sends a text.

Try the Z-API integration on MakeSee the 48 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Z-API Make integration do for you?

The Z-API Make integration lets Make drive your WhatsApp Business number through Z-API: send messages, look up contacts, handle chats, groups, status posts, catalog products and the message queue. You build a scenario, which is the automation Make runs, out of modules, which are its single steps, and no code is involved.

Confirmations that leave on their own. A booking lands in your calendar tool, Make checks the number with Contact Phone Exists, then Send a Text Message or Send a Document delivers the details to the customer.

Groups that stay tidy. A support team can open a group per project with Create a Group, bring people in with Add a Group Participant and set the tone with Update a Group Description, all from one scenario.

A catalog that matches your stock. A small shop can keep its WhatsApp Business catalog in line with its product sheet through Create/Update a Product and Delete a Product.

What Make does not do with this app: Z-API has no trigger module in Make, so Z-API itself never starts a scenario. Something else does, a trigger from another app or the scenario schedule. The official documentation also gives no numeric limit for this app. If your team already works in n8n, the n8n vs Make comparison helps you pick a side, Make training covers the editor from the start, and Make pricing explains how operations are counted.

Connect

How do you connect Z-API to Make?

  1. 01

    Create a web instance in Z-API

    In your Z-API account, open Web Instances in the left sidebar, click + Add, name the instance and click Save. Copy the Instance ID and the Instance token and keep them somewhere safe.

  2. 02

    Generate the Client Token

    Still in Z-API, open Security, then click Configure now next to Account Security Token. Pick how to confirm, type the code you receive, and copy the Client Token. That makes three values in hand.

  3. 03

    Paste the three values in Make

    Add any Z-API module to your scenario and click Create a connection. Fill Name, then Instance ID, Token ID with the instance token and Client Token, and click Save. Every Z-API module reuses this connection afterwards.

First scenario

Your first scenario: a WhatsApp text when a lead arrives

GoalWhen a new lead shows up in another app, Make sends that person a WhatsApp text through Z-API.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module is the trigger of the app that holds your leads, since Z-API has none.

  2. 02

    Add Send a Text Message

    Click the + on the right of that first module, search for Z-API and pick Send a Text Message. Select the connection you created, or click Create a connection if this is your first Z-API module.

  3. 03

    Map the number and the text

    Fill the module fields by mapping data from the first module: the lead's phone number and a short message that uses the lead's name. Each bundle, meaning each lead, becomes one text.

  4. 04

    Test with Run once

    Click Run once and create a test lead with your own number. Read the bundles each module received, then check that the text reached your phone.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module that runs counts as one operation on your Make plan.

Modules

What the Z-API modules do

Z-API gives you 48 modules in 9 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Contacts

4 modules
Z-API1

List Contacts

Search

In Make“Lists all Whatsapp contacts.”

You get every contact of the connected WhatsApp number, each one as its own bundle, ready to feed the next module or a spreadsheet.

When to use it
building a first export of your WhatsApp address book to clean it up in another tool.
Watch out
as a search, it can return many bundles, and every module placed after it runs once per contact, so operations add up fast.
Z-API2

Get a Contact Profile Picture

Action

In Make“Gets the URL with the updated profile picture.”

This one hands back a link to the current profile photo of a WhatsApp contact, which you can store next to the person's record.

When to use it
enriching a CRM card with a face when a new customer is added to it, so your team recognizes who they talk to.
Watch out
you receive a URL, not the image file itself, so map it into a field that accepts links.
Z-API3

Get a Contact Metadata

Action

In Make“Gets the contact metadata.”

Pulls the details Z-API holds about one contact, so the rest of the scenario can work with more than a bare phone number.

When to use it
before creating a record in another app, to fill it with what WhatsApp already knows about the person.
Watch out
run it on one known number at a time; for a whole address book, List Contacts is the better start.
Z-API4

Contact Phone Exists

Action

In Make“Returns whether the number has Whatsapp or not.”

Tells you whether a phone number has WhatsApp, before you spend an operation sending anything to it.

When to use it
right after a form submission, to decide between a WhatsApp message and an email for that lead.
Watch out
the module only answers yes or no; the scenario still needs a later step that reads the answer and chooses the channel, otherwise the message goes out anyway.

Message

15 modules
Z-API5

Send a Text Message

Action

In Make“Sends a text message.”

The workhorse of the app: a plain WhatsApp text goes out from your number to the chat you point it at.

When to use it
order confirmations, appointment reminders tied to a booking, or a quick hello when a lead fills a form.
Watch out
test with Run once on your own number first, because a text sent to a real customer cannot be pulled back by the scenario.
Z-API6

Send PIX Button

Action

In Make“Send PIX key messages with a button to copy.”

Sends a message carrying a PIX key with a button the recipient taps to copy it, so paying does not start with retyping a long key.

When to use it
once an order or invoice is validated in your sales tool, to hand the customer the key in the same chat.
Watch out
keep the key in one mapped value you control, since a typo here sends money to the wrong place.
Z-API7

Send an Audio

Action

In Make“Sends an audio to your chat.”

Drops an audio clip into a WhatsApp chat, handy when a voice explains better than a paragraph of text.

When to use it
a recorded welcome or a spoken how-to that goes out when a customer signs up.
Watch out
the audio has to come from somewhere the scenario can reach, usually an earlier module that downloads or points to the file, so plan that step first.
Z-API8

Send an Image

Action

In Make“Sends an image to your chat.”

Puts a picture in the chat: a product shot, a receipt, a floor plan, whatever the previous module provides.

When to use it
showing a customer the item they just ordered or the proof of a delivery the moment it is logged.
Watch out
on the Make Free plan, files are capped at 5 MB, so heavy photos may need resizing before they reach this module.
Z-API9

Send a Location

Action

In Make“Sends a location to your chat.”

Shares a map pin in the chat, so the recipient opens directions instead of copying an address by hand.

When to use it
after a booking, to send the exact meeting point, a pickup counter or the site of an intervention.
Watch out
store the location once in the source app and map it here, rather than typing it into the module where nobody will think to update it.
Z-API10

Send a Document

Action

In Make“Sends a document to your chat.”

Delivers a file such as a quote, a contract or an invoice straight into the customer's WhatsApp chat.

When to use it
when your billing tool generates a PDF, so the customer gets it where they actually read messages.
Watch out
the Free plan caps files at 5 MB and 512 MB of data transfer, so a scenario that ships many documents can hit that ceiling.
Z-API11

Send a Button List

Action

In Make“Sends a button list to your chat.”

Gives the recipient a message with buttons to tap, which turns a vague question into a clear choice.

When to use it
confirming or cancelling an appointment, or asking a customer to rate a delivery with one tap.
Watch out
Z-API has no trigger in Make, so catching which button was tapped needs another route, not this scenario.
Z-API12

Send a Sticker

Action

In Make“Sends a sticker to your chat.”

Sends a sticker to the chat, the light touch that makes an automated message feel less robotic.

When to use it
a thank-you after a payment or a small celebration when a customer hits a milestone in your app.
Watch out
pair it with a real text; a sticker alone rarely tells the customer why they received it.
Z-API13

Send a Video

Action

In Make“Sends a video to your chat.”

Pushes a video clip into the chat, useful when a demonstration beats any written instruction.

When to use it
an unboxing or setup tutorial sent when an order ships, or a short product preview after a quote request.
Watch out
video files grow quickly, and the Free plan stops at 5 MB per file, so keep clips short or move to a paid plan.
Z-API15

Send a Contact

Action

In Make“Sends a contact to your chat.”

Passes a contact card into the chat, so the recipient saves the right person with one tap.

When to use it
introducing the account manager assigned to a new client, or the technician coming on site.
Watch out
the card comes from the data you map; if the source record is outdated, the customer saves a wrong number.
Z-API16

Send an Option List

Action

In Make“Sends an options list to your chat.”

Offers a list of options in one message, a tidier alternative to buttons when there are more choices on the table.

When to use it
letting a customer pick a delivery slot or a service from a menu instead of typing an answer.
Watch out
like the button list, the reply does not come back into Make through Z-API, so plan how answers are read.
Z-API17

Read a Message

Action

In Make“This module marks a chat message as readed.”

Marks a message as read, so the chat stops showing it as waiting on your side.

When to use it
after a scenario has copied an incoming message into your helpdesk, to keep the WhatsApp inbox in line with reality.
Watch out
place it after the step that stores or handles the message, never before, or unread work can slip through.
Z-API18

Reply a Message

Action

In Make“Replys a message.”

Answers a specific message in a chat, so the answer is tied to the question it responds to.

When to use it
a customer asked several things and each answer must sit under the matching question.
Watch out
the module needs to know which message it replies to, so that reference must come from an earlier step in the scenario.
Z-API19

Delete a Message

Action

In Make“Deletes a message.”

Removes a message from a chat, cleaning up something that should never have gone out.

When to use it
withdrawing an offer that was sent with a wrong price, right after the mistake is flagged in your back office.
Watch out
a delete cannot be undone by the scenario, so test it on your own chat before letting it touch customer conversations.

Instance

3 modules
Z-API20

QR Code Status

Action

In Make“Reads a QR code.”

Reads the QR code of your Z-API instance, the one used to link a phone to it.

When to use it
building a small admin scenario that sends the code to the person in charge when the phone needs to be linked again.
Watch out
this code is how a phone gets linked to your instance, so send it only to a private channel.
Z-API21

Disconnect Phone

Action

In Make“Disconnects your number from Z-API platform.”

Unlinks your number from the Z-API platform, which stops every message scenario that relies on it.

When to use it
an offboarding flow, when the device behind the number is handed back or replaced.
Watch out
treat it as a deliberate, rare step; placing it in a scenario that runs often cuts your WhatsApp automations until the phone is linked again.
Z-API22

Get Device Data

Action

In Make“Gets the device data.”

Returns information about the device linked to your instance, a quick health check before any message goes out.

When to use it
a monitoring scenario that writes the device state into a sheet or alerts the team in a chat tool.
Watch out
it reports, it does not fix; pair it with QR Code Status if relinking is the next step.

Chat

4 modules
Z-API23

Archive a Chat

Action

In Make“Archives and unarchives a chat.”

Archives a chat, or brings it back out of the archive, so the main list only shows conversations that still need you.

When to use it
once a ticket is closed in your helpdesk, to move the matching WhatsApp chat out of sight.
Watch out
the same module does both directions, so check which one you set before running it on real chats.
Z-API24

Delete a Chat

Action

In Make“Deletes a chat.”

Wipes a whole conversation from the linked number, a stronger move than archiving.

When to use it
honoring a data deletion request logged in your CRM for a contact who wants no trace left.
Watch out
there is no way back from inside Make, so prefer Archive a Chat whenever you may need the history later.
Z-API25

List Chats

Search

In Make“Lists all chats.”

Brings out every chat of the number, one bundle per conversation, for reporting or bulk tidying.

When to use it
feeding a sheet that shows who you talk to, or finding the chats to archive in one pass.
Watch out
a busy number returns plenty of chats, and each module after this search runs for every single one of them.
Z-API26

Pin Chat

Action

In Make“This module pins or unpins a chat.”

Pins a chat to the top of the list, or unpins it, so priority conversations stay in view.

When to use it
when a deal moves to a key stage in your CRM, to keep that customer's chat at the top for the sales rep.
Watch out
the same module also unpins, so add a second Pin Chat set to unpin when the deal closes, or the top of the list fills up.

Group

12 modules
Z-API27

Create a Group

Action

In Make“Creates a group.”

Starts a new WhatsApp group from the scenario, ready to be named, filled and configured by the next modules.

When to use it
opening a dedicated group per new client project as soon as it is signed in your project tool.
Watch out
run a test first; a scenario that fires twice on the same record opens two groups with the same people.
Z-API28

Add a Group Participant

Action

In Make“Adds a new group participant.”

Brings a phone number into an existing group, without anyone opening WhatsApp to invite them.

When to use it
adding each new student to the cohort group when their enrollment is paid.
Watch out
check the number with Contact Phone Exists beforehand, since a number without WhatsApp cannot join.
Z-API29

Remove a Group Participant

Action

In Make“Removes a group participant.”

Takes a number out of a group, the mirror step of adding one.

When to use it
a membership ends or an employee leaves, and access to the group should end with it.
Watch out
map the number from the source record rather than typing it, so the scenario never removes the wrong member.
Z-API30

Add an Admin

Action

In Make“Gives admin permissions to a phone number.”

Promotes a group member to admin, giving that number the rights to manage the group.

When to use it
a new team lead is assigned to a client group and should be able to add people without asking.
Watch out
the number must already be in the group, so place Add a Group Participant before this module when needed.
Z-API31

Remove an Admin

Action

In Make“Removes admin permissions from a phone number.”

Withdraws admin rights from a number while leaving that person in the group as a regular member.

When to use it
a coordinator hands over a project and keeps following the chat without managing it.
Watch out
run Get a Group Metadata first if you are unsure who holds admin rights, so the scenario does not strip the wrong person.
Z-API32

Get a Group Invitation Metadata

Action

In Make“Gets a group invitation metadata.”

Reads the information behind a group invitation, so the scenario knows which group a link leads to before acting on it.

When to use it
checking an invitation shared in a form or a ticket before your team joins or forwards it.
Watch out
it only reads; joining or sharing the group is a separate step.
Z-API33

Get a Group Metadata

Action

In Make“Gets a group metadata.”

Fetches what Z-API knows about one group, so the next steps work from the group's current details instead of guesses.

When to use it
auditing a client group before a scenario renames it or changes its settings.
Watch out
the output describes a single group; if you manage dozens, start from List Chats and run this once per group, one operation each.
Z-API34

Update a Group Settings

Action

In Make“Updates the group settings.”

Changes how a group behaves, applying the same rules to every group your scenario creates.

When to use it
right after Create a Group, to set the group up the way your team always does by hand.
Watch out
try the settings on a test group first, as a wrong choice applies to everyone inside it straight away.
Z-API35

Leave a Group

Action

In Make“Leaves a group.”

Makes your linked number quit a group, for when your business no longer belongs in the conversation.

When to use it
a project is archived in your tool and the WhatsApp group tied to it should be left behind.
Watch out
leaving is hard to undo from Make, so hand admin rights to a colleague with Add an Admin before this step.
Z-API36

Update a Group Description

Action

In Make“Updates the group description.”

Rewrites the description of a group, the place members check for rules, links and contacts.

When to use it
when the project's key dates or the support contact change in your tool, so the group always shows the current info.
Watch out
map the whole description from your source each time, so a partial field never ends up as the group text.
Z-API37

Update a Group Image

Action

In Make“Updates the group image.”

Sets a new picture on a group, which makes a client group easy to spot in a crowded chat list.

When to use it
after Create a Group, to apply the client's logo taken from the CRM record.
Watch out
the image must be reachable by the scenario, usually from a previous module, and the Free plan caps files at 5 MB.
Z-API38

Update a Group Name

Action

In Make“Updates the group name.”

Renames a group from the scenario, keeping names consistent across every project your team runs.

When to use it
a deal changes stage or a project is renamed in your tool, and the group title should follow.
Watch out
each rename is one more operation, so start the scenario on a real name change, not on every small edit of the record.

Status

2 modules
Z-API39

Post a Status Image

Action

In Make“Post an image on status.”

Publishes an image to your WhatsApp status, seen by the contacts who follow your updates.

When to use it
a new product lands in your shop and its photo should appear in your status without anyone posting it by hand.
Watch out
a status reaches all your contacts at once, so keep a review step before anything reaches it.
Z-API40

Post a Status Text

Action

In Make“Post a text on status.”

Posts a short text to your WhatsApp status, the lightest way to broadcast news to your contacts.

When to use it
announcing closed hours or a restock the moment it is entered in your planning tool.
Watch out
unlike a message, a status has no single recipient, so double-check wording before the scenario goes live.

Product

5 modules
Z-API41

Create/Update a Product

Action

In Make“Creates or edits a product.”

Adds a product to your WhatsApp Business catalog or updates one already there, without opening the phone app. One module covers both cases.

When to use it
a new reference goes live in your online store or spreadsheet and should also be offered to customers who shop through WhatsApp.
Watch out
map the values from the previous module rather than typing them, otherwise every run pushes the same product.
Z-API42

Delete a Product

Action

In Make“Deletes a product.”

Takes an item out of your WhatsApp Business catalog, so customers stop seeing something you no longer sell.

When to use it
an item is marked as retired in your stock sheet and the catalog should follow without anyone remembering to clean it up.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a dummy product before you switch the scenario on.
Z-API43

Get a Product

Search

In Make“Gets a product by id.”

Returns one catalog entry from its product ID, ready for the next modules to read. It is the direct lookup when you already know which item you mean.

When to use it
another tool stores the Z-API product ID next to an order, and you want the current catalog details before replying to the buyer.
Watch out
it is a search module, so an unknown ID simply returns nothing; add a filter so the scenario does not send an empty reply.
Z-API44

Get a Product by Phone

Action

In Make“Gets a product by phone number.”

Starts from a phone number instead of an ID and brings back the product data tied to it. Handy when the number is the only reference you have.

When to use it
a scenario begins with a WhatsApp number from a form or a CRM, and you need to see what that account offers in its catalog.
Watch out
if you already hold the product ID, Get a Product is the more direct choice.
Z-API45

List Products

Search

In Make“List products from whatsapp business catalog.”

Pulls the whole WhatsApp Business catalog into your scenario, each product as its own bundle. From there you can copy, compare or report on it.

When to use it
you keep a spreadsheet or database in step with what customers can actually order on WhatsApp.
Watch out
every product that comes out feeds the next modules, and each of their runs is an operation counted on your plan.

Queue

2 modules
Z-API46

Delete Queue Messages

Action

In Make“Deletes all messages in queue.”

Clears every message waiting in the queue of your Z-API instance in one go. It acts on the whole queue, not on a message you pick.

When to use it
a campaign was loaded by mistake or with the wrong text, and nothing still waiting should reach your contacts.
Watch out
nothing is kept aside; read the queue first with Get a Queue Messages if you need a trace of what gets removed.
Z-API47

Get a Queue Messages

Search

In Make“Gets all messages in queue.”

Shows what your Z-API instance still holds in its queue, each message as a separate bundle you can log or alert on.

When to use it
a customer says a message never arrived and your support team wants to check whether it is still stuck on the Z-API side.
Watch out
an empty queue returns no bundle at all, so the modules after it will not run on that execution.

Other

1 module
Z-API48

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Z-API API when no listed module does what you need, reusing the connection you already set up. No second login.

When to use it
your Z-API account offers a feature that has no dedicated module in Make yet, and the rest of the scenario is already built.
Watch out
you write the request yourself, so keep the Z-API documentation open next to the module.
Need help

Need help automating Z-API with Make?

A person reads every message.

FAQ

Z-API and Make: common questions

01Is the Z-API Make integration free?
Yes, on the Make side. Z-API is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits, one operation each time a module runs. The price of Z-API itself is not covered by this page.
02What do you need to connect Z-API to Make?
A Z-API account and three values from it. In Z-API, create a web instance under Web Instances and copy its Instance ID and Instance token. Then open Security and generate the Client Token from Account Security Token. In Make, add a Z-API module, click Create a connection, paste the Instance ID, the instance token in the Token ID field, and the Client Token, then save. If Z-API asks you to authenticate and confirm access, accept. The same connection then serves all 48 modules of the app.
03Does Z-API have a trigger that starts Make scenarios?
No. The Z-API app lists no trigger module in Make, only 43 actions and 5 searches. A Z-API scenario therefore starts elsewhere: on a trigger from another app, such as a new form entry or a new CRM record, or on the scenario schedule, which checks every 15 minutes by default and down to 1 minute on paid plans. Z-API sends messages, updates groups or reads chats once that first module has fired, which is the pattern of the first scenario above.
04What if a Z-API module you need is missing in Make?
Use Make an API Call. This module ships with the Z-API app and calls any endpoint of the Z-API API with the connection you already set up, so you are not limited to the other modules listed on this page. You need the Z-API API documentation to know which endpoint to call and what it expects. The official Make documentation lists no numeric limit for this app, so check on the Z-API side whether any cap applies before sending large batches.
05Should you use Make or n8n for Z-API?
It depends on where your automations already live. Make gives you 48 ready Z-API modules, a visual editor and a guided first scenario like the one on this page. The same app often has an n8n node as well, so a team that already runs its workflows in n8n can check there before adding a second tool. Neither choice is better by default: pick the platform your team knows, and compare how each one counts usage against your volume of messages.
Same platform

Other docs you might need on this stack.

Browse all integrations