Resources · Make integration

MakePlans Make integrationAutomate MakePlans with Make.

Can Make react the moment a booking changes in MakePlans? Yes: the MakePlans Make integration gives you 22 modules, including 8 instant triggers. This page is for people who run a booking calendar, and it walks you from the API key to a first working scenario.

Try the MakePlans integration on MakeSee the 22 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MakePlans Make integration let you automate?

The MakePlans Make integration links your MakePlans account to Make, a no-code tool where you build a scenario (the automation itself: a chain of modules, each one a brick that watches, acts or searches). MakePlans can alert Make whenever a booking or a customer changes, and Make can create, update or cancel bookings for you.

Bookings that come from elsewhere. A request arrives through a form in another app. Create a Booking turns it into a real slot in MakePlans, so nobody retypes dates by hand.

A customer file that stays in sync. Watch Created People fires when someone new appears in MakePlans. From there you can send the contact to the tool your team already uses, and Update a Person covers the reverse path when details change elsewhere.

Follow-up on every status change. Confirmed, declined, verified, canceled: each status has its own instant trigger. A cancellation can free a spot in your planning sheet, and a confirmation can send a message through another app.

What Make does not do here: the listed modules only cover bookings and people. For anything else in the MakePlans API, the Make an API Call module reuses the same connection. MakePlans may also exist on n8n; the n8n vs Make page lays out the differences, and the Make review helps you judge Make itself. Stuck on a run? Make troubleshooting lists the usual fixes.

Connect

How do you connect MakePlans to Make?

  1. 01

    Switch on the API in MakePlans

    In MakePlans, open Setup in the main menu, then Integrations, then the API section. Turn the API on if it is off, and copy the API key shown there. Your account needs API access for this to work.

  2. 02

    Add a MakePlans module in Make

    In your scenario, add any MakePlans module and click Create a connection. A connection is your MakePlans account linked to Make once, then reused by every MakePlans module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the instructions Make shows on screen, then save. Make now reads your MakePlans data, and the next MakePlans module you add will offer this connection in its list.

First scenario

Your first scenario: turn outside requests into MakePlans bookings

GoalWhen a request lands in another app, Make creates the matching booking in MakePlans.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where requests arrive, such as your form tool, and choose its module that brings in new entries.

  2. 02

    Add Create a Booking

    Click the + to the right of that first module, search for MakePlans and pick Create a Booking. Select your connection, or click Create a connection if this is your first MakePlans module.

  3. 03

    Map the request into the booking

    Fill the fields Make displays for the booking. Instead of typing values, click into a field and pick data from the first module, so each request carries its own details into MakePlans.

  4. 04

    Test with Run once

    Send one test request in the other app, then click Run once. Open the bubble above each module to read the bundle it received, a bundle being one item passed along, here one request.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule; a new scenario checks every 15 minutes by default. Then switch the scenario on. Each module run on one bundle counts as an operation on your Make plan.

Triggers

The MakePlans triggers: what starts your scenario

8 modules start a scenario when something happens in MakePlans. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by MakePlans as soon as it happens.

MakePlans1Watch Canceled Bookings

Watch Canceled Bookings

Instant trigger

In Make“Watches for canceled bookings.”

Gives you a signal the moment a customer or your team cancels a booking, so the empty slot never goes unnoticed. The scenario gets the canceled booking as a bundle and can pass it to any next step.

How it fires
instant, MakePlans calls Make through a webhook as soon as it happens.
When to use it
you keep a waiting list and want the next person told that a place opened up.
Watch out
a canceled booking is not a deleted one; deletions have their own trigger, Watch Deleted Bookings.
MakePlans2Watch Confirmed Bookings

Watch Confirmed Bookings

Instant trigger

In Make“Watches for confirmed bookings.”

Hands your scenario each booking at the point it becomes confirmed, which is usually when the real work begins: preparing the room, the material or the reminder message.

How it fires
instant, MakePlans calls Make through a webhook as soon as it happens.
When to use it
only confirmed appointments should reach your shared calendar or your invoicing tool, not every raw request.
Watch out
if bookings in your account are confirmed by hand, the scenario waits for that click, not for the original request.
MakePlans3Watch Created Bookings

Watch Created Bookings

Instant trigger

In Make“Watches for created bookings.”

Catches every new booking the instant it lands in MakePlans, whatever its later status. This is the widest net of the eight triggers and the easiest one to start with.

How it fires
instant, MakePlans calls Make through a webhook as soon as it happens.
When to use it
you want a line in a spreadsheet or a message in a team channel for each booking made, even before anyone reviews it.
Watch out
a booking created and then declined still fires here, so add a later check if only approved ones matter.
MakePlans4Watch Created People

Watch Created People

Instant trigger

In Make“Watches for created people.”

Brings each new person record from MakePlans into Make, so your contact list elsewhere grows by itself instead of through exports. It watches customers, not bookings.

