Resources · Zapier integration

miu.ai Zapier integrationAutomate miu.ai with Zapier.

The miu.ai Zapier integration gives you 8 triggers (all instant), 6 actions and 1 search around chats, customers, tags and flows. Below: what each one does for your chatbot, what it costs on the free plan, how to connect the account and what breaks.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the miu.ai Zapier integration actually does

miu.ai is a chatbot driven by AI that talks with your customers and runs automated flows. The integration links it to your other apps through Zapier: a new chat, a booked appointment or a tag change in miu.ai starts an automation, and other apps can tag customers, update profiles, send messages or start flows in miu.ai.

Appointments that land in your calendar. Appointment Scheduled starts the Zap when a customer books through the chatbot, and your calendar gets the event. Add Tags can then mark the customer in miu.ai so the next conversation knows.

Customers sorted by what they do elsewhere. When something happens in another tool, Add Tags or Remove Tags changes how miu.ai sees the customer, and Update Profile writes the new details into their record.

Flows started from outside the chat. Run Flow launches a miu.ai flow for a customer when another app says so, and Flow Ended tells the rest of your tools when it is over.

All eight triggers are instant: miu.ai tells Zapier the moment something happens, so even on the free plan nothing waits for a check. What Zapier does not do for miu.ai: no step deletes a customer or a chat, the search has no find-or-create variant, and conversations from before the Zap was switched on are not picked up. To weigh Zapier against other tools, see our Make vs Zapier comparison.

Vocabulary

Zapier words in one minute

Eight words, and the rest of the page reads easily. For a guided start, see our Zapier training.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked on a timer by Zapier. An instant trigger is reported by the app the moment it happens. All of miu.ai's are instant.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found instead of guessing.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
Cost

What a miu.ai Zap really costs

Zapier bills by task, and only for what works. The trigger never costs a task, so a busy chatbot does not drain your plan by itself.

  • Free plan100 tasks a month, unlimited Zaps
  • Steps per Zap on free2: one trigger, one action
  • Premium appNo, miu.ai works on the free plan
  • Instant triggersAll 8

Each action that succeeds counts once: a Zap that creates a calendar event and then adds a tag uses two tasks per appointment. A failed action is not counted. miu.ai is not a premium app and runs on the free plan, which stops at two steps per Zap; a filter, a search or a second action needs a paid plan. The interval grid below does not apply to miu.ai's triggers, which are all instant; it only matters when a Zap starts from another app's polling trigger.

Connect

Connect miu.ai to Zapier in three steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. A dialog opens: type miu.ai in its search box, then pick the app from the results.

  2. 02

    Sign in and grant access

    Click Add connection. miu.ai opens in a new tab: sign in with the account the Zaps will act for, then grant Zapier access. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Reuse the connection

    The connection is your miu.ai account linked to Zapier once. Every miu.ai step reuses it afterwards, in this Zap and the next ones. On the first test, run the step once and read what comes back before going further.

First Zap

Your first Zap: chatbot bookings go to your calendar and tag the customer

GoalEvery appointment booked through miu.ai creates an event in your calendar and tags the customer, so the next conversation starts with that context.

  1. 01

    Pick the trigger

    Start a new Zap, choose miu.ai and the Appointment Scheduled event, with the connection made earlier. It is instant, so the Zap will start right away whatever your plan.

  2. 02

    Test on a real booking

    Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on an appointment that really exists.

  3. 03

    Add the calendar event

    Add your calendar and its create-event action, then map the appointment details from the trigger. Test the step and read what came back before going further.

  4. 04

    Add the tag

    Add miu.ai with Add Tags and choose the tag to put on the customer. With three steps the Zap is multi-step and needs a paid plan; it uses two tasks per booking.

  5. 05

    Publish

    Click Publish to switch the Zap on. Only appointments booked after that moment go through it; earlier ones stay where they are.

Triggers

miu.ai triggers on Zapier

8 events start a Zap when something happens in miu.ai, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Appointment Scheduled

Instant trigger

In Zapier“Triggers when an appointment is booked”

Starts a Zap when a customer books an appointment through miu.ai, which turns the chatbot into the front door of your schedule.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when each booking should also reach your calendar, a spreadsheet or the person who will take the meeting.
Watch out
run the test before you map anything, and check which appointment details actually come back.
2

Profile Updated

Instant trigger

In Zapier“Triggers when a profile is updated”

Fires each time a customer profile changes in miu.ai, so what the chatbot learns does not stay locked inside it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when your contact list or CRM should follow the profile miu.ai keeps, without a manual export.
Watch out
as a general precaution, a Zap that writes into the very place its own trigger watches can set itself off again and again. Look at where each step writes.
3

Tag Assigned

Instant trigger

In Zapier“Triggers when a tag is added”

Reacts when a tag is added to a customer in miu.ai, which makes tags a simple switch for whatever should happen next.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a tag means a stage, an interest or a request, and another tool needs to act on it.
Watch out
it reacts to every tag added, whatever the tag. If only one tag matters, a filter that picks it needs a paid plan.
4

Tag Removed

Instant trigger

In Zapier“Triggers when a tag is removed”

The mirror of Tag Assigned: it starts the Zap when a tag comes off a customer, so leaving a group can be as useful a signal as joining it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when removing a tag should undo something elsewhere, such as taking the customer off a list.
Watch out
only removals that happen after the Zap is published count; tags taken off earlier are not replayed.
5

Flow Ended

Instant trigger

In Zapier“Triggers when a flow completes”

The end of a miu.ai flow for a customer starts this one which is the natural moment to hand the result to another tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when the end of a flow should produce a row, a notification or a follow-up task somewhere else.
Watch out
test it with a flow that has really finished, so the three recent items Zapier brings back look like the real thing.
6

Flow Started

Instant trigger

In Zapier“Triggers when a flow begins”

Fires as a flow begins in miu.ai, earlier than Flow Ended, so you can react while the customer is still inside the conversation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when someone on the team should know a flow has started, or when you want to count how many begin.
Watch out
a flow that starts is not a flow that finishes. If you only care about completed ones, pick Flow Ended instead.
7

New Chat

Instant trigger

In Zapier“Triggers when a new conversation is started by a customer.”

Once per conversation, not per message: it fires when a customer starts a new chat.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when every new conversation should be logged, counted or announced to the team in another tool.
Watch out
if the Zap should react to each message, New Message is the one; New Chat stays quiet for the rest of the conversation.
8

New Message

Instant trigger

In Zapier“Triggers when a new message is received from a customer.”

Fires on every message a customer sends, which makes it the most talkative of the eight triggers.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when the content of each message matters, for instance to transfer certain conversations or tag the customer.
Watch out
every run that reaches an action costs a task. Put a filter after it, which needs a paid plan, if only some messages should go through.
Actions

miu.ai actions on Zapier

miu.ai gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Tags

Action

In Zapier“Add tags to a customer”

Puts one or more tags on a customer in miu.ai, so the chatbot and your Zaps can tell groups apart.

When to use it
a purchase, a booking or a form answer in another tool should change how miu.ai treats that customer.
2

Remove Tags

Action

In Zapier“Remove tags from a customer”

Takes tags off a customer in miu.ai, the clean way to close a stage once it is over.

When to use it
a request is solved or a subscription has ended in another tool, and the tag that marked it should go.
3

Run Flow

Action

In Zapier“Start a flow for a customer”

Starts a miu.ai flow for a customer, so a scripted sequence begins without anyone opening the chatbot.

When to use it
an event elsewhere, a payment or a sign-up, should launch the same guided conversation every time.
Watch out
each flow started is one task; check at the test which flow and which customer the step picks.
4

Send Message

Action

In Zapier“Send a message to a customer”

Sends a message to a customer through miu.ai, written or filled in by your Zap.

When to use it
another tool knows something the customer should hear: an order shipped, a booking confirmed, a document ready.
Watch out
check at the test step how the customer is chosen and what the message looks like before publishing.
5

Transfer Chat

Action

In Zapier“Transfer a conversation”

Transfers a conversation in miu.ai, based on something your Zap noticed elsewhere.

When to use it
a filter has spotted a message that meets your condition, and the conversation should be transferred without anyone watching the inbox.
Watch out
read the options the step offers at the test, and check where the conversation actually ends up.
6

Update Profile

Action

In Zapier“Update customer information”

Updates the information miu.ai holds on a customer, so the chatbot works from current details.

When to use it
your CRM or a form collects new details and miu.ai should know them before the next chat.
Watch out
Find Customers placed before it can hand over the right customer; check the result at the test.
Searches

The miu.ai search on Zapier

1 search step looks for data that already exists in miu.ai, so a later step can use it.

A search step reads, it does not write. miu.ai has one, listed at the bottom of the Action event list under SEARCH. Adding it makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when it comes back empty or crowded.

1

Find Customers

Search

In Zapier“Search customers by filters”

Looks up customers in miu.ai using filters and hands what it found to the steps that follow.

When to use it
before Update Profile, Add Tags or Send Message, when the trigger comes from another app and does not carry the miu.ai customer.
Watch out
a search by filters can match several customers, so set the multiple-results option on purpose and check at the test.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    On apps that offer it, this box turns a search into a find-or-create. Find Customers has no such variant, so the Zap never creates a missing customer.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once. With a search by filters, this one matters.
When it breaks

When a miu.ai Zap breaks

Zapier attaches no help article to miu.ai, and no limit specific to the app is documented. The failures worth knowing are the general ones; with eight instant triggers on a busy chatbot, nothing waits for a check, so the number worth watching is how many runs reach an action.

  • The past is not replayed

    A Zap reacts only to what happens after it is switched on. Chats, bookings and tags from before stay out, and moving that backlog is a separate job.

  • A Zap that sets itself off

    As a general precaution, a Zap that writes into the very place its own trigger watches can start itself again and again, and the task count drops fast.

  • A sudden flood gets held

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back instead of running every item.

  • Every message can cost

    New Message fires on each customer message. Without a filter, every message that reaches an action uses a task, and each one counts against the 100 tasks of the free plan.
Need help

Need help automating miu.ai with Zapier?

A person reads every message.

FAQ

miu.ai and Zapier: frequent questions

01Is the miu.ai Zapier integration free?
Yes, as long as each Zap stays at two steps. miu.ai is not a premium app, so it works on the free plan of Zapier, which gives 100 tasks a month and an unlimited number of Zaps. A new chat that triggers one Send Message fits. A booking that should both reach your calendar and tag the customer, or a filter on New Message, makes the Zap multi-step, and a multi-step Zap requires a paid plan.
02How many tasks does a miu.ai Zap use?
One per action that succeeds, nothing for the trigger. That matters on a chatbot: New Message runs on every customer message, and each run that reaches an action uses a task. A booking Zap that creates a calendar event and adds a tag uses two tasks per appointment. An action that fails is not counted. Some apps and actions take more than one task when they complete, so read the count on your plan after the first runs.
03Does miu.ai start Zaps in real time?
Yes, all eight of its triggers are instant. miu.ai tells Zapier the moment a chat starts, a message arrives, a tag changes, a profile is updated, a flow starts or ends, or an appointment is booked, and the Zap starts right away, whatever your plan. The editor shows a lightning bolt on such Zaps. The interval grid of the plans does not apply to these triggers; it only concerns other apps whose triggers are polling ones.
04What do you need to connect miu.ai to Zapier?
An account on miu.ai, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection happens from the Apps page of Zapier: click + Add connection, search miu.ai, click Add connection, sign in in the tab that opens and grant access. It is made once and reused by every miu.ai step afterwards, whether it is a trigger, an action or the Find Customers search.
05New Chat or New Message: which trigger should you pick?
New Chat fires once, when a customer starts a conversation. New Message fires on every message that customer sends afterwards. For logging conversations or alerting the team about new ones, New Chat keeps the volume low. For reacting to what customers actually write, New Message is the one, usually with a filter behind it so only some messages reach an action. That filter needs a paid plan, and without it every message that reaches an action costs a task.
06What if the miu.ai operation you want is not listed?
Then no miu.ai step will do it. The miu.ai page on Zapier shows the current list, which is what the editor offers: eight triggers, six actions and Find Customers. There is nothing to delete a customer or close a chat, and the search cannot create a customer that is missing. Check that page before designing a Zap around an operation, and see whether a tag, a profile update or a flow can carry the same intent.
07Zapier, Make or n8n for miu.ai?
Decide on criteria rather than reputation. On Zapier, all eight miu.ai triggers are instant, even on the free plan, so speed does not depend on what you pay. What does depend on it is the shape: two steps are free, a filter or a second action is not. Check whether Make and n8n list miu.ai, which operations they expose, how they count a run, and who on the team will maintain the automation.
Same platform

Other docs you might need on this stack.

Browse all integrations