Resources · Make integration

Planyo Make integrationAutomate Planyo with Make.

What if every Planyo booking could start the next task by itself? The Planyo Make integration brings 23 modules: 9 instant triggers, 11 actions and 3 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Planyo integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Planyo Make integration do for you?

The Planyo Make integration links your booking system to Make, so reservations, payments and customer records can move to other tools without copy and paste. You build a scenario, which is the automation itself: a chain of modules, each module being one brick such as a trigger, an action or a search.

Confirmed bookings that reach the rest of your stack. Watch Reservations Confirmed starts a scenario the moment a booking is confirmed, and Get a User pulls the customer details you want to pass along, for a welcome message or a line in a shared sheet.

Cancellations sorted by who made them. Planyo splits cancellations into three triggers: by the customer, by an admin, or automatic. A rental team can treat each case differently, for example alerting staff only when a customer cancels.

Bookings created from outside Planyo. When a request lands in another tool, Add a User and Make a Reservation enter the customer and the booking without anyone retyping it. Add a Vacation blocks a resource when it is unavailable.

The documentation lists no specific limit for this app, and for anything the listed modules skip, Make an API Call reaches the rest of the Planyo API. Planyo may also exist as an n8n node: the n8n vs Make page explains how the two tools differ. For the bigger picture, read our Make review or check Make pricing before you choose a plan.

Connect

How do you connect Planyo to Make?

  1. 01

    Copy your Planyo API key

    In Planyo, open the API section from your user dashboard and click the API key button. The key shows on that page: copy it and keep it at hand, Make will ask for it in a moment.

  2. 02

    Add a Planyo module

    In your Make scenario, add any Planyo module and click Create a connection. The Connection name field is optional, but a clear name helps when several Planyo sites are linked to the same Make account.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the instructions shown on screen, then save. This connection, your Planyo account linked to Make once, is reused by every Planyo module you add afterwards.

First scenario

Your first scenario with Planyo

GoalWhen a booking request arrives from another app, Make creates the customer in Planyo, then enters the reservation.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module is the app where requests come in, for instance your form tool or your inbox.

  2. 02

    Add Add a User

    Click the + on the right, search Planyo and pick Add a User. Click Create a connection and paste your API key if the connection does not exist yet.

  3. 03

    Map the customer details

    Fill the fields of Add a User with the data from the first module: Make shows each value the previous module received, so you click it instead of typing it.

  4. 04

    Add Make a Reservation

    Add Make a Reservation after it and map the booking details from the request, plus what Add a User returned, so the reservation belongs to the right customer.

  5. 05

    Test with Run once

    Click Run once and send a test request. Each module shows the bundles it received, a bundle being one item passing through, here one customer and one booking.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From then on, each request becomes a Planyo booking without manual entry.

Triggers

What can start a Planyo scenario?

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

Planyo1Watch New Reservations

Watch New Reservations

Instant trigger

In Make“Triggers when a new reservation has been added.”

Your scenario starts as soon as a booking is added to Planyo, carrying that reservation into Make so the next modules can use it. It is the most general entry point of the app.

How it fires
instant, Planyo calls Make through a webhook as soon as the booking exists, shown by the lightning badge on the module.
When to use it
any follow-up that must happen for every new booking, such as a note to the team or a row in a planning sheet.
Watch out
it follows every added booking; if only confirmed ones matter to you, Watch Reservations Confirmed is the more precise choice.
Planyo2Watch Payments Received

Watch Payments Received

Instant trigger

In Make“Triggers when a new payment has been received.”

Each payment recorded in Planyo sends one bundle to Make, which lets you react to money coming in rather than to the booking itself. Useful when the booking and the payment happen at different moments.

How it fires
instant, through a webhook Planyo calls the moment the payment is received.
When to use it
telling the accounting tool or the team that a deposit has arrived for a stay or a rental.
Watch out
this page does not know which payment details the bundle holds, so click Run once with a real payment and read the bundle before you map anything.
Planyo3Watch Reservations Cancelled Automatically

Watch Reservations Cancelled Automatically

Instant trigger

In Make“Triggers when a reservation has been cancelled automatically.”

Here Make hears about the bookings Planyo cancels on its own, without anyone clicking a button. That gives you a trace of reservations that disappeared by system rule rather than by choice.

How it fires
instant, Planyo sends a webhook to Make as soon as the automatic cancellation happens.
When to use it
warning the customer or the front desk that a slot has been freed, so it can be offered again.
Watch out
cancellations made by the customer or by an admin do not pass through this trigger; each has its own module further down.
Planyo4Watch Reservations Cancelled by a Customer

Watch Reservations Cancelled by a Customer

Instant trigger

In Make“Triggers when a reservation has been cancelled by a customer.”

Only cancellations made by the customer land here, which isolates the case where the person who booked changed their mind. Your scenario receives that booking and can act on it right away.