How it fires
instant, MakePlans calls Make through a webhook as soon as it happens.
When to use it
your CRM or newsletter tool should hold every client who signs up in MakePlans, and you want that without copying rows.
Watch out
this trigger does not know what already exists outside MakePlans, so if duplicates worry you, search for the contact in the destination tool first.
MakePlans5Watch Declined Bookings

Watch Declined Bookings

Instant trigger

In Make“Watches for declined bookings.”

Lets you close the loop with anyone whose booking request was turned down, instead of leaving them without an answer. The declined booking arrives in Make with its details.

How it fires
instant, MakePlans calls Make through a webhook as soon as it happens.
When to use it
a polite message offering other slots, or a note in your CRM, should follow each refusal.
Watch out
if the decline itself comes from a Make scenario using Decline a Booking, keep the follow-up in that scenario rather than in a second one that listens for the same event.
MakePlans6Watch Deleted Bookings

Watch Deleted Bookings

Instant trigger

In Make“Watches for deleted bookings.”

Tells Make when a booking is removed, so the copies you keep in other tools can be cleaned up and stop showing appointments that no longer exist.

How it fires
instant, MakePlans calls Make through a webhook as soon as it happens.
When to use it
bookings are mirrored in a shared calendar or a sheet, and a deletion in MakePlans must remove the matching entry there.
Watch out
MakePlans marks a deleted booking as deleted and inactive rather than erasing it, so the bundle still carries the booking data you can match on.
MakePlans7Watch Modified Bookings

Watch Modified Bookings

Instant trigger

In Make“Watches for modified bookings.”

Keeps your other tools honest when a booking moves or changes: Make receives the updated version each time someone edits it in MakePlans.

How it fires
instant, MakePlans calls Make through a webhook as soon as it happens.
When to use it
a customer reschedules and the staff member's calendar or a planning sheet has to show the new slot without anyone noticing it by chance.
Watch out
a scenario that listens here and also runs Update a Booking on the same booking can start itself again; filter those changes out before switching it on.
MakePlans8Watch Verified Bookings

Watch Verified Bookings

Instant trigger

In Make“Watches for verified bookings.”

Picks up each booking once it reaches the verified state in MakePlans, which lets you reserve the heavier follow-up for bookings that passed that step.

How it fires
instant, MakePlans calls Make through a webhook as soon as it happens.
When to use it
your process separates a first request from a checked one, and only checked bookings should trigger an invoice or a welcome pack.
Watch out
the Make documentation does not explain what verification means in your account, so check in MakePlans which bookings go through it before relying on this trigger.
Modules

What the MakePlans modules can do

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

MakePlans1

Cancel a Booking

Action

In Make“Cancels a specified booking.”

Cancels an existing booking from inside a scenario, so a cancellation made somewhere else lands in MakePlans without a trip to its dashboard. You point it at the booking to cancel.

When to use it
a customer answers a reminder email or fills a form saying they cannot come.
Watch out
use it rather than Delete a Booking when you want the history to show a cancellation.
MakePlans2

Create a Booking

Action

In Make“Creates a new booking.”

Adds a new booking to MakePlans from data another module passes in, which is how requests collected outside MakePlans become real slots in the calendar.

When to use it
a form, a chat or a sales tool gathers the request and you do not want anyone rekeying it.
Watch out
run it once with a test entry and check the result in MakePlans before switching the scenario on, since every run adds a booking.
MakePlans3

Create a Person

Action

In Make“Creates a new person.”

Registers a new customer in MakePlans, so the person exists before any booking is made for them and your client list stays in one place.

When to use it
a lead signs up in another tool and should be ready to book without filling their details a second time.
Watch out
run List People first to look for that customer, otherwise the same person can end up created twice.
MakePlans4

Decline a Booking

Action

In Make“Declines a specified booking.”

Turns down a booking request on your behalf, which fits when the rule for refusing is clear enough that a scenario can apply it without a person deciding.

When to use it
a check in another tool shows the slot cannot be honored, and the refusal should reach MakePlans straight away.
Watch out
a decline sent by mistake reaches a real customer, so test with Run once on a dummy booking first.
MakePlans5

Delete a Booking

Action

In Make“Deletes a specified booking. Deleting a booking will set its state to deleted and active to false.”

Removes a booking from active use in MakePlans. Under the hood it is not erased: its state becomes deleted and it is marked inactive, so it drops out of the live calendar.

When to use it
test bookings or duplicates created by another scenario need clearing out.
Watch out
for a customer who simply is not coming, Cancel a Booking tells a clearer story than a deletion.
MakePlans6

Delete a Person

Action

In Make“Deletes a specified person.”

Removes a customer record from MakePlans, handy when the person also disappears from your main contact list and should not linger in the booking tool.

When to use it
a customer asks to be forgotten and the request is handled in your CRM, which then passes the word to MakePlans.
Watch out
the Make documentation says nothing about restoring a deleted person, so treat this as final and test on a dummy record.
MakePlans7

