Resources · Make integration

Mumble Make integrationAutomate Mumble with Make.

Every new contact can land in Mumble and get its first message without you copying a thing. The Mumble Make integration offers 8 action modules for customers, labels and messages. This guide walks you through the connection and a first working scenario.

Try the Mumble integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Mumble Make integration do?

The Mumble Make integration lets a Make scenario (the automation you build in Make, a chain of bricks called modules) act inside your Mumble account: create or update customers, manage labels and send messages. Mumble has no trigger of its own in Make, so something else starts the flow: another app or a schedule.

A welcome message for every signup. A contact fills in a form in another tool, Make passes that person to Add a New Customer, then Send a Template sends your ready-made greeting. Nobody retypes a name or a number.

Customer records that stay current. When a deal moves in your CRM, Edit a Customer updates the matching Mumble record, and Add a New Label creates the tag you sort people with. When a campaign ends, Delete a Label clears the old tag.

Personal messages at scale. Send a Template With Variables is the one to reach for when each message should carry data from the previous module, and Send a Text Message covers plain replies.

Know the limits before you start: Make itself states that its Mumble documentation is incomplete because little public information exists about the app, so expect to test each module with your own data. When a listed module falls short, Make an API Call reaches other parts of the Mumble API with the same connection. If you are still weighing tools, our n8n vs Make comparison lays out the criteria, the Make pricing page explains how operations are counted, and Make troubleshooting helps when a run fails.

Connect

How do you connect your Mumble account to Make?

  1. 01

    Open a Mumble module

    In your scenario, add any Mumble module, for example Add a New Customer, and click Create a connection. A connection is your Mumble account linked to Make once, then reused by every Mumble module you add later.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, such as your workspace name, so you can tell accounts apart later. Then either approve access on the Mumble page that opens, or paste the key Mumble gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. The module now shows the connection as selected and lets you fill in its fields. If the fields load without an error message, Make can talk to your Mumble account and you can move on.

First scenario

Your first scenario: add a customer and greet them

GoalWhen a new contact arrives from another app, Make adds them to Mumble and sends your welcome template.

  1. 01

    Start from the app that holds new contacts

    On the Scenarios page, create a new scenario and click the +. Pick the trigger of the tool where contacts first appear, such as your form builder, since Mumble has no trigger in Make.

  2. 02

    Add the customer to Mumble

    Click the + on the right, search Mumble and choose Add a New Customer. Create the connection, then map the contact details coming out of the first module into its fields.

  3. 03

    Send the welcome template

    Add one more module after it: Send a Template. Pick the template and map the customer from the previous step, so the greeting reaches the person Make just created.

  4. 04

    Test it with one contact

    Click Run once and submit a test entry. Each module shows the bundles (the items passed from one module to the next) it received, so you can check the customer and the message.

  5. 05

    Schedule and switch it on

    Open the clock on the first module and set how often Make checks for new contacts, every 15 minutes by default. Then turn the scenario on and let it run.

Modules

What each Mumble module does

Mumble gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Mumble1

Add a New Customer

ActionIn the docs only

Puts a new person into your Mumble customer list straight from the data another app hands over, so nobody copies contact details by hand.

When to use it
as the first Mumble step after a form, a checkout or a CRM, whenever the person does not exist in Mumble yet.
Watch out
running it for someone already on file may create a second record, so use Edit a Customer for returning people.
Mumble2

Add a New Label

ActionIn the docs only

Creates a label in Mumble, which gives you a new way to group customers without leaving your scenario.

When to use it
a new campaign, product or event starts and the tag it needs does not exist yet in your account.
Watch out
this module makes the label itself; check in Mumble how the label then gets attached to customers, because the documentation does not say.
Mumble3

Delete a Label

ActionIn the docs only

Removes a label you no longer need, which keeps your Mumble account tidy once a campaign or segment has ended.

When to use it
at the closing step of a flow that ends an event, right after the last message tied to that label has gone out.
Watch out
a deletion cannot be undone from Make, so test it on a throwaway label with Run once before activating.
Mumble4

Edit a Customer

ActionIn the docs only

Updates a customer who already exists in Mumble, so the record follows what changes in your other tools.

When to use it
a contact changes status in your CRM or corrects their details, and Mumble should reflect it before the next message.
Watch out
the customer has to be in Mumble already; for brand new people, Add a New Customer is the right module.
Mumble5

Make an API Call

ActionIn the docs only

Opens the rest of the Mumble API to your scenario, using the connection you already created, for anything the seven other modules do not cover.

When to use it
you need an action that has no dedicated module, and you have the Mumble API reference at hand to build the request.
Watch out
this is the one technical module here; you write the request yourself, so run it once and read the response.
Mumble6

Send a Template

ActionIn the docs only

Sends one of your prepared Mumble templates to a customer, which keeps wording consistent and saves you writing the same greeting over and over.

When to use it
the message is identical for everyone, like a welcome note after signup or a standard confirmation.
Watch out
the template has to exist in Mumble first; if the text should change per person, pick the variables version instead.
Mumble7

Send a Template With Variables

ActionIn the docs only

Sends a Mumble template that can carry details specific to each customer, so one message model reads as personal to everyone who gets it.

When to use it
the text should include data mapped from an earlier module, such as a first name or an order reference from your shop.
Watch out
check in Mumble which variables the template expects, and map every one before you run the scenario.
Mumble8

Send a Text Message

ActionIn the docs only

Sends a free text message to a customer, written or assembled inside the scenario, for the cases where no template fits.

When to use it
a short follow up built from live data, such as a note to a contact after your support tool closes their ticket.
Watch out
Make documents little about this module, so confirm in Mumble which kind of messages it can send before relying on it.
Need help

Need help automating Mumble with Make?

A person reads every message.

FAQ

Mumble and Make: common questions

01Is the Mumble Make integration free?
Yes. Mumble is a standard app in Make, so it is available from the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Every module run counts as an operation, which is what Make measures on your plan. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios.
02What do you need to connect Mumble to Make?
A Mumble account and a Make account. The Make documentation lists no special prerequisite for Mumble. You add a Mumble module, click Create a connection, optionally name it, then authorize Make on the Mumble page or paste the key Mumble provides, and click Save. The same connection then serves all 8 Mumble modules. Since Make says its Mumble documentation is limited, test the connection with a single module before building a longer scenario.
03Can a Mumble scenario start in real time?
Not from Mumble itself: the app has no trigger module in Make, only actions. The scenario starts from something else. Either you set a schedule on the first module, every 15 minutes by default, or you open the scenario with an instant trigger from another app, which calls Make through a webhook as soon as something happens there. In that second case the Mumble modules run right after that other app reports its event.
04What if the Mumble module you need is missing?
Use Make an API Call. It reaches any endpoint of the Mumble API with the connection you already have, so an action without a dedicated module is still possible. You build the request yourself from the Mumble API reference. Also keep in mind that Make describes its Mumble documentation as incomplete, so for behavior the page does not explain, the Mumble side is the place to check. Test that request with Run once before adding it to a live scenario.
05Should you use Make or n8n with Mumble?
It depends on what you need. In Make, Mumble comes with 8 action modules and Make an API Call, which covers customers, labels and messages without code. Many apps also have an n8n node; check whether Mumble does before comparing, because the documentation reviewed here does not say. Base the choice on which tool already runs your other automations and which editor your team prefers, then test the exact modules you plan to use.
Same platform

Other docs you might need on this stack.

Browse all integrations