TL;DR
Make.com is a no-code automation platform that lets you connect Mumble to thousands of other apps – Google Sheets, Gmail, Shopify, HubSpot, Salesforce, Stripe, Calendly, and more. With a simple connection using an API key, you can build a scenario where an event in one app automatically triggers an action in Mumble – sending a message, creating a customer, adding to a list, and more.
Initial Setup of the Connection
- Generate an API key in Mumble. Open the right-hand menu and click Settings, go to the Technical Profile tab, and in the API Key section click Copy. This key is the master key of your sending account – don’t share it in open documents, and if it leaks, generate a new key immediately.
- Open a Make account. You can sign up for free at make.com. The free plan includes all modules and is usually enough for one or two scenarios. For heavier automations, paid plans are available.
- Create a new scenario. From the Make dashboard, click Create a new scenario. You’ll get a blank canvas.
- Add the Mumble app. On the canvas, click the first circle, search for Mumble, and choose one of the modules (for example, Send Template).
- Connect the account. Make will ask for an API key. Paste the key you copied from Mumble. The connection is saved and will be available for every future scenario.
- Add a trigger. Before the Mumble module, add a module for the app that will trigger the scenario (Google Sheets, Webhook, Calendly, Shopify, etc.). Map the fields between the modules, and test with your own phone before running it on a real audience.
Five Scenarios Worth Building First
Practical suggestions, ordered from simple to advanced. They are typically built in 10 to 30 minutes.
1. Lead from a Website Form → WhatsApp Message Within Seconds
The flow: a website form (Webflow / Elementor / WordPress / Typeform) → Make → the Send Template With Variables module in Mumble.
The experience: someone fills out the form on the website at 3 a.m. Within seconds they receive a WhatsApp message from the business with a personal greeting, contact details, and sometimes a link to book a meeting. Responding to leads quickly, within seconds, improves the response rate.
Must know: this is a first message to a new customer, so you must have opt-in on the form (an explicit checkbox) and an approved message template. See the article on the 24-hour conversation window to understand the categorization.
2. New Order in Shopify or WooCommerce → WhatsApp Confirmation
The flow: Shopify / WooCommerce → Make → the Send Template With Variables module in Mumble.
The experience: the customer completes a purchase and within seconds receives a WhatsApp message with the order number, item details, and an estimated delivery time. WhatsApp has a very high open rate compared with other channels, and businesses that use this channel see fewer “where’s my order?” inquiries.
Must know: this is a message template in the Utility category (not Marketing), because it updates on an action the customer took (a purchase). A Utility message template is cheaper at Meta than a Marketing one.
3. New Meeting in Calendly or Google Calendar → WhatsApp Reminder the Day Before
The flow: Calendly / Google Calendar → Make (with a one-day delay) → the Send Template With Variables module in Mumble.
The experience: a customer books a meeting for next week. The day before the meeting, they automatically receive a WhatsApp reminder with the time, location, and a Waze link. Automatic reminders significantly reduce the no-show rate.
Must know: the customer usually won’t be inside the conversation window after a week, so an approved message template is required. This is a Utility category as well.
4. Payment Received in Stripe or PayPal → Confirmation and Next Steps
The flow: Stripe / PayPal → Make → the Send Template With Variables module in Mumble.
The experience: beyond the technical confirmation the customer gets from the payment system itself, they receive a personal WhatsApp message from the business with a thank-you, a breakdown of what they purchased, and the next steps (when the product will ship, when the course begins, how to schedule a training session). A clear follow-up message after a purchase reduces repeat support inquiries.
Must know: a message template in the Utility category. In Israel, Utility conversations are low-cost.
5. New Rows in Google Sheets → Send to a Customer List
The flow: Google Sheets → Make (Loop over the rows) → the Send Template With Variables module in Mumble.
The experience: instead of building a campaign in Mumble, you can keep a list in Google Sheets and send from it directly. Useful when the list updates automatically from external sources (a CRM, a registration system, an ongoing lead form). Each new row that appears gets a personal message.
Must know: this is not a full replacement for Mumble campaigns – campaigns provide analytics, segmentation, scheduling, and post-send actions. But for simple “every new row → a message” scenarios, it’s quick and convenient. Don’t use it to send to hundreds of customers at once – a campaign is better suited for that.
Mumble’s Modules in Make
The Mumble app in Make exposes seven action modules. There are currently no trigger modules – meaning Make cannot start a scenario in response to an event that happened in WhatsApp (a new message, a closed conversation, etc.). For scenarios triggered by WhatsApp events, use the Webhook configured in Mumble’s Technical Profile, or a Webhook in the automations engine (When → If → Then).
| Module | What it does |
|---|---|
| Make an API Call | A general call to any endpoint in Mumble’s API. For anything that has no dedicated module. |
| Add New Customer | Creates a new customer with phone, name, and ad-attribution fields. |
| Add New Label | Creates a new list (label). |
| Delete Label | Deletes a list. |
| Send Template | Sends an approved message template without variables. |
| Send Template With Variables | Sends an approved message template with text variables ({{1}}, {{2}}, etc.). |
| Send Text Message | Sends free-form text (only within the conversation window). |
For anything not covered by these modules (assigning to an agent or team, fetching conversations, sending media, custom fields), use the Make an API Call module against the appropriate endpoint in Mumble’s API documentation.
Troubleshooting Common Issues
Sharing the API Key in a Shared Scenario or Document
What happens: the API key gives full control over your sending account. If someone else gets the key, they can send from your WhatsApp number.
Solution: store the key only in Make’s Connection, which is encrypted. If the key leaks, go to Settings → Technical Profile and generate a new key – this revokes the old one immediately.
Invalid Phone Number Format
What happens: WhatsApp requires the international format without a + and without a leading 0. Trying to send to the phone 0501234567 or +972501234567 will return an error.
Solution: the correct format for Israel is 972501234567. If your data is in a different format, add a Text Parser or Set Variables module in Make before sending the phone to Mumble – remove the +, replace a leading 0 with 972.
Trying to Send Free-Form Text via Send Text Message to a Customer Outside the Window
What happens: the module returns a Conversation is closed error, and the message is not sent. The whole flow fails.
Solution: before sending, use the Make an API Call module against the is-active-conv endpoint to check whether the window is open. If it is, send free-form text. If not, send a message template. Or simply always send a message template – safe in every situation.
No Error Handling in the Scenario
What happens: Meta imposes rate limits on aggressive sending. If a scenario sends 1,000 messages within a minute with no protection, some will fail.
Solution: use Make’s Error Handler mechanism. Set up an automatic retry with a delay of 2-5 seconds between attempts. And for sending to hundreds of customers in sequence, add a Sleep of one second between each send.
Expecting a Scenario to Start from an Incoming WhatsApp Message
What happens: the Mumble app in Make does not expose trigger modules. There is no way to start a scenario because “a WhatsApp message arrived”.
Solution: use the Webhook in Settings → Technical Profile → Forward message to Webhook. Mumble will send a POST to the Make Webhook address, and your scenario will start there. Similarly, you can set up a specific Webhook in Mumble’s automations engine (When → If → Then) for specific events.
Related Articles
- The 24-hour conversation window in WhatsApp Business
- When to use a message template and when to use a free-form message
- WhatsApp message templates guide
- General account settings
The Bottom Line
Connecting Mumble to Make.com turns your WhatsApp account into an automated part of your digital flows – from a lead form to an order update. Setup takes about five minutes, and a first scenario is built in about fifteen. You can add the rest of the scenarios gradually.