How it fires
instant, the webhook reaches Make the moment the customer cancels in Planyo.
When to use it
asking the customer why they left, or alerting a manager who might offer another date.
Watch out
an admin cancelling on behalf of the customer triggers Watch Reservations Cancelled by Admin instead, so test both paths before relying on this one alone.
Planyo5Watch Reservations Cancelled by Admin

Watch Reservations Cancelled by Admin

Instant trigger

In Make“Triggers when a reservation has been cancelled by admin.”

When someone on your side cancels a booking in the Planyo back office, this module passes that reservation to Make. It covers staff decisions, not customer ones.

How it fires
instant, Planyo calls Make through a webhook right after the admin cancels.
When to use it
sending the customer a clear notice whenever the team has to cancel, for a closed venue or a broken resource.
Watch out
the message leaves as soon as the cancellation is saved, so check your wording with Run once before switching the scenario on.
Planyo6Watch Reservations Confirmed

Watch Reservations Confirmed

Instant trigger

In Make“Triggers when a reservation has been confirmed.”

A booking reaches Make at the moment it moves to confirmed, which is often the point where the real work begins. Nothing fires for requests still waiting for approval.

How it fires
instant, Planyo notifies Make through a webhook as soon as the confirmation is saved.
When to use it
preparing what the customer needs for their visit, or blocking the slot in another calendar once the booking is certain.
Watch out
if your site confirms bookings immediately, this trigger and Watch New Reservations may both fire for the same booking, so choose one of them per scenario.
Planyo7Watch Reservations Modified by Admin

Watch Reservations Modified by Admin

Instant trigger

In Make“Triggers when a reservation has been modified by admin.”

Changes your staff make to an existing booking are sent to Make with this module, so other tools stay in line with the new version of the reservation.

How it fires
instant, a webhook from Planyo reaches Make as soon as the admin saves the change.
When to use it
updating a shared schedule or telling the customer when the team moves their date or resource.
Watch out
edits made by the customer go through Watch Reservations Updated by a Customer, a separate trigger, so a scenario built on this one will not see them.
Planyo8Watch Reservations Updated by a Customer

Watch Reservations Updated by a Customer

Instant trigger

In Make“Triggers when a reservation has been updated by a customer.”

Whenever a customer edits their own booking, Make receives the updated reservation and your scenario can react without anyone checking Planyo by hand.

How it fires
instant, Planyo calls Make through a webhook the moment the customer saves the edit.
When to use it
letting the person who prepares the room or the equipment know that something changed on a booking they handle.
Watch out
the bundle shows the booking after the edit; this page cannot tell you whether the previous values come with it, so read the bundle after a Run once test.
Planyo9Watch Users Updated

Watch Users Updated

Instant trigger

In Make“Triggers when a user has been updated.”

This trigger follows your customers rather than their bookings: each time a user record changes in Planyo, the new version goes to Make.

How it fires
instant, the change reaches Make through a webhook as soon as it is saved in Planyo.
When to use it
keeping a CRM or a mailing list in line when a customer corrects their phone number or email.
Watch out
if your scenario writes back to the same user with Update a User, it can call itself again, so never close that loop inside one scenario.
Modules

What each Planyo module does

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

Planyo1

Add a User

Action

In Make“Adds a new user(customer) associated with your Planyo site.”

Creates a new customer on your Planyo site, so a person who contacted you elsewhere already exists before any booking is made for them.

When to use it
a request comes from a form or an email and the customer has never booked with you.
Watch out
nothing on this page says Planyo stops duplicates, so run List Users first when the customer may already exist.
Planyo2

Add a Vacation

Action

In Make“Adds a new one-time vacation for given resource or entire Planyo site.”

Blocks time in Planyo, either for one resource or for the whole site, so nobody can book it during that period. In Planyo, a vacation is simply a one-time closed period.

When to use it
a maintenance ticket or a staff absence recorded in another tool should close the matching slots automatically.
Planyo3

Delete a Reservation

Action

In Make“Permanently removes a reservation.”

Removes a booking from Planyo for good, which clears it from your planning and frees the slot it was holding.

When to use it
test bookings or duplicate entries that should leave no trace.
Watch out
the removal is permanent and cannot be undone from Make, so for a real customer a cancellation is usually the safer route; test it on a dummy booking first.
Planyo4

Get a Reservation

Action

In Make“Gets a reservation.”

Fetches one booking from Planyo so the following modules can read its details, even when your scenario started somewhere else.

When to use it
a trigger or another app gives you a reservation reference, and you need the rest of the booking to write a message or fill a sheet.
Watch out
it needs one precise reservation; to browse several, use List Reservations.
Planyo5

Get a User

Action

In Make“Gets user data.”

Reads the record of one Planyo customer and hands those details to the next modules, which saves you from asking the customer twice.

When to use it
right after a booking trigger, when your follow-up needs the customer's contact data rather than just the booking.
Watch out
run it once and check which details the bundle really contains before you build a message around them.
Planyo6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Planyo API from your scenario, using the same connection as the other modules, for anything the 23 listed modules do not cover.

When to use it
you know which Planyo endpoint does what you need and no ready module offers it.
Watch out
you write the request yourself, so keep the Planyo API documentation open while you set it up.
Planyo7

Make a Reservation

Action

In Make“Enters a new reservation into the system.”

Enters a new booking in Planyo from Make, so a request received in another tool turns into a real reservation without retyping.

When to use it
bookings taken by phone, chat or a partner site that you log in a sheet or a form.
Watch out
run a test on a spare resource with Run once, because a wrong mapping creates a real booking your customers will see as taken.
Planyo8

Remove a User

Action

In Make“Removes a user.”

Takes a customer out of your Planyo site, so their record no longer shows up among your users.

When to use it
a deletion request handled in your CRM or support tool should reach Planyo as well, without someone doing it twice.
Watch out
nothing here tells what happens to that user's bookings, so try it on a test account before any real one.
Planyo9

Remove a Vacation

Action

In Make“Removes a specified vacation.”

Deletes a closed period you set earlier, so those dates can be booked again on the resource or across the whole site it covered.

When to use it
maintenance ends early. Or a planned absence gets cancelled in the tool where your team tracks who is off, and Planyo should reopen those days too.
Watch out
it targets one specific vacation, so pair it with List Vacations when you only know the dates.
Planyo10

Update a Reservation

Action

In Make“Updates a reservation.”

Changes an existing booking in Planyo from your scenario, keeping the reservation in line with what was agreed elsewhere.

When to use it
a customer asks your support team for a change and the ticket tool holds the new details.
Watch out
a scenario that starts on Watch Reservations Modified by Admin and ends with this module can keep firing on its own changes, so keep those two apart.
Planyo11

Update a User

Action

In Make“Modifies an existing user's data.”

Edits the data of an existing Planyo customer, so the contact details you use for bookings match the ones in your other tools.

When to use it
a customer updates their email in your CRM and Planyo should follow.
Watch out
leave Watch Users Updated out of the same scenario, otherwise each update can trigger the next one.
Planyo12

List Reservations

Search

In Make“Lists all reservations that either start within given time period or that were entered into the system within given time period.”

Returns the bookings that start within a period, or that were entered during a period, one bundle per reservation, ready for a report or a check.

When to use it
building an overview of the upcoming arrivals or of the bookings logged over a given stretch of time.
Watch out
as a search it can return zero, one or many bundles, and every module placed after it runs once per booking, which counts operations.
Planyo13

List Users

Search

In Make“Lists users.”

Searches the customers of your Planyo site and returns them as separate bundles, so you can check who exists before acting.

When to use it
before Add a User, to avoid creating the same customer twice when requests come from several channels.
Watch out
an empty result is normal for a new customer, so plan what the scenario does when nothing comes back.
Planyo14

List Vacations

Search

In Make“Lists all vacations within specified time range.”

Shows the closed periods set within a date range, one bundle each, so you know which slots Planyo keeps unavailable.

When to use it
checking closures before promising a date to a customer, or finding the vacation you want to remove.
Watch out
each vacation found sends the following modules into one more operation, an operation being one module run that Make counts on your plan.
Need help

Need help automating Planyo with Make?

A person reads every message.

FAQ

Planyo and Make: common questions

01Is the Planyo Make integration free?
Yes, Planyo is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios, with usage counted in operations each month. You still need a Planyo account with an API key, and Planyo sets its own subscription terms.
02What do you need to connect Planyo to Make?
An active Planyo account and its API key. In Planyo, open the API section from your user dashboard, click the API key button and copy the key. In Make, add a Planyo module, click Create a connection, give it a name if you like, and paste the key. For instant modules, Make first asks you to click Create a webhook, then Create a connection. The connection is stored once and reused by every Planyo module in your scenarios.
03Do Planyo triggers in Make fire instantly?
Yes. All 9 Planyo triggers in Make are instant: Planyo calls Make through a webhook as soon as the event happens, whether it is a new booking, a payment, a confirmation, a change or a cancellation. You see a lightning badge on these modules, while scheduled triggers show a clock. The 15 minute default schedule applies to scenarios that start with a scheduled module, such as one opening on another app.
04What if the Planyo module you need is missing in Make?
Use Make an API Call. It sends any request to the Planyo API with the connection you already set up, so you can reach what the 23 listed modules leave aside. You need to know which Planyo endpoint does the job, so keep the Planyo API documentation at hand. The Make documentation for this app lists no specific limit, and it notes that parts of it are generated from Planyo sources, so check important details with Planyo.
05Should you pick Make or n8n for Planyo?
It depends on the tool you already use. On Make, Planyo comes with 23 ready modules, including 9 instant triggers covering bookings, payments, cancellations and user changes, and it runs from the Free plan. n8n often offers a node for the same app, so compare the modules you need on both sides before deciding. If your team already builds scenarios in Make, staying there keeps every automation in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations