Resources · Make integration

Mihu AI Make integrationAutomate Mihu AI with Make.

Can Make run your Mihu AI contacts, calls and campaigns for you? The Mihu AI Make integration gives you 36 modules: 1 trigger, 28 actions and 7 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Mihu AI integration on MakeSee the 36 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mihu AI Make integration do for you?

The Mihu AI Make integration links your Mihu AI account to Make, so a scenario (the automation you build in Make, a chain of modules) can read and write your Mihu AI data. Going by the module names, that covers contacts, AI agents, calls, WhatsApp and SMS messages, campaigns, appointments and a knowledge base, all without writing code.

Follow up on every finished session. Watch session ended picks up the sessions that closed since its last check, Get session evaluation fetches how it went, and Update a contact writes the result back to the person, so nobody copies notes by hand.

Feed a campaign from another tool. When a lead lands in your form or CRM, Create a contact adds it to Mihu AI and Add contacts to campaign puts it in the right list; Run a campaign and Stop a campaign let the scenario start or halt the outreach.

Keep your agent's knowledge current. Import knowledge text, Update knowledge record and Delete knowledge record mirror changes made in your documentation, so the agent answers from the latest version.

What Make does not do here: Make's documentation for this app lists no groups, no field details and no specific limits, and it notes that its content is AI-generated and should be checked against the vendor's own docs. Anything the listed modules miss goes through Make an API call. If you also look at n8n, our n8n vs Make comparison helps you choose, and our Make review and Make training cover the editor in depth.

Connect

How do you connect Mihu AI to Make?

  1. 01

    Copy your API key in Mihu AI

    In your Mihu AI account, open Settings, then the API tab, and copy the API key shown on screen. You need an active Mihu AI account for this key to exist. Keep it somewhere safe for the next step.

  2. 02

    Add a Mihu AI module in Make

    Log in to Make, open a scenario and add any Mihu AI module. Click Create a connection. A connection is your Mihu AI account linked to Make once, then reused by every Mihu AI module you add later.

  3. 03

    Paste the key and save

    If you like, type a label in the Connection name field so you recognize the account later. Paste the API key you copied, or follow the instructions on screen, then save. Make now lists the Mihu AI data it can reach.

First scenario

Your first scenario with Mihu AI and Make

GoalWhen a session ends in Mihu AI, Make fetches its evaluation and updates the matching contact.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for Mihu AI and pick Watch session ended.

  2. 02

    Link your account

    Click Create a connection and paste your Mihu AI API key. Once the connection exists, Make can read your Mihu AI data and offers it in the module settings.

  3. 03

    Add the evaluation

    Click the + on the right of the trigger and add Get session evaluation. Map the session data the trigger returned, so Make knows which session to look up.

  4. 04

    Write back to the contact

    Add Update a contact after the evaluation and map what you want to keep from the previous modules. Each bundle, one ended session here, flows through the chain on its own.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the data before anything runs unattended.

  6. 06

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Triggers

What starts a Mihu AI scenario

1 module starts a scenario when something happens in Mihu AI. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Mihu AI as soon as it happens.

Mihu AI1Watch session ended

Watch session ended

triggerIn the docs only

This trigger hands each Mihu AI session that has ended to your scenario, one bundle per session, so the rest of the chain can react to it: fetch the evaluation, read the conversation or update the contact who took part.

How it fires
scheduled. Make checks Mihu AI on the scenario's schedule, every 15 minutes by default, down to 1 minute on paid plans. Nothing happens between two checks.
When to use it
any follow-up that should only start once the exchange is over, like logging the outcome in your CRM.
Watch out
Make's directory was unavailable for this app, so the scheduled type is inferred from the module name. Look for the clock badge on the module to confirm it.
Modules

Everything Mihu AI can do in Make

Mihu AI gives you 35 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Mihu AI1

Add contacts to campaign

ActionIn the docs only

You get contacts enrolled in an existing Mihu AI campaign without opening the app, straight from whatever scenario produced them. It is the link between the place your leads come from and the outreach itself.

When to use it
right after Create a contact or List contacts, when those people belong in a campaign you already set up.
Watch out
the campaign has to exist first; create it by hand or with Create a campaign.
Mihu AI2

Create a campaign

ActionIn the docs only

This module sets up a new campaign in Mihu AI from your scenario, so an event elsewhere, a new product or a new segment, can open its own outreach without anyone clicking through the app.

When to use it
when each new list or launch needs its own campaign, followed by Add contacts to campaign to fill it.
Watch out
creating a campaign does not start it; Run a campaign does that.
Mihu AI3

