Resources · Zapier integration

MakePlans Zapier integrationAutomate MakePlans with Zapier.

The MakePlans Zapier integration gives you 4 triggers, 5 actions and 1 search. Bookings and new customers reach Zapier the moment they happen, and Zapier can create, confirm, decline or cancel bookings in return, or add and find customers.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MakePlans Zapier integration does for you

The MakePlans Zapier integration links your MakePlans account to Zapier so that booking events start automations in other apps, and other apps can act on your bookings and customers. Every trigger is instant, which is rare and useful. It is not a premium app, so it runs on the free plan.

Bookings that move on their own. Booking Verified hands each verified booking to the Zap, and Confirm Booking or Decline Booking settles it according to a rule you set, so nobody has to open the calendar to click through.

Bookings made elsewhere. Create Booking lets a request that arrives in another tool become a real slot in MakePlans, on the resource and the times you map in.

A customer list that stays in sync. New Customer passes each first-time booker to your other tools, and Create Customer works in the other direction when contacts start outside MakePlans.

What Zapier does not do here: there is no search for bookings, only Find Customer. The actions that confirm, decline or cancel need the booking's Id, so an earlier step of the same Zap has to supply it, a MakePlans booking trigger for instance. There is no action to edit a booking or a customer either.

Comparing platforms first? See our n8n vs Zapier and Make vs Zapier pages.

Vocabulary

Zapier words, in one minute

Eight terms come back on this page. Each one, once, in plain words.

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 on, Zapier waits for it, here a booking or a new customer.
Action
What the Zap does once it has started: the step that writes, sends or changes something for you, such as confirming a booking.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app the moment it happens. All four MakePlans 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.
Search step
A step that looks up something that already exists in an app, such as a customer, so later steps can use what it found.
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 it really costs

A booking arriving costs nothing. Zapier bills what the Zap does with it.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Trigger speedInstant on all four triggers

The trigger never costs a task. Each action that succeeds is one task, and one that fails is not counted. The free plan gives 100 tasks a month and two-step Zaps, so Booking Verified plus Confirm Booking fits as is. A filter or a Find Customer step makes the Zap multi-step, which needs a paid plan. The interval grid below is Zapier's general one for polling triggers; it does not apply to the four MakePlans triggers, which are instant on every plan.

Connect

Connect MakePlans to Zapier

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. You need a MakePlans account first; Zapier links an existing one and does not create it.

  2. 02

    Pick MakePlans

    Type MakePlans in the search box of the dialog, select it and click Add connection. A new tab opens on the MakePlans side so you can sign in there as usual.

  3. 03

    Sign in and grant access

    Log in to MakePlans in that tab and allow Zapier to reach the account. Use a login that can see, and change, the bookings and customers your Zaps will touch.

First Zap

Your first Zap: confirm verified bookings that meet your rule

GoalWhen a booking is verified in MakePlans, confirm it automatically, but only when it meets the condition you set.

  1. 01

    Create the Zap

    Start a new Zap, pick MakePlans as the app that starts it and Booking Verified as the event. Choose your connection; the editor shows a lightning bolt, since this trigger is instant.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent bookings of the account, so you build the next steps on a real one and see which details it carries.

  3. 03

    Add the filter

    Add a filter from the plus icon and fill its three boxes: the field, the rule, the value. Pick a text rule for text and a number rule for numbers, or it will never pass.

  4. 04

    Add Confirm Booking

    Add MakePlans again with Confirm Booking and map the booking Id brought back by the trigger test into the required Id field. Nothing else is required for this step.

  5. 05

    Test and publish

    Test the action once on that real booking and check the result in MakePlans. Then click Publish. With the filter, this is a multi-step Zap on a paid plan.

Triggers

MakePlans triggers

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

1

Booking Cancelled

Instant trigger

In Zapier“Triggers when a booking is cancelled.”

Starts your Zap when a booking is cancelled, so a freed slot or a lost appointment can be dealt with outside MakePlans as well.

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 cancellations logged in a sheet or flagged to someone who can fill the gap.
Watch out
a Zap that ends with Cancel Booking should not start from this trigger, or each cancellation it makes will start it again.
2

New Booking Confirmed

Instant trigger

In Zapier“Triggers when a new booking is confirmed.”

Fires each time a new booking is confirmed, which makes it the natural starting point for anything that should follow a firm appointment.

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 confirmed slot should land in another calendar, a CRM or a team message straight away.
Watch out
it only covers new bookings once confirmed; a later cancellation needs its own Zap on Booking Cancelled.
3

Booking Verified

Instant trigger

In Zapier“Triggers when a new booking is verified.”

Hands each newly verified booking to the Zap, with its details, ready for the steps that decide what happens 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
you want a rule, through a filter, to confirm or decline bookings instead of doing it by hand.
Watch out
Confirm Booking and Decline Booking require the booking Id, so check during the test that this trigger brings it back.
4

New Customer

Instant trigger

In Zapier“Triggers when an appointment by a new customer is made on the MakePlans booking site.”

Reacts when someone books on your MakePlans booking site for the first time, so a new customer reaches your other tools without an export.

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 first-time booker should be added to your mailing tool or your contact list.
Watch out
it is tied to an appointment made on the MakePlans booking site, so plan around bookers rather than every contact.
Actions

MakePlans actions

MakePlans gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Cancel Booking

Action

In Zapier“Cancel a booking.”

Cancels a booking that was already made, so a decision taken in another tool reaches your MakePlans calendar.

When to use it
a cancellation is recorded elsewhere first and the slot should be freed in MakePlans.
Watch out
the booking Id is required, so the tool where the cancellation is logged must know it and hand it over.
2

Confirm Booking

Action

In Zapier“Confirm a booking.”

Confirms an existing booking from your Zap, so nobody has to do it by hand in MakePlans.

When to use it
verified bookings that meet a rule should be accepted without waiting for you.
Watch out
the booking Id is required, and no booking search exists to look it up for you.
3

Create Booking

Action

In Zapier“Create a booking.”

Books a slot in MakePlans from another tool, on the resource and between the start and end times you map in.

When to use it
requests arrive through a form or a chat and should become real appointments.
Watch out
Resource, From and To are all required, so the earlier step must provide clean times.
4

Decline Booking

Action

In Zapier“Decline a booking.”

Turns a booking down from inside a Zap, which pairs naturally with a filter that spots the ones you do not take.

When to use it
some requests fall outside what you accept and should be refused consistently.
Watch out
it needs the booking Id too, so an earlier step has to pass it along.
5

Create Customer

Action

In Zapier“Create new customer. Please note that either name, email or phone number is required for creating a customer.”

Adds a new customer record to MakePlans, so a contact who starts elsewhere is already known when they book.

When to use it
leads land in your CRM first and you want them ready in MakePlans.
Watch out
MakePlans needs at least a name, an email or a phone number to create the customer.
Searches

MakePlans search

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

A search step sits at the bottom of the action-event list, under the SEARCH heading. Three settings decide what happens when the result is not a single clean match.

1

Find Customer

Search

In Zapier“Finds an existing customer.”

Looks up a customer who already exists in MakePlans and hands their record to the steps that follow.

When to use it
before creating someone, check that they are not already there, then branch on the answer with a filter.
Watch out
MakePlans, not Zapier, decides whether it wants an exact value or a close one, so test it on a real customer.

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 and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this turns a search into find-or-create. Find Customer offers no such variant on Zapier, so the box is not there for it.
  3. If multiple search results are found?
    Three ways out when several customers match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When it breaks

Zapier links no help article and no app-specific limit to MakePlans. What can go wrong comes from how Zapier itself works.

  • Past bookings are never picked up

    A Zap only reacts to what happens after you switch it on. Bookings and customers that already exist are left alone; moving them is a separate job.

  • A Zap that sets itself off

    A Zap that writes where its own trigger watches, such as Cancel Booking after Booking Cancelled, starts itself again and again and burns tasks fast.

  • A sudden batch can be held back

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

  • Filters and searches need a paid plan

    The free plan builds two-step Zaps only. A filter or a Find Customer step in the middle makes the Zap multi-step, and it stops fitting the free plan.
Need help

Need help automating MakePlans with Zapier?

A person reads every message.

FAQ

MakePlans Zapier integration: common questions

01Is the MakePlans Zapier integration free?
Yes. MakePlans is not a premium app on Zapier, so it works on the free plan. That plan gives 100 tasks a month and Zaps of two steps, one trigger and one action, which covers a simple flow such as a verified booking that gets confirmed. Add a filter, a second action or a Find Customer step and the Zap becomes multi-step, which needs a paid plan. You also need your own MakePlans account, since Zapier only links an existing one.
02How many tasks does a MakePlans Zap use?
The trigger uses none: a booking or a new customer reaching Zapier is free. Each action that completes successfully counts as one task, per run. A Zap that only confirms a booking uses one task per booking; a Zap that creates a customer and then a booking uses two. An action that fails is not counted against your plan. On the free plan you have 100 tasks a month to spend that way.
03Does MakePlans reach Zapier in real time?
Yes. All four MakePlans triggers are instant: MakePlans tells Zapier the moment a booking is cancelled, confirmed or verified, or a new customer books, and the Zap starts right away. The plan's checking interval does not apply to them, which makes this integration as fast on the free plan as on a paid one. In the editor, a Zap built on one of these triggers shows a lightning bolt, so you can check it at a glance.
04What does it take to connect MakePlans to Zapier?
A MakePlans account, with a login that can see and change the bookings and customers your Zaps will use, including those you do not own. In Zapier, open the Apps page, click + Add connection, search for MakePlans, click Add connection, sign in on the tab that opens and grant access. The connection is then reused by every MakePlans step, so you set it up once and pick it from a list afterwards.
05What does a Zap need to confirm or decline a booking?
The booking's Id. Confirm Booking, Decline Booking and Cancel Booking all require it, and MakePlans offers no search to find a booking on Zapier. So an earlier step of the same Zap has to supply that Id. A MakePlans booking trigger such as Booking Verified is the obvious candidate: test it, check that the Id is among what comes back, then map it into the action. If the Zap starts in another tool, that tool has to know the Id itself.
06What if the MakePlans operation you need is missing?
Then Zapier does not offer it today. The MakePlans app covers four booking and customer triggers, five actions to create, confirm, decline or cancel bookings and to create customers, and one search for customers. There is no action to edit a booking or a customer and no search for bookings. A flow that depends on those cannot be built with this integration alone, so check whether the step can happen on another side of the Zap.
07Zapier, Make or n8n for MakePlans?
Decide on criteria, not on a ranking. First, check which platform actually offers a ready-made MakePlans connection with the operations you need; on Zapier that is four instant triggers, five actions and one search. Second, compare billing: Zapier counts tasks, meaning successful actions, and the trigger is free. Third, look at speed: here every trigger is instant, so the plan interval does not slow anything down. Weigh those against the tools your team already runs.
Same platform

Other docs you might need on this stack.

Browse all integrations