Resources · Make integration

Mumara Make integrationAutomate Mumara with Make.

Your Mumara contact list can stay in step with every other tool you use. The Mumara Make integration offers 6 modules: 5 actions and 1 search, all about contacts. This page shows marketers how to link the account, build a first scenario and pick the right module.

Try the Mumara integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mumara Make integration do for your contacts?

The Mumara Make integration lets Make add, change, look up and remove contacts in your Mumara account for you. You build a scenario, which is the automation itself: a chain of modules, each module being one brick that does one job. Mumara has no trigger of its own, so another app or a schedule starts the chain.

Fresh leads land in Mumara on their own. A signup arrives in your form tool or your CRM, and Create a Contact writes that person into Mumara. Nobody exports a file or pastes rows by hand anymore.

Records stay current when details change elsewhere. When a customer edits their profile in another app, Search Contacts finds the matching record and Update a Contact rewrites it. Each item passed between modules is called a bundle, and here a bundle is one contact.

Data deletion requests get handled cleanly. When someone asks to be forgotten in your support tool, Get a Contact confirms the record and Delete a Contact removes it. Anything the listed modules skip can go through Make an API Call, which reaches the rest of the Mumara API with the same connection.

Keep one limit in mind: the Make documentation for Mumara is flagged as AI-generated from the vendor docs, so check anything critical with Mumara directly. The same app may also exist as an n8n node; our n8n vs Make comparison helps you weigh the two, and the Make training walks through the editor step by step. To see what the plans include, read Make pricing.

Connect

How do you connect your Mumara account to Make?

  1. 01

    Generate your API token in Mumara

    In Mumara, click the profile icon next to the Logout button, open API Configuration under Integration in the left menu, then click Generate API Token. Copy the token shown in the API token field and keep it at hand.

  2. 02

    Add a Mumara module in Make

    Sign in to Make, place any Mumara module in your scenario and click Create a connection. A connection is your Mumara account linked to Make once, then reused by every Mumara module you add later.

  3. 03

    Paste the token and save

    Give it a label in Connection name if you like; that field is optional. Paste the credentials copied from Mumara, or follow the prompts on screen, and save. Make can now read your contacts.

First scenario

Your first scenario with Mumara and Make

GoalWhen a customer changes their details in another app, Make finds the matching contact in Mumara and updates it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app where profile changes happen, such as your CRM or form tool.

  2. 02

    Add Search Contacts

    Click the + to the right of that trigger, search for Mumara and choose Search Contacts. Create the connection, then map the customer details coming from the first module.

  3. 03

    Chain Update a Contact

    Add Update a Contact after the search. Map the contact it found and the new values from the trigger, so the right Mumara record gets the fresh details.

  4. 04

    Test with Run once

    Click Run once and change a test profile in the source app. Open each module to read the bundles it received and confirm Mumara now shows the new data.

  5. 05

    Schedule and switch it on

    Set the clock on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps working without you.

Modules

What each Mumara module does

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

Mumara1

Create a Contact

Action

In Make“Creates a contact.”

You get a brand new contact in Mumara, filled from whatever the previous module passed along, so every lead reaches your mailing tool without a manual import.

When to use it
right after a signup form, a webinar registration or a new deal in your CRM, whenever the person is certainly not in Mumara yet.
Watch out
if that person may already exist, run Search Contacts first so you do not end up with two records.
Mumara2

Delete a Contact

Action

In Make“Deletes a contact.”

This one removes a contact from your Mumara account, which keeps your list clean when someone leaves or asks to have their data erased.

When to use it
after a deletion request logged in your helpdesk, once you have confirmed which record belongs to that person.
Watch out
treat the removal as final and try the scenario on a test contact with Run once before you point it at your real audience.
Mumara3

Get a Contact

Action

In Make“Retrieves a contact.”

Pulls up the full record of a single contact you already know, so later modules can reuse its details without asking the person again.

When to use it
when an earlier step already holds the contact reference and you need the record itself, for example to copy it into a spreadsheet or a support ticket.
Watch out
it works on one known contact; if you only have partial details, reach for Search Contacts instead.
Mumara4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Mumara API to your scenario, reusing the connection you already set up, for anything the five contact modules do not cover.

When to use it
when your plan needs a Mumara feature that has no module of its own in Make, and you know which endpoint handles it.
Watch out
you write the request yourself, so keep the Mumara API documentation open and check the answer with Run once.
Mumara5

Update a Contact

Action

In Make“Updates a contact.”

Rewrites an existing Mumara contact with newer information, so the person you email always matches what your other tools know about them.

When to use it
a customer changes company, moves to another plan or fixes a typo in their profile, and you want Mumara to follow without anyone touching it.
Watch out
the module needs to know which record to change, so it usually follows Search Contacts or Get a Contact.
Mumara6

Search Contacts

Search

In Make“Searches for contacts.”

Finds the contacts that match what you are looking for and hands them to the next module, one bundle per contact found.

When to use it
before an update or a creation, to check whether a person already sits in your Mumara list.
Watch out
a search can return zero, one or several contacts; plan for the empty case, because the modules after it then have nothing to work on.
Need help

Need help automating Mumara with Make?

A person reads every message.

FAQ

Mumara and Make: common questions

01Is the Mumara Make integration free?
Yes, on the Make side. Mumara is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum gap between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and lift the cap on active scenarios. Usage is counted in operations, one operation being one module run on one bundle. You still need your own active Mumara subscription.
02What do you need to connect Mumara to Make?
Two things: an active Mumara account and an API token generated inside it. In Mumara, open the profile icon beside Logout, go to API Configuration under Integration and click Generate API Token. Copy the value, then in Make add a Mumara module, click Create a connection and paste it. The connection name is optional. Once saved, every Mumara module in any of your scenarios can reuse that same connection without asking again.
03Does the Mumara Make integration react in real time?
No, because Mumara has no trigger module in Make, so it never starts a scenario itself. The scenario starts from another app instead, for example a form or CRM trigger, and Mumara modules act further down the chain. You can also start it on a schedule set on the first module, every 15 minutes by default, or through a Make webhook called by another tool. How fast things happen then depends on that first module.
04What if a Mumara module is missing in Make?
It depends on what you need. The listed modules cover contacts: create, get, search, update and delete. For anything else in Mumara, use Make an API Call, which calls any endpoint of the Mumara API with the connection you already have. Keep the vendor documentation nearby, since the Make help page for Mumara is marked as AI-generated and may contain mistakes. When in doubt about a behavior, confirm it with Mumara directly.
05Should you use Make or n8n for Mumara?
It depends on the tool your team already runs. In Make, Mumara comes with 6 ready modules focused on contacts, plus Make an API Call for the rest, all driven from the visual scenario editor. The same app may also exist as an n8n node, so check the n8n side before deciding. Compare which contact actions each tool exposes for Mumara and which platform the rest of your automations already live on, then choose the one that fits.
Same platform

Other docs you might need on this stack.

Browse all integrations