TL;DR
Zapier is a no-code automation platform that connects thousands of different services. Mumble has a dedicated Zapier app that lets you create Zaps (automations) connecting your WhatsApp to other systems: Gmail, Sheets, Shopify, HubSpot, Mailchimp, and more. This article covers what’s possible, how to set up your first connection, which actions are available, and when Zapier is the right choice versus Make or the direct API.
What Zapier is and why it matters
Zapier is a service that lets you connect different apps without writing code. You build a Zap (Zapier’s term for an automation) made up of three parts:
- Trigger. An event in one app that starts the Zap.
- Filters/Actions. What to check or do.
- Action. An action in another app, for example sending a WhatsApp message through Mumble.
The main advantage: no code. You add apps, map fields, and test. It’s all in a friendly GUI.
What Mumble supports in Zapier
The Mumble Zapier app provides actions only, no triggers. In other words, Mumble receives actions from Zapier but does not initiate them. If you want an event in Mumble to start a Zap, you need to go through a Webhook in an automation (see Webhooks in Mumble).
The available actions
| Action | What it does |
|---|---|
| Add New Customer | Add a new customer with phone, name, and additional fields |
| Send Template | Send an approved message template to a customer (without variables) |
| Send Template With Variables | Send a message template with variables filled in |
| Send Text Message | Send a free-form message (only inside the 24-hour window) |
| Add New Label | Create a new list in the account |
| Delete Label | Delete a list |
| Make an API Call | A generic action to call any Mumble API endpoint |
The Make an API Call action gives you access to any API capability that doesn’t appear as a dedicated action: assigning to an agent or team, retrieving conversations, sending media, updating custom fields, and more.
Setting up your first connection
The connection process is simple and one-time. Once connected, you can create as many Zaps as you need without going through the connection setup again.
Step 1: Create an API key in Mumble
- Log into Mumble.
- Open Settings < Technical Profile < API Key.
- If there’s no key, create one. If there is, copy it.
- Save the key somewhere secure (it’s shown only once).
Step 2: Add the Mumble app in Zapier
- Log into your Zapier account.
- On the new Zap creation page, search for “Mumble” in the apps.
- Choose Mumble as the action.
- When choosing an account, click Connect a new account.
- Enter the API Key you copied in the previous step.
- Confirm the connection.
That’s it. The connection is ready and will be available to every Zap you build.
Examples of Zaps you can build
Website form → WhatsApp welcome message
- Trigger: A new form submission in Google Forms or Typeform.
- Action: Send Template With Variables in Mumble. The message template includes a personal welcome.
Useful for: businesses that collect leads through forms. The customer gets a message within seconds, long before anyone opens the email.
Shopify order → WhatsApp order confirmation
- Trigger: Order created in Shopify.
- Action: Send Template in Mumble with the order details.
Useful for: any online store that wants to send an order confirmation over WhatsApp instead of, or in addition to, email.
Calendly booking → reminder before the meeting
- Trigger: A new meeting in Calendly.
- Filter: A Zapier Delay, 24 hours before the meeting.
- Action: Send Template in Mumble with a reminder.
Useful for: therapists, accountants, and consultants who need to remind clients about an appointment.
New row in Google Sheets → import customer to Mumble
- Trigger: New row in Google Sheets.
- Action: Add New Customer in Mumble.
Useful for: sales teams that collect leads in Sheets and want automation in Mumble right away.
Gmail email with a keyword → WhatsApp message
- Trigger: A new email matching a filter.
- Action: Make an API Call in Mumble to perform a specific action.
Useful for: syncing a legacy support system that still runs on email with your WhatsApp channel.
Zapier vs. Make: which to choose
The two platforms do similar things, but there are differences:
| Criterion | Zapier | Make |
|---|---|---|
| Simplicity | Easier to learn | Takes some learning |
| Complexity | Good for simple Zaps | Good for complex flows, loops, branching scenarios |
| Price | More expensive at high volume | Cheaper at high volume |
| Israeli community | Less common locally | Very common |
| Mumble actions | Same actions | Same actions |
Recommendation:
- If you already use Zapier for other systems, keep Mumble in the same place.
- If you’re starting from scratch and need complex automations, Make is the better choice.
- If you want the most simplicity, Zapier is the choice.
See also Connecting Mumble to Make for comparison.
When not to use Zapier
- You need to trigger on a Mumble event. The Mumble Zapier app doesn’t provide triggers. Use a Webhook in an automation instead.
- Very high volume. Zapier is billed by tasks. If you have 10,000 events a month, Make can be significantly cheaper.
- Complex flows with lots of branching. Make handles scenarios with many splits better.
- You need full control. For custom actions, the direct API gives more flexibility. See The Complete Mumble API Guide.
Best practices
- Test with your own number before going live. Every new Zap should be sent to your own number first, to confirm the format is correct.
- Use international format for numbers. Anywhere a phone number appears in a Zap, make sure it’s in international format. See International Phone Number Format.
- Don’t expose your API Key. Never share a Zap that includes the key. If someone needs help with a Zap, disconnect the account before sharing a screenshot.
- Use Error Handling. Zapier lets you handle errors so an automation doesn’t fail if something goes wrong along the way.
- Monitor task usage. Zapier is billed by tasks. If you have many active Zaps, track usage so you don’t overrun.
- Use Filters to save costs. Instead of running the Zap on every event, use a Filter to make sure only relevant events trigger the action in Mumble.
Common issues
The connection fails during authentication
Check:
- That the API Key is correct (no extra spaces at the start or end).
- That the key hasn’t been revoked in Mumble.
- That the account is active and hasn’t been suspended.
The Zap doesn’t send the message
Check:
- The phone number is in international format (972…).
- The message template you chose is actually Approved.
- If it’s a Send Text Message, the 24-hour window with the customer is open.
- The customer isn’t on the blacklist.
Check the Zap’s Task History in Zapier to see specific errors.
I can’t find the action I need
If the action you need isn’t in the short list, use the Make an API Call action, which lets you call any Mumble API endpoint. See The Complete Mumble API Guide for the full list of endpoints.
How do I create a Zap that runs when something happens in Mumble?
The Mumble Zapier app doesn’t provide triggers. The way to do it:
- Create a Webhook in a Mumble automation that runs on the event (for example, a conversation status changed).
- In Zapier, create a Zap with a Webhooks by Zapier < Catch Hook trigger.
- Copy the URL into the Webhook in the Mumble automation.
- Build the actions that follow, in other apps.
This enables triggers even without a dedicated Mumble app. See Automations in Mumble.
Related articles
- Connecting Mumble to Make
- The Complete Mumble API Guide
- Webhooks in Mumble
- Automations in Mumble
- International Phone Number Format
The bottom line
Zapier is the simplest way to connect Mumble to hundreds of other services. If you already use Zapier, add Mumble and start building Zaps in minutes. If you’re starting from scratch and need complex flows, it’s worth looking at Make too. Either way, the API behind both is the same, and anything you can’t do in Zapier you can always do through the Make an API Call action or the direct API.