Get a Booking

Action

In Make“Returns a specified booking.”

Fetches the full details of one booking you already know, so later modules can use data that the triggering event did not carry.

When to use it
another app sends you only a booking reference, and you need the rest before writing a message or an invoice.
Watch out
it reads a single booking; to look through several, List Bookings is the right tool.
MakePlans8

Get a Person

Action

In Make“Returns information about a specified person.”

Pulls the information MakePlans holds about one customer, which turns a bare reference into customer details you can put in an email or a CRM record.

When to use it
right after a booking trigger, when the message you send needs to address the customer properly.
Watch out
it expects one specific person; when you only have a search term, use List People.
MakePlans9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole MakePlans API to your scenario with the connection you already set up, for the cases the ready-made modules leave out.

When to use it
you need something beyond bookings and people, and the MakePlans API documentation describes the endpoint for it.
Watch out
this module asks you to write the request yourself, so keep it for gaps and prefer a dedicated module whenever one exists.
MakePlans10

Update a Booking

Action

In Make“Updates a specified booking.”

Changes an existing booking in MakePlans, so a reschedule or a correction made in another tool shows up in the calendar your customers see.

When to use it
your team edits appointments in a shared planning sheet and MakePlans should follow that sheet.
Watch out
in a scenario started by Watch Modified Bookings, this update is itself a modification that the trigger can pick up; add a filter so the scenario does not loop.
MakePlans11

Update a Person

Action

In Make“Updates a specified person.”

Edits a customer record in MakePlans, which keeps contact details consistent when your CRM is where people actually get corrected.

When to use it
a customer updates their contact details in your main tool, and the booking tool should hold the same data.
Watch out
find the right person first with Get a Person or List People, or the change lands on the wrong record.
MakePlans12

Verify a Booking

Action

In Make“Verifies a specified booking.”

Moves a booking to the verified state from a scenario, handy when the check that justifies it happens outside MakePlans.

When to use it
another tool confirms that a condition you require is met, and the booking should advance without a manual click.
Watch out
Watch Verified Bookings listens for this exact change, so a scenario that uses both can start itself again; add a filter.
MakePlans13

List Bookings

Search

In Make“Returns a list of bookings or searches them by specified queries.”

Returns a batch of bookings, or only those matching the query you set, each one as its own bundle. It is a search module: the result can be zero, one or many bookings.

When to use it
you want to push every upcoming booking into a sheet or check what already exists before creating one.
Watch out
every returned booking runs the next modules once, which adds operations on your plan.
MakePlans14

List People

Search

In Make“Returns a list of people or searches people by specified queries.”

Searches the MakePlans customer base and hands back each match as a separate bundle, or the whole list when you set no query.

When to use it
before Create a Person, to check whether that customer is already in MakePlans and avoid a duplicate.
Watch out
an empty result is a normal outcome, so add a route for the case where nobody matches.
Need help

Need help automating MakePlans with Make?

A person reads every message.

FAQ

MakePlans and Make: common questions

01Is the MakePlans Make integration free?
Yes, on the Make side. MakePlans is a standard app, so its modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans raise these limits. Your MakePlans account is a separate matter: it needs API access, and the MakePlans pricing page tells you which subscription includes it.
02What do you need to connect MakePlans to Make?
An active MakePlans account with API access, plus the API key. You find it in MakePlans under Setup, then Integrations, then the API section, where you switch the API on if needed and copy the key. In Make, add a MakePlans module, click Create a connection and paste the key. For a trigger, the window starts with Create a webhook, and the connection comes right after. Give the connection a clear name so you recognize it later.
03Do MakePlans triggers in Make fire instantly?
Yes. All 8 MakePlans triggers are instant: MakePlans calls Make through a webhook as soon as a booking or a person changes, so the scenario does not wait for a schedule. On the editor, these modules carry the lightning badge. The trade-off is setup order: you create the webhook first, then the connection, and the scenario must be switched on for the webhook to be received. If a trigger stays silent, check first that the scenario is on.
04What if the MakePlans module you need is missing?
Use Make an API Call. It reaches any endpoint of the MakePlans API with the connection you already have, so you are not limited to the 22 listed modules. The ready-made ones cover bookings and people; anything else goes through this module and the MakePlans API documentation. Keep in mind that the Make documentation for this app is AI-generated from the MakePlans docs, so verify important details with MakePlans directly.
05Should you use Make or n8n for MakePlans?
It depends on what you already run. On Make, MakePlans comes with 22 modules, 8 of them instant triggers, and works from the Free plan. n8n often has a node for the same app, so check its catalog before deciding. The practical question is where the rest of your automations live: keeping MakePlans in the same tool as your CRM and calendars makes scenarios easier to follow and maintain. Both routes start from the same MakePlans API key.
Same platform

Other docs you might need on this stack.

Browse all integrations