> For the complete documentation index, see [llms.txt](https://support.whapi.cloud/help-desk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.whapi.cloud/help-desk/integrations/make.com.md). # Make.com Make is a visual platform that allows you to automate tasks without programming skills by connecting different applications to each other. The automated processes created in Make are called Scenarios. {% embed url="" %} We have implemented an integration application that will help you automate WhatsApp, for example, to send messages to groups or WhatsApp channels. To use it, you will need to have a token in our service. You can read more about how to get it in the article: [Getting Started](/help-desk/getting-started/welcome-to-whapi.cloud.md) *** {% embed url="" %} ## Connecting Whapi.Cloud to Make.com There are several ways to take advantage of the integration within the Make service: * When creating a scenario, enter the name of our service Whapi.Cloud in the action search

When creating a scenario, enter the name of our service Whapi.Cloud in the action search

or * Install our application in Make via a direct link: [Install app](https://www.make.com/en/hq/app-invitation/be2f8b5ba4979970f8a13d85eb6aaaec)

*** ## Creating a scenario Scenario is an automated process created in Make. Each scenario consists of a trigger and an action. When a trigger is fired in one application, an action is automatically executed in the other application.

On the scenarios page, click "Create a new scenario" to create a new scenario

To automatically activate your scenario, you must first configure **a trigger** (to activate the scenario when you receive a message) and then configure the appropriate **action** (to automatically send the message).

Creating scenarios is pretty easy. Select the desired application combinations and choose the appropriate actions.

## Creating Trigger: Receiving messages A trigger is an event that triggers your scenario. For example, it could be a new message in WhatsApp, a new entry in Google Sheets, or something else. List of existing triggers at Whapi.Cloud: 1. **Watch Group Participants:** Watch Group Participants Actions , like join group or leave group; 2. **Watch Messages:** Triggers for new message events; 3. **Watch New Call:** Triggers when a new call is received; 4. **Watch New Conversation:** Trigger called, when new conversation created; When you use the Watch Messages trigger, we will automatically set Webhook in your channel settings. In other triggers, you will have to do it yourself. To learn how exactly to set a webhook on your channel, see the article: [Webhooks](/help-desk/receiving/webhooks.md#webhooks-management) {% hint style="info" %} In Make, the methods for the trigger are marked with the ACID tag. In our case, the triggers are methods for receiving a message. {% endhint %}

On the `Create a webhook` window, click `add` to add a connection. Insert your channel token from the Whapi.Cloud dashboard

## Creating Actions: Sending a message To send a message, you need to configure **an action** in Make. Add actions that should be performed after the trigger occurs. These can be sending messages, filling cells, updating data, or other actions in other applications or services. Customizing the action should be done after configuring the trigger so that messages are sent automatically after the event is triggered. {% hint style="info" %} It is also possible to configure only the action, without a trigger. However, in this case, you will need to run the scenario yourself. {% endhint %} **List of existing actions at Whapi.Cloud:** * **Send Text Message.** Sends a Text Message to the specific contact, group chat or your channel. * **Send Media Message.** This method allows you to send media messages to a simple dialog, group chat, or your channel. (Available for sending: `image / video / gif / audio / voice / document / sticker`). * **Make an API Call.** Performs an arbitrary authorized API call. A universal method that will allow you to perform any function from our documentation.

Example of sending a media message to a number when you miss a call on WhatsApp

Make a test by clicking the Run once button. If the test is successful, click on the magnifying glass to see the details of the result of the action.

Done! The simplest scenario is set up and ready to use! We can't wait to see what results you achieve. ### Custom call of any API function If you need to use any other function that has not been added by us to the finished actions, then you will need action "Make an API Call". To use it, copy the request method (POST/GET/DELETE) from our [documentation](https://whapi.readme.io/reference/createstory), as well as the parameters for the request. This way you can automate any API method. In the *URL* field, you need to add an endpoint (without specifying the full API URL). For example it could be: /newsletters, /groups, /stories, etc. You can look up the endpoint in our documentation:

In the *Method* field, all you have to do is specify the request method (POST/PUT/GET/DELETE) In *Body*, it remains to specify the request parameters in JSON format. It is most convenient to copy them from our [documentation](https://whapi.readme.io/reference/sendmessagetext).

This is a very convenient and flexible way to automate any functionality!

### Detailed example Let's send a poll to a channel for an example. We need a `POST /messages/poll` endpoint, in the Developer Hub it can be found at: . So, we already know what we need to fill in the URL field, we take this snippet "**/messages/poll**" from the endpoint, and change the request type to **POST**.

Initially, we define for Make which request will be executed.

Now our task is to specify the parameters of this request. The easiest way is to fill them in the Developer's Hub, and then simply transfer them to Make by copying the text.

Copy the resulting text, taking into account the brackets

Paste the copied fragment into the "Body" field

All set, run the scenario! ### Using Transform JSON Block in Make When manually forming the body of a request in Make, serialization errors may occur due to incorrect line breaks (\n) or quotes inside the text. This is especially true when sending formatted messages in WhatsApp. To avoid such problems, we recommend using the Transform JSON Block module . It automatically handles special characters and formats the text according to API requirements. Advantages of using a JSON block: * Line breaks are set by pressing Enter (Make will insert \n automatically) * Correct escaping of quotes and symbols * Support for WhatsApp formatting (bold, italic, strikethrough)

This approach makes the integration more stable and reduces the number of errors when sending messages. Need help getting started? We will tell you exactly how to create the scenario you need or help you find a mistake. Our support team is always here to assist you. ## Make.com WhatsApp Bot Template A ready-made Make.com scenario that shows how to build a simple WhatsApp bot using the Whapi Cloud API. ### What It Does The scenario listens for incoming WhatsApp messages via a Whapi webhook and auto-replies based on the message text. A **Router** with a built-in filter ensures the bot only reacts to **incoming messages** — your own outgoing messages are ignored, preventing loops.(The scenario will not respond to messages to itself.) The router then splits the flow into three routes, each demonstrating a different way to send a reply: | Send `1` | **HTTP Request + API Key** — full manual control over the request | | -------- | --------------------------------------------------------------------------------------------------------------------------------- | | Send `2` | **JSON Transform + HTTP Request** — builds a multi-line formatted message (bold, italic, links) in a separate step, then sends it | | Send `3` | **Whapi Cloud native module** — simplest option, auth and base URL are handled automatically | All three routes do the same thing (send a text reply to the sender) but let you compare approaches and pick the one that fits your use case. ### How to Import {% file src="/https/support.whapi.cloud/files/LSFmjItmQZ42hm9OCWa6" %} 1. Download the `example_blueprint.json` file 2. In Make.com, go to **Scenarios → Create a new scenario** 3. Click the **⋯** menu at the bottom → **Import Blueprint** → upload the file 4. Set up connections: * **Whapi Cloud connection** — click the trigger module, create a connection with your API token from [panel.whapi.cloud](https://panel.whapi.cloud/) * **API Key** (for HTTP modules) — add a Credentials entry with header `Authorization`\ and Key `Bearer YOUR_API_TOKEN` 5. Click **Run once**, send `1`, `2`, or `3` to your WhatsApp number, and check the reply --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://support.whapi.cloud/help-desk/integrations/make.com.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.