Create a contact

ActionIn the docs only

A new person appears in your Mihu AI contacts the moment another tool records them, a form, a CRM or a spreadsheet row, so your agents can reach them without a manual import.

When to use it
as the first Mihu AI step after a trigger from your lead source.
Watch out
running it twice for the same person may create a duplicate; search with List contacts first if the source can send someone again.
Mihu AI4

Create a knowledge data record

ActionIn the docs only

You add a single new entry to the knowledge your Mihu AI agents draw on, fed by a source you already maintain, such as a product sheet or a support article stored in another app.

When to use it
when one structured item appears elsewhere and the agent should know about it too.
Watch out
for a longer piece of plain text, Import knowledge text is the closer fit; this one creates a record.
Mihu AI5

Create a task

ActionIn the docs only

This module drops a task into Mihu AI from your scenario, so a follow-up that another event calls for lands where your team or your agent will see it, instead of living in someone's memory.

When to use it
after a session or a call that needs a human action, for example when the evaluation flags a problem.
Watch out
Make's documentation says nothing more about tasks; check in Mihu AI what a task triggers on its side.
Mihu AI6

Create an agent

ActionIn the docs only

You spin up a new AI agent in Mihu AI directly from a scenario, handy when agents follow a pattern and are created from data kept in another tool, like one agent per client or per offer.

When to use it
in an onboarding scenario that prepares everything a new account needs.
Watch out
to change an agent that already exists, use Update an agent rather than creating a second one.
Mihu AI7

Create an appointment

ActionIn the docs only

This one books an appointment in Mihu AI from your scenario, so a slot agreed somewhere else, on a booking page or in a CRM, shows up on the Mihu AI side as well.

When to use it
when a booking happens outside Mihu AI but your agents should know about it.
Watch out
if the booking may change later, keep the appointment reference so Update an appointment can find it.
Mihu AI8

Delete a contact

ActionIn the docs only

This module removes a contact from Mihu AI, which keeps your lists clean when someone leaves your database or asks not to be contacted anymore, without a manual cleanup pass.

When to use it
when an unsubscribe or a deletion request arrives in another tool.
Watch out
a deletion cannot be undone from Make. Test it with Run once on a dummy contact before switching the scenario on.
Mihu AI9

Delete knowledge record

ActionIn the docs only

Outdated information disappears from your agents' knowledge as soon as the source is withdrawn, so an agent stops quoting an old offer or a retired procedure.

When to use it
when a document or a product is archived in the tool you treat as the reference.
Watch out
the scenario needs to know which record to remove; keep the record reference from Create a knowledge data record in a place the scenario can read.
Mihu AI10

Get a call

ActionIn the docs only

You pull the details of one call from Mihu AI into your scenario, ready to be sent on to a CRM, a spreadsheet or a message to the team.

When to use it
when you already know which call you want, for instance after List calls or from data another module passed on.
Watch out
it reads one call; to go through several, start with List calls, which returns one bundle per call.
Mihu AI11

Get a contact

ActionIn the docs only

This module fetches a single Mihu AI contact, so later modules can use that person's details: to personalize a message, to check a record before changing it, or to copy it into another tool.

When to use it
when an earlier step already gives you the contact to look up.
Watch out
if you only have partial information about the person, List contacts is the safer starting point.
Mihu AI12

Get a conversation

ActionIn the docs only

You get one full conversation from Mihu AI inside Make, which is what you need to archive an exchange, pass it to a colleague or store it next to the customer record.

When to use it
after Watch session ended or Get a session, once you know which exchange matters.
Watch out
to handle the messages one by one, List conversation messages gives you a bundle per message instead.
Mihu AI13

Get a session

ActionIn the docs only

This module reads one Mihu AI session in detail, useful when the trigger or another step only told you that something happened and you now want the whole picture.

When to use it
before deciding what to do next, for example routing a session to a person or logging it in a report.
Watch out
the evaluation of that session is fetched separately with Get session evaluation.
Mihu AI14

Get an appointment

ActionIn the docs only

You retrieve one appointment stored in Mihu AI, so the scenario can check it, show it in another calendar or remind the right person.

When to use it
when an earlier module passes you the appointment to look at, for instance a change coming from your booking tool.
Watch out
for booking requests that are not confirmed yet, List appointment requests is the module to look at instead.
Mihu AI15

Get session evaluation

ActionIn the docs only

This is how you learn how a session went: the module fetches the evaluation Mihu AI holds for it, ready to be stored, shared or used to decide the next step.

