- Home
- Resources
- Integrations
- Planyo Online Booking
Planyo Online Booking Zapier integrationAutomate Planyo Online Booking with Zapier.
The Planyo Online Booking Zapier integration gives you 17 triggers and 3 actions, no search. Every trigger is instant, so a booking, a payment or a check-in reaches your other tools without waiting, even on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Planyo Online Booking Zapier integration actually does
It links your Planyo booking system to the rest of your tools without code. Planyo reports what happens to a reservation (created, confirmed, paid, changed, cancelled, checked in or out) and Zapier carries it elsewhere. In the other direction, Zapier can add a customer, block a period or enter a reservation in Planyo for you.
Three results you can build on day one. A live booking log: New Reservation starts a Zap (an automation on Zapier) that writes each booking into a sheet or a CRM, so the front desk stops copying by hand. A payment alert: New Payment pings accounting the moment a guest pays. A closed calendar: Create Vacation blocks a resource in Planyo when another tool says it is out of service, so nobody books a boat that is in the yard.
Now the limits, because they matter. This integration has no search step: a Zap cannot look up an existing reservation or customer in Planyo. It also has no action to cancel, edit or check in a booking; those changes happen in Planyo and come out as triggers. And the six reminder triggers only fire on rules you define in Planyo itself, not in Zapier.
If you are weighing other platforms, the Make vs Zapier comparison is there, and the Zapier review covers the tool as a whole.
Zapier vocabulary in one minute
Seven words you will meet in the editor. Each one is explained once here, then used as is.
- Zap
- The automation you build: 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. Once the Zap is switched on, Zapier sits and waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully; your plan counts those.
- Instant trigger
- The app itself reports the event to Zapier when it happens, so nothing waits for a scheduled check. All Planyo triggers work this way.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items and keeping only the ones it has not seen yet.
- Filter
- A step that lets the Zap go on only when what arrived matches your condition, and stops it there otherwise.
What a Planyo Zap really costs
Planyo is not a premium app (Zapier's label for apps reserved to paid plans), so it works on the free plan.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, 2-step Zaps
- Premium appNo
The trigger never costs a task. Each action that succeeds counts as one task, and a failed action is not billed. The free plan gives you 100 tasks a month and Zaps of two steps only: one trigger, one action. Add a second action or a filter and it becomes a multi-step Zap, which needs a paid plan. The polling grid below does not touch you here: every Planyo trigger is instant. A search step would do the same, but Planyo has none.
Connect your Planyo account in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Planyo account linked once, then reused by every Zap that touches Planyo.
- 02
Pick Planyo Online Booking
Type the app name in the dialog, select Planyo Online Booking, then click Add connection. You need an existing Planyo account; Zapier does not create one for you.
- 03
Sign in and grant access
Log in to Planyo in the tab that opens and let Zapier access the account. If you manage a site you do not own, check first that your login can read and write the resources the Zap will use.
Your first Planyo Zap
GoalLog every new booking in a sheet and email the team about it.
- 01
Choose the trigger
Start a new Zap, pick Planyo Online Booking as the app and
New Reservationas the event. Select the connection you just created. - 02
Test it on a real booking
Run the trigger test. Zapier brings back the three most recent items of your account, so you map the next steps on an actual reservation instead of a blank one.
- 03
Add the sheet action
Add the sheet step, choose the target file and map the booking values into its columns. Test the step and read what came back before going further.
- 04
Add the email
Add the email step and map the reservation details into the message. Two actions make this a multi-step Zap: it needs a paid plan and uses two tasks per booking.
- 05
Publish
Click Publish to switch the Zap on. From then on, each new booking runs it; reservations made before that moment stay where they are.
Planyo Online Booking triggers
17 events start a Zap when something happens in Planyo Online Booking, and 17 of them are instant: the app calls Zapier straight away, whatever your plan.
Before or After Event #1
Instant triggerIn Zapier“Triggers a given number of hours/days before or after the rental begins or ends.”
This is the first of six timed reminders: it starts a Zap a set number of hours or days before or after a rental begins or ends. You decide the offset and the reference point in Planyo, not in Zapier.
Before or After Event #2
Instant triggerIn Zapier“Triggers a given number of hours/days before or after the rental begins or ends (#2 event defined in Notifications in the Planyo backend).”
A second, independent timer. It follows event #2 as you define it under Notifications in the Planyo backend, so you can run a different message from the one tied to #1 on the same bookings.
Before or After Event #3
Instant triggerIn Zapier“Triggers a given number of hours/days before or after the rental begins or ends (#3 event defined in Notifications in the Planyo backend).”
Slot number three, again configured under Notifications in the Planyo backend. Keeping one purpose per slot makes your Zaps easier to read months later.
Before or After Event #4
Instant triggerIn Zapier“Triggers a given number of hours/days before or after the rental begins or ends (#4 event defined in Notifications in the Planyo backend).”
Use slot four for anything tied to the start of a booking that the first three slots do not already cover. It reads the event #4 rule from the Notifications section of your Planyo backend.
Before or After Event #5
Instant triggerIn Zapier“Triggers a given number of hours/days before or after the rental begins or ends (#5 event defined in Notifications in the Planyo backend).”
The fifth timer is handy for internal follow-ups that customers never see. As with the other numbered slots, its timing lives under Notifications in the Planyo backend.
Before or After Event #6
Instant triggerIn Zapier“Triggers a given number of hours/days before or after the rental begins or ends (#6 event defined in Notifications in the Planyo backend).”
The last numbered slot, defined in Planyo Notifications like the previous ones. Teams often keep it for a long-range nudge, well before or well after the stay.
Update of Reservation Status to Checked-In
Instant triggerIn Zapier“Triggers when the customer checks in.”
Fires when a customer checks in, meaning the status of the booking moves to Checked-In in Planyo. It reacts to the status change, not to the scheduled start of the rental.
Update of Reservation Status to Checked-Out
Instant triggerIn Zapier“Triggers when the customer checks out.”
The mirror of the previous trigger: it starts when the customer checks out and the reservation status moves to Checked-Out. It is the cleanest signal that a unit is free again.
New Reservation
Instant triggerIn Zapier“Triggers when a new reservation is made.”
The workhorse of this integration. Each new booking made in Planyo starts the Zap, whether a customer booked online or staff entered it.
Create Reservation in the same Planyo site creates a booking that fires the trigger again, endlessly.Update of Reservation Status to Cancelled by Admin
Instant triggerIn Zapier“Triggers when a reservation is cancelled by an admin.”
Starts when someone on your side cancels a reservation in Planyo. Customer cancellations and automatic ones have their own triggers, so this one tells you the decision came from staff.
Update of Reservation by Admin
Instant triggerIn Zapier“Triggers when a reservation is modified by an admin.”
Runs each time an admin edits an existing booking in Planyo, whatever the change. It covers changes, not new bookings and not cancellations.
Automatic Update of Reservation Status to Cancelled
Instant triggerIn Zapier“Triggers when a reservation is automatically cancelled according to the cancellation rules set for the resource.”
Here nobody clicked anything: Planyo cancelled the booking itself, following the cancellation rules set for that resource. That makes it the trigger to watch for lost revenue.
New Reservation Is Confirmed
Instant triggerIn Zapier“Triggers when a reservation gets confirmed.”
Waits for the confirmation step rather than the booking itself. If your workflow reviews requests before accepting them, this is the moment the booking becomes real.
New Payment
Instant triggerIn Zapier“Triggers when a new payment is made.”
Starts on each payment recorded in Planyo. It is the trigger for anything money-related: invoicing, bookkeeping or a thank-you note.
Update of Reservation Status to Cancelled by Customer
Instant triggerIn Zapier“Triggers when a reservation is cancelled by the customer.”
Fires only when the customer cancels their own booking. Separating it from admin and automatic cancellations lets you treat each case with a different tone.
Update of Reservation by Customer
Instant triggerIn Zapier“Triggers when a reservation is modified by the customer.”
Runs when the customer changes their own reservation from the booking side. Paired with the admin version, it gives you a full picture of who changes what.
New or Updated Customer
Instant triggerIn Zapier“Triggers when a new customer has been added or when customer data has been updated.”
The only trigger about people rather than bookings. It starts when a customer is added to Planyo, and again whenever their data is updated.
Planyo Online Booking actions
Planyo Online Booking gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
New Customer
ActionIn Zapier“Adds a new user (customer) to your planyo site.”
Adds a customer to your Planyo site with first name, last name and email address, the three required fields.
Create Vacation
ActionIn Zapier“Adds a new vacation (period of unavailability) for given resource or entire planyo site.”
Blocks a period in Planyo, either on one resource or on the whole site, between a start and an end date and time. In Planyo, a vacation means unavailable.
Create Reservation
ActionIn Zapier“Enters a new reservation into the system.”
Enters a booking in Planyo from another tool. It asks for the resource ID, start and end, quantity, and the customer's name and email, all required.
When a Planyo Zap breaks
Zapier lists no help article or rate limit specific to Planyo. What breaks is the general stuff, and it bites booking systems hard.
Four cases to check before you publish. If one of them already hit you, the Zapier troubleshooting page is the next stop.
Past bookings are never picked up
A Zap only reacts to what happens after it is switched on. Reservations made before that stay out; moving them is a separate job.A Zap that books itself in a loop
New Reservation followed by Create Reservation on the same site fires again on its own booking, over and over, and burns your tasks.Bulk imports get held back
After a migration or a mass import, a sudden pile of events can be held back by Zapier's flood protection instead of running at once.The second action is refused
On the free plan, a Zap stops at one trigger and one action. A second action or a filter needs a paid plan.
Need help automating Planyo Online Booking with Zapier?
A person reads every message.



