Resources · Zapier integration

Meevo Zapier integrationAutomate Meevo with Zapier.

The Meevo Zapier integration offers 13 triggers, 0 actions and 0 searches. Appointments, client records and client packages in Meevo can each start an automation the moment they change, and the work then happens in the apps you plug in after them.

See the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Meevo Zapier integration does for your business

The Meevo Zapier integration connects Meevo, the cloud business software that med spas, salons and spas use for scheduling, point of sale, staff and product tracking, to your other tools. It runs one way: events in Meevo start the automation, and the apps after it do the work.

With thirteen triggers spread over appointments, clients and packages, three kinds of result come up again and again.

A visit log that fills itself. Appointment Completed (Checked Out) adds a row to a spreadsheet for every finished visit, which gives you one list to sort, share or chart. A mailing list that stays in step with your client file. Client Created and Client Communication Preferences Update pass new clients and their changed preferences to your email tool, so the list follows what is in Meevo. A package tracker outside Meevo. Client Package Created and Client Package Redeemed record each sale and each use in a shared sheet.

What Zapier does not do here: Meevo offers no action and no search, so a Zap cannot create, change or look up anything in Meevo. Every Zap starts in Meevo and ends somewhere else. Zapier also ignores whatever happened before your Zap was switched on, so existing clients and past appointments do not come through on their own.

The upside: all thirteen triggers are instant, so even the free plan gets them without waiting. To weigh platforms, see our Make vs Zapier comparison or our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Eight words carry this page. Here they are, in plain language.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap, like a client checking in at Meevo. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, in another app here.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. No Meevo trigger works this way.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens. All thirteen Meevo triggers are instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter or a second action turns it into one, and then it needs a paid plan.
Cost

What Meevo on Zapier really costs

Meevo is not a premium app, so all thirteen triggers are open on the free plan. You pay for the work done in the other apps.

  • Premium appNo, open on the free plan
  • Free plan100 tasks a month, unlimited two-step Zaps
  • BilledEach successful action, never the trigger
  • Meevo triggersAll 13 instant, no polling interval

A Meevo event that starts a Zap costs nothing: the trigger never uses a task. Each action that succeeds in the next app counts as one task, and an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each of two steps: one trigger, one action. Add a filter or a second action and the Zap turns multi-step, which needs a paid plan. A Zap with three actions uses three times as many tasks as a Zap with one. The interval grid below sets how often Zapier checks polling triggers on each plan; it does not apply to Meevo, whose thirteen triggers are all instant.

Connect

Connect your Meevo account to Zapier

  1. 01

    Open Apps and add a connection

    In Zapier, go to the Apps page and click + Add connection. A connection is your Meevo account linked to Zapier once, then reused by every Zap that starts from Meevo.

  2. 02

    Pick Meevo

    Search for Meevo in the dialog, select it, then click Add connection. You need a Meevo account to sign in with: the one whose events the Zap will listen to.

  3. 03

    Sign in and allow access

    Sign in to Meevo in the tab that opens and grant Zapier access. For anything you do not own yourself and want the Zap to touch, you also need read or write access to it.

First Zap

Your first Zap: new Meevo clients into your mailing list

GoalEach new Meevo client that passes your filter is added to your email tool. The filter makes it a multi-step Zap, so it needs a paid plan.

  1. 01

    Create the Zap

    Start a new Zap, pick Meevo as the app that starts it and Client Created as the event. Then select the Meevo connection you made earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent clients of the connected account, so you map fields from a real record, not from a guess.

  3. 03

    Add the filter

    Click the plus icon and add a Filter step. Fill the three boxes: the field to look at, the rule and the value. A text rule only works on text.

  4. 04

    Add your email tool

    Add the action of your email tool, pick the list, then map the client details you saw in the test. Check at the test what each mapped field really holds.

  5. 05

    Test and publish

    Test the action once and read what came back, then click Publish. From now on each matching client is added right away, for one task.

Triggers

Meevo triggers on Zapier

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

1

Appointment Started (Checked In)

Instant trigger

In Zapier“Triggers when an appointment is checked in.”

Starts a Zap when an appointment is checked in at Meevo, which marks the moment the visit actually begins.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
someone on the team should get a message the moment a client is checked in, without watching the Meevo screen.
Watch out
a check-in is not the same event as the booking; if you want to react when the appointment is first made, use Appointment Created instead.
2

Appointment Completed (Checked Out)

Instant trigger

In Zapier“Triggers when an appointment gets checked out.”

Fires when an appointment gets checked out in Meevo, the end of the visit, and passes it to the next steps.

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 a log of finished visits in a spreadsheet and want each one added without retyping.
Watch out
only check-outs that happen after the Zap is published are sent. Past visits stay in Meevo; if your log needs to start complete, moving them is a separate job.
3

Appointment Created

Instant trigger

In Zapier“Triggers when an appointment service gets created.”

Kicks off when an appointment service is created in Meevo, before anyone has arrived.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a new booking should land in a shared calendar or a team channel so everybody sees the day filling up.
Watch out
the description speaks of an appointment service, so run the test and look at what one booking sends before you map fields.
4

Appointment Deleted

Instant trigger

In Zapier“Triggers when appointment gets deleted.”

Reacts when an appointment is deleted in Meevo, so the slot it held can be cleared from the other places that copied 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
you mirror bookings in a sheet or calendar and need a removal to show up there too.
Watch out
Meevo has no action on Zapier, so this trigger can only tell other apps about the deletion. Removing the matching entry elsewhere is the job of an action in that other app.
5

Appointment Updated

Instant trigger

In Zapier“Triggers when an appointment gets updated.”

Goes off each time an existing Meevo appointment gets updated, whatever was edited.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a change to a booking has to reach the tool where the team plans its day, so nobody works from an old version.
Watch out
check at the test what an update actually sends before mapping anything. If only some edits matter to you, a filter on the field you care about makes the Zap multi-step, which needs a paid plan.
6

Client Communication Preferences Update

Instant trigger

In Zapier“Triggers when a client updates their communication preferences.”

Runs when a client changes how they want to be contacted in Meevo, and hands that change to your other tools.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your email or text tool must respect the choice the client made in Meevo, without someone copying it by hand.
Watch out
preferences changed before the Zap went live are not sent. Bringing the existing choices across is a separate job, done once before you rely on the Zap.
7

Client Created

Instant trigger

In Zapier“Triggers when a new client gets created.”

Fires whenever a new client record appears in Meevo, and brings that client into the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
new clients should join your mailing list or your contact sheet without a second round of typing.
Watch out
existing clients are not replayed when you publish. If the other tool needs them too, import them once as a separate job before switching the Zap on.
8

Client Deleted

Instant trigger

In Zapier“Triggers when a client gets deleted.”

Lets other apps know when a client gets deleted from Meevo.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a contact list kept outside Meevo should flag or drop the person too, so it does not drift from your client file.
Watch out
run the test on a real deletion and check which fields come back before you rely on them to find the matching contact elsewhere.
9

Client Merge

Instant trigger

In Zapier“Triggers when a client gets merged.”

When a client gets merged in Meevo, this trigger opens a Zap, so tools that held a copy of that client can be told.

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 a contact sheet beside Meevo and want a heads-up each time records are combined, to tidy the sheet the same way.
Watch out
what a merge sends to Zapier is something to check at the test before mapping anything; do not assume which record survives.
10

Client Package Created

Instant trigger

In Zapier“Triggers when a new client package gets created.”

Fires when a new client package is created in Meevo and passes the package on to the next steps.

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 package sold should open a line in a tracking sheet, or a note to whoever follows up with the client.
Watch out
this event covers the creation of a package only. Uses and changes come through their own triggers, Client Package Redeemed and Client Package Updated, which you can run in separate Zaps.
11

Client Package Redeemed

Instant trigger

In Zapier“Triggers when a new client package gets redeemed.”

Reacts when a client package gets redeemed in Meevo, so every use can be counted somewhere outside the software.

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 track package usage in a shared sheet and want a row per redemption rather than a manual tally.
Watch out
redemptions made before you published are not sent, so a running total built from this Zap starts at the day it went live.
12

Client Package Updated

Instant trigger

In Zapier“Triggers when a new client package gets updated.”

Each time an existing client package gets updated in Meevo, this trigger hands the package to your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a package record kept in another tool has to follow the changes made in Meevo.
Watch out
check at the test what an update to a package actually sends, then decide whether a filter is needed to keep only the edits that matter, which turns the Zap multi-step and needs a paid plan.
13

Client Updated

Instant trigger

In Zapier“Triggers when a client gets updated.”

Runs whenever an existing client record gets updated in Meevo, and brings that client into the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your contact sheet or email tool should hold the same details as Meevo after every edit.
Watch out
contact preferences have their own trigger, Client Communication Preferences Update. Check at the test whether such a change also reaches this one before you run both in parallel.
When it breaks

When a Meevo Zap breaks

Zapier attaches no help article to Meevo and no limit specific to the app is on record. What can go wrong comes from the way Zapier works in general.

Four cases deserve a look before you publish. Most of them do not show as a clear error: the Zap simply does less, or more, than you planned. If something still looks off after these checks, see our Zapier troubleshooting guide.

  • History is not replayed

    A Zap reacts only to what happens after it goes live. Clients, packages and appointments that already existed are not picked up; moving them is a separate job.

  • A Zap that feeds its own trigger

    As a general precaution: a Zap that writes into the very place its trigger watches can set itself off again and again, and burn through your tasks.

  • A sudden flood is held back

    If a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back.

  • A filter that never lets anything through

    Filter rules are typed: a text rule only works on text, a number rule only on numbers. Picking the wrong one is why a filter on a Meevo field never passes.
Need help

Need help automating Meevo with Zapier?

A person reads every message.

FAQ

Meevo and Zapier: common questions

01Is the Meevo Zapier integration free?
Yes. Meevo is not a premium app, so all thirteen of its triggers work on Zapier's free plan. That plan gives you 100 tasks a month and unlimited Zaps, each built from two steps: one trigger and one action. A Zap that logs each checked-out appointment in a spreadsheet fits inside it. As soon as you add a filter, say to keep only some clients, or a second action, the Zap becomes multi-step and you need a paid plan.
02How many tasks does a Meevo Zap use?
The Meevo side costs nothing: a trigger never uses a task, so a check-in or a new client that starts a Zap is free. What you pay for is each action that succeeds afterwards, one task per action and per event. A Zap with one action costs one task each time it runs, a Zap with three actions costs three. An action that fails is not counted. Some apps and some actions take more than one task when they complete, so check the one you add after Meevo.
03Are Meevo triggers on Zapier real time?
Yes. All thirteen Meevo triggers are instant: Meevo tells Zapier the moment an appointment, client or package event happens, and the Zap starts straight away. The interval grid for polling triggers, every 15 minutes on the free plan, does not apply to them on any plan. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is the quickest way to confirm it before you publish.
04What do you need to connect Meevo to Zapier?
A Meevo account to sign in with, plus read or write access on anything you do not own yourself and want the Zap to touch. In Zapier, open the Apps page, click + Add connection, search for Meevo, click Add connection, sign in to Meevo in the tab that opens and grant access. Once that connection exists, every Zap that starts from Meevo reuses it, so you only go through these steps once.
05Can Zapier book appointments or edit clients in Meevo?
No. On Zapier, Meevo offers thirteen triggers and nothing else: no action and no search. A Zap can react to a new appointment, a check-out, a client update or a package redemption, but it cannot create or change anything inside Meevo, and it cannot look up a client in the middle of a Zap. Plan every automation with Meevo as the starting point and the work happening in another app.
06What if the Meevo operation you need is not on Zapier?
Then the integration cannot do it, whatever the settings. Meevo's list on Zapier is thirteen triggers on appointments, clients and client packages. Start by checking the Meevo page on zapier.com, which shows what is offered today. Next, see whether the job can be turned around: a Meevo event starts the Zap, and an action in another app does the work. If the step you are missing has to happen inside Meevo, compare what other automation tools offer for it.
07Zapier, Make or n8n for Meevo?
Choose on criteria rather than a ranking. Coverage first: on Zapier, Meevo brings thirteen instant triggers and no action, so confirm what each other tool offers for Meevo before going further. Timing next: on Zapier those triggers are instant, so the polling interval of your plan does not apply. Then billing: Zapier counts one task per successful action, and the free plan stops at two-step Zaps. Weigh that against how your team prefers to build and maintain its automations.
Same platform

Other docs you might need on this stack.

Browse all integrations