When to use it
right after Watch session ended, to feed a quality report or alert someone when a session needs attention.
Watch out
Make's documentation does not describe what the evaluation contains; run it once and read the bundle before mapping anything.
Mihu AI16

Import knowledge text

ActionIn the docs only

Plain text written elsewhere becomes part of what your Mihu AI agents know, without copy and paste, whether it comes from a document, a help article or a note.

When to use it
when your reference content lives in another tool and changes there first.
Watch out
importing the same text again may add a second copy; pair it with Update knowledge record when the source is edited rather than new.
Mihu AI17

Initiate a WhatsApp call

ActionIn the docs only

This module starts a call over WhatsApp through Mihu AI, triggered by an event in your scenario rather than by someone dialing.

When to use it
when your contacts prefer WhatsApp and a new lead or a booking should get a call back.
Watch out
the app also has Send WhatsApp call approval, which suggests WhatsApp calls may need the contact's consent; check the rule in Mihu AI before automating it.
Mihu AI18

Initiate a call

ActionIn the docs only

You get a phone call placed by Mihu AI as soon as your scenario decides it should happen, for a fresh lead, a missed appointment or a form that asks to be called back.

When to use it
for a regular phone call; pick Initiate a WhatsApp call when the channel is WhatsApp.
Watch out
every run places a real call, so test Run once with your own contact first.
Mihu AI19

List agents

SearchIn the docs only

This search brings back the agents in your Mihu AI account, zero, one or several, each as its own bundle that the next modules process separately.

When to use it
to sync your agents into a sheet, or to find the agent to update before calling Update an agent.
Watch out
each bundle runs the following modules once, which counts operations (one execution of one module, what Make bills on your plan).
Mihu AI20

List appointment requests

SearchIn the docs only

You see the appointment requests waiting in Mihu AI, returned one bundle each, so a scenario can confirm them, pass them to the team or copy them into a calendar.

When to use it
when requests should be handled somewhere other than Mihu AI.
Watch out
Make's documentation does not say how a request differs from an appointment; compare the output with List appointments before building on it.
Mihu AI21

List appointments

SearchIn the docs only

This search returns the appointments booked in Mihu AI, zero or more bundles, which you can then filter, copy into another calendar or use to prepare reminders.

When to use it
for a view of several appointments at once; for a single one you already know, Get an appointment is lighter.
Watch out
an empty result is normal when nothing matches, so the next modules simply do not run.
Mihu AI22

List calls

SearchIn the docs only

You get the calls recorded in Mihu AI as separate bundles, a good base for a log in a spreadsheet or a summary sent to a manager.

When to use it
when you want many calls at once; pair it with Get a call only if a call needs more detail.
Watch out
a long list means many bundles and many operations downstream; add a filter after the search to keep only the calls you need.
Mihu AI23

List contacts

SearchIn the docs only

This search finds contacts in Mihu AI and returns them one bundle each, which is how a scenario checks whether a person already exists or grabs a group to work on.

When to use it
before Create a contact to avoid duplicates, or to prepare a batch for Add contacts to campaign.
Watch out
a search can return zero, one or several contacts; plan for each case.
Mihu AI24

List conversation messages

SearchIn the docs only

You receive the messages of a conversation one by one, each as a bundle, so you can store them line by line, scan them for a keyword or forward selected ones.

When to use it
when the individual messages matter more than the conversation as a whole, which Get a conversation covers.
Watch out
one bundle per message multiplies operations on long exchanges.
Mihu AI25

List sessions

SearchIn the docs only

This search returns Mihu AI sessions as separate bundles, handy for a report or for catching up on sessions older than the ones your trigger has seen.

When to use it
for a one-time export or a recap; for sessions as they end, Watch session ended is the better start.
Watch out
Get session evaluation after this search runs once per session found.
Mihu AI26

Make an API call

ActionIn the docs only

This module reaches any endpoint of the Mihu AI API with the connection you already set up, which covers everything the other listed modules leave out.

When to use it
when a need is missing from the list, after checking the Mihu AI API documentation for the right request.
Watch out
you write the request yourself, so a mistake returns an error rather than a friendly form; our Make troubleshooting guide helps read it.
Mihu AI27

Run a campaign

ActionIn the docs only

You launch a Mihu AI campaign from Make, at the moment an outside event says it is ready: a list is complete, an offer goes live, a manager approves it.

When to use it
at the end of a scenario that has created the campaign and filled it with Add contacts to campaign.
Watch out
a running campaign reaches real people; keep Stop a campaign in mind as the way to halt it.
Mihu AI28

Send WhatsApp call approval

ActionIn the docs only

This module sends a WhatsApp call approval to a contact through Mihu AI, the step that precedes a WhatsApp call when permission is needed.

When to use it
before Initiate a WhatsApp call, when the person has not yet agreed to be called on WhatsApp.
Watch out
Make's documentation does not explain the approval flow; check in Mihu AI how the reply is recorded before chaining the call.
Mihu AI29

Send a WhatsApp message

ActionIn the docs only

You get a WhatsApp message sent through Mihu AI whenever the scenario calls for it, for instance a confirmation after a booking or a nudge after a missed call.

When to use it
when a written message on WhatsApp fits better than a call; for a text message, pick Send an SMS.
Watch out
map the recipient carefully, then test with Run once on your own number.
Mihu AI30

Send an SMS

ActionIn the docs only

This module sends a text message through Mihu AI, the plain channel that reaches a phone even without WhatsApp installed.

When to use it
for short confirmations or reminders tied to an event in the scenario, such as a new appointment created with Create an appointment.
Watch out
every bundle sends a message, so a search placed before it can trigger many SMS in one run.
Mihu AI31

Stop a campaign

ActionIn the docs only

You halt a Mihu AI campaign from a scenario, so an event elsewhere, a sold-out product or a complaint, can pause the outreach without waiting for someone to log in.

When to use it
as the safety brake paired with Run a campaign.
Watch out
Make's documentation does not say whether a stopped campaign can be resumed; check that in Mihu AI before relying on it.
Mihu AI32

Update a contact

ActionIn the docs only

This module changes an existing Mihu AI contact, so the details stay in step with the tool you treat as the reference, or record what came out of a session.

When to use it
after Get session evaluation to store the outcome, or when your CRM changes a phone number.
Watch out
the scenario must know which contact to change; find it first with List contacts if the source does not give it.
Mihu AI33

Update an agent

ActionIn the docs only

You adjust an existing Mihu AI agent from Make, useful when the settings of your agents are managed from a central place and should follow its changes.

When to use it
when a client, an offer or a script changes and the matching agent should follow.
Watch out
find the right agent first with List agents; updating the wrong one changes how it talks to real contacts.
Mihu AI34

Update an appointment

ActionIn the docs only

This module edits an appointment already in Mihu AI, so a rescheduling made in another tool does not leave the two sides out of step.

When to use it
when your booking tool reports a change and you created the appointment earlier with Create an appointment.
Watch out
without the appointment reference, look it up with List appointments first.
Mihu AI35

Update knowledge record

ActionIn the docs only

You refresh an existing entry of your agents' knowledge when the source changes, so the answers stay correct without deleting and recreating anything.

When to use it
when a price sheet, a policy or a procedure is edited in the tool where your team writes it.
Watch out
keep the record reference from creation; if the entry no longer exists, Create a knowledge data record is the fallback.
Need help

Need help automating Mihu AI with Make?

A person reads every message.

FAQ

Mihu AI and Make: common questions

01Is the Mihu AI Make integration free?
Yes, Mihu AI is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits per month. You still need your own active Mihu AI account, which Make does not provide.
02What do you need to connect Mihu AI to Make?
You need an active Mihu AI account and its API key. In Mihu AI, open Settings, then the API tab, and copy the key shown there. In Make, add any Mihu AI module, click Create a connection, give it a name if you want, and paste the key. The connection is then reused by every Mihu AI module in your scenarios, so you only do this once per account. If the connection fails, copy the key again from the same tab and check that the account is still active.
03Does the Mihu AI trigger in Make fire instantly?
No. Watch session ended is a scheduled trigger: Make checks Mihu AI on the scenario's schedule and picks up the sessions that ended since the last check. A new scenario checks every 15 minutes by default, the minimum on the Free plan, and paid plans go down to 1 minute. Note that this type comes from the module name, since Make's directory was unavailable for this app; the clock badge on the module confirms it.
04What if a Mihu AI module is missing in Make?
Use Make an API call. Mihu AI has this module in Make, and it lets a scenario call any endpoint of the Mihu AI API with the connection you already created. You write the request based on the Mihu AI API documentation, and Make returns the response as a bundle for the next modules. Make's documentation for this app gives no specific limits, so check the vendor's documentation for any restriction on the calls you plan.
05Should you pick Make or n8n for Mihu AI?
It depends on where the rest of your automations already live. On Make, Mihu AI has 36 modules, including a trigger for ended sessions and Make an API call for anything else. Many apps also have an n8n node, so check whether Mihu AI has one before deciding. Compare what each tool actually offers for this app, then pick the one your team already uses and maintains. Our n8n vs Make comparison on the site walks through the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations