Resources · Zapier integration

Miho Zapier integrationAutomate Miho with Zapier.

The Miho Zapier integration gives you 7 triggers, 0 actions and 0 searches. Every trigger is instant, so a sale, a sign-up or a finished course reaches your other tools without waiting on your plan. Miho only starts Zaps; the next app does the work.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Miho Zapier integration actually does

It links your Miho workspace to Zapier so that what happens in your courses starts automations in other apps. The automation is called a Zap: one trigger (the event that starts it), then one or more actions (what happens next). All seven Miho triggers are instant: Miho reports the event itself, so nothing waits for a scheduled check.

Three results people build with it. A sales log you never have to update: New Sale fires when a customer buys one of your digital products, and each purchase becomes a row in a spreadsheet. A list of new sign-ups for your email tool: New Lead Signup fires on each sign-up in your workspace, so the person can join a list in the next app. A record of who finished: Course Completed fires when a customer completes the progress on a product, which gives you a clean list of finishers.

What Zapier does not do for Miho: write anything into it. The integration has no action and no search, so a Zap cannot enroll a customer, create a course or look up a student in Miho. It listens to your workspace, then passes what it heard to another app. Anything that has to change inside Miho is still done there.

For the budget, that means every task you spend is an action in the next app, never on Miho. Before you build, see our Zapier review, and if you are still choosing a tool, open our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Eight words you will see in the editor. Once they are clear, the notes below read fast.

Zap
The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts a Zap. With Miho, it is a sale, a sign-up, a submitted quiz or a finished course.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in another app.
Task
The unit Zapier bills: one action that completes successfully. The number on your plan counts those.
Instant vs polling trigger
An instant trigger is reported by the app itself. A polling trigger is checked by Zapier on a timer. All seven Miho triggers are instant.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it otherwise.
Connection
Your Miho account, linked to Zapier once and then reused by every Zap that starts from it.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it needs a paid plan.
Cost

What a Miho Zap really costs

Short version: the Miho side is free. The trigger never costs a task, however many sales or sign-ups come in.

  • Trigger cost0 tasks
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, works on the free plan
  • Miho triggers7, all instant

Each action that succeeds counts as one task. A Zap with three actions eats three times more than a Zap with one, and an action that fails is not counted. Miho is not a premium app, so it works on the free plan: 100 tasks a month and as many Zaps as you like, each limited to one trigger and one action. Add a filter or a second action and you need a paid plan. The polling grid below is Zapier's official one; it does not apply to Miho, whose seven triggers are all instant.

Connect

Connect Miho to Zapier in three steps

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. You need an account on Miho, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Miho

    Type Miho in the search box of the dialog, select it, then click Add connection. A new tab opens so you can sign in with the account that runs your workspace.

  3. 03

    Grant access

    Sign in to Miho in that tab and allow Zapier to reach the account. Every Zap that starts with a Miho trigger then reuses this connection without asking again.

First Zap

Your first Zap: log every sale in a spreadsheet

GoalEach purchase of one of your Miho products adds a row to a shared spreadsheet, so sales are visible without logging in to Miho.

  1. 01

    Start a Zap and pick the trigger

    Create a new Zap, choose Miho as the app, then New Sale as the event. Then select the connection you set up a moment ago.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the account, so you map the next step on a real sale rather than on guesses.

  3. 03

    Add a filter if you need one

    A filter is set in three boxes: the field to look at, the rule, the value. It makes the Zap multi-step, so it needs a paid plan. On the free plan, skip it.

  4. 04

    Add the spreadsheet action

    Pick your spreadsheet app and its add-a-row action, then map the sale fields from the trigger into the columns. Test this step and read what came back.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, each new sale adds a row. Sales made before that moment stay out of the sheet.

Triggers

The 7 Miho triggers

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

1

Assignment Submitted

Instant trigger

In Zapier“Triggers when some customer submits Lesson of type Assignment.”

Starts a Zap when a customer hands in a lesson of the Assignment type. It is the trigger for work that someone on your side will want to look at.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each submitted assignment should post a message in your team chat so someone reviews it.
Watch out
only lessons of the Assignment type start it; quizzes have their own trigger.
2

Course Completed

Instant trigger

In Zapier“Triggers when some customer completes the progress on your digital product.”

Fires when a customer completes the progress on one of your digital products. It marks the end of the road, the right moment to send what comes after a course.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want every finisher added to a separate list in your email tool.
Watch out
it reacts to completed progress, so check in the test what a finished product looks like in the data.
3

Course Published

Instant trigger

In Zapier“Triggers when a course is published on miho application.”

Runs when a course is published in Miho. Unlike the other triggers, it follows your own work rather than a customer's action.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each new course should be added to the catalog sheet your team keeps.
Watch out
courses published before the Zap goes live are not sent, so publish the Zap first.
4

New Lead Signup

Instant trigger

In Zapier“Triggers when a new signup happens on your workspace.”

Fires on each new sign-up in your Miho workspace. It catches people at the start, before any purchase, which is when an email sequence has the most to say.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every sign-up should join a contact list in your email tool.
Watch out
check in the test which details a sign-up carries before you map them into another app.
5

New Sale

Instant trigger

In Zapier“Triggers when some customer buys your digital product.”

Each time a customer buys one of your digital products, this one goes off. It sits closest to the money, a natural base for a sales log or a purchase alert.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every purchase should add a row to a sales sheet the team can read.
Watch out
sales made before the Zap was published are not picked up.
6

Quiz Submitted

Instant trigger

In Zapier“Triggers when some customer submits the quiz type of lesson.”

A customer submits a lesson of the quiz type, and the Zap begins. It gives you a trace of each attempt outside Miho, for follow-up or reporting.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you keep one sheet of quiz submissions to see which lessons people reach.
Watch out
assignments do not start this trigger; they go through Assignment Submitted instead.
7

Section Went Live

Instant trigger

In Zapier“Triggers when the some section goes live for some customer on miho application.”

Tied to a single customer: a section of a course goes live for them and the Zap starts. Read that way, the same section may start the Zap once for each customer it opens for; confirm it in the test.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each customer should get a heads-up from your email tool when new material opens for them.
Watch out
if it does run per customer, every action multiplies by the number of customers, so count your tasks before you add any.
When it breaks

When a Miho Zap breaks

Zapier attaches no help article to Miho, and the source lists no app-specific rate limit. The failures you will meet are Zapier's own.

Most of them show up on a busy launch day rather than during the test. Read them before you publish, and keep our Zapier troubleshooting guide nearby for the day one does.

  • Past sales are not picked up

    A Zap only reacts to what happens after you switch it on. Sales and sign-ups from before stay out; moving the backlog is a separate job.
  • A bulk import can be held back

    When a trigger suddenly sends a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.
  • A Zap that feeds its own trigger

    A Zap that writes into the very place its trigger watches can set itself off again and again, and burn tasks fast. Keep the output elsewhere.
Need help

Need help automating Miho with Zapier?

A person reads every message.

FAQ

Miho Zapier integration: common questions

01Is the Miho Zapier integration free?
Yes, it works on Zapier's free plan, because Miho is not a premium app. The free plan gives you 100 tasks a month and an unlimited number of Zaps, each limited to two steps: one trigger and one action. That is enough for a Zap that writes each sale into a spreadsheet. As soon as you want a filter or a second action, the Zap becomes multi-step and needs a paid plan. Check that limit before you design anything larger.
02How many tasks does a Miho Zap use?
The Miho trigger itself uses none. Zapier counts a task only when an action completes successfully, and Miho has no actions, so every task you spend is in the next app. A Zap that adds one row per sale costs one task per sale; add a chat message and it costs two. An action that fails is not counted. On a launch day, multiply the expected sales by the number of actions to size your plan.
03Do Miho sales reach Zapier in real time?
Yes. All seven Miho triggers are instant: Miho tells Zapier the moment a sale, a sign-up or a submission happens, and the Zap starts right away, whatever your plan. The polling interval of Zapier's plans does not apply to them, so a free account gets the same speed here as an Enterprise one. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to confirm it.
04What do you need to connect Miho to Zapier?
An account on Miho, plus read or write access on anything you do not own yourself and want the Zap to touch. In Zapier you open the Apps page, click + Add connection, search for Miho, click Add connection, sign in on the tab that opens, and grant access. Once that is done, every Zap that starts with a Miho trigger reuses the same connection, so you only go through these steps once.
05Can Zapier enroll customers or create courses in Miho?
No. The integration has 7 triggers and no action or search, so Zapier can only listen to Miho, never write to it. A Zap can copy a sale or a sign-up into another tool, but it cannot enroll a customer, publish a course or look up a student in Miho. Anything that has to change inside Miho is still done there by hand. Plan your process as a one-way flow, from Miho toward your other tools.
06What if the Miho trigger you need is not on Zapier?
Check the Miho page on Zapier first: it shows the current list of triggers, and nothing outside that list can be added from the editor. Today it covers sales, sign-ups, published courses, finished courses, quizzes, assignments and sections going live. If your event is none of these, look at whether a nearby one carries what you need, for instance Course Completed instead of a final quiz. If none fits, that event cannot start a Zap today.
07Zapier, Make or n8n for Miho?
Decide on criteria, not on a ranking. Presence first: check that the tool you pick lists Miho at all. Then direction: on Zapier, Miho gives 7 instant triggers and no action, so data only flows out of your workspace. Then plan: a sales log with one row per sale fits the free plan; a filter on certain products, or a second action, needs a paid one. Then volume: on a launch day, sales times actions is your task count. The polling interval is not a criterion here, since every Miho trigger is instant.