--- title: "Planyo Integration" description: "Connect AI agents to Planyo, an online reservation and booking system. Agents make and modify reservations, check availability and pricing, and confirm, cancel, or check in bookings so reservation workflows run end to end." url: https://flowrunner.ai/integrations/planyo date_modified: 2026-08-12T15:40:33-07:00 --- # Planyo [Scheduling](https://flowrunner.ai/integrations/category/project-management-productivity) Connect AI agents to Planyo, an online reservation and booking system. Agents make and modify reservations, check availability and pricing, and confirm, cancel, or check in bookings so reservation workflows run end to end. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 14 actions · API key · available [Planyo website](https://planyo.com/) · [Platform Documentation](https://www.planyo.com/api.php) · Capability data verified 2026-08-10 1. A rental request arrives by email with dates, a resource, and a quantity 2. Get User loads the requester's profile, history, and preapproval status 3. Check Availability confirms the resource is free for that window at that quantity 4. Get Rental Price quotes the period against the site pricing rules 5. Make Reservation holds the resource and returns the reservation ID 6. The hold and the quote go back to the customer with pickup instructions 7. Staff decide the status transition when the requester has a prior no-show on file ## What This Integration Enables Planyo is a reservation system for rentals, and that makes it a different animal from an appointment book. A Planyo booking carries a quantity, a price calculated from site rules, a check in and a check out, and a customer who has a standing in the business. That standing is the part most scheduling APIs do not model at all. Agents read the catalog through List Resources and Get Resource, test a window with Check Availability, quote it with Get Rental Price, and commit it with Make Reservation. They reschedule through Modify Reservation, annotate the record with Set Reservation Notes, and pull the day's book with List Reservations for reporting. The operation that defines the connector is Perform Reservation Action. Planyo deliberately routes every status change through one lever rather than letting anyone edit a status field directly, which keeps the workflow rules intact. Confirming a booking, checking a customer in, checking them out, marking a no-show, and preapproving a customer all travel through that same call. Agents run the reads, the quotes, and the routine confirmations without supervision. The transitions that write a judgment about a person onto their profile go to a human first, which is the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) default FlowRunner builds around. Every operation here is built and verified against the Planyo REST API. ### Without FlowRunner **Availability checked by eye**: Staff scan a planner for conflicts across resources that are booked by quantity, not by single slot **Prices quoted from memory**: Seasonal rules and unit pricing get applied differently depending on who answers the phone **Customer standing lives in heads**: Whether a renter has skipped a booking before is remembered by whoever took the last call ### With FlowRunner **Availability answered from the record**: Check Availability returns the maximum quantity still free and the first conflicting time **Prices quoted from the rules**: Get Rental Price applies the site pricing configuration the same way to every quote **Standing attached to the profile**: Get User returns preapproval and reservation history, so the decision has evidence behind it ## Use Case Scenarios ### Inbound Request to Priced Hold A rental inquiry arrives in a shared mailbox. The agent parses the dates, the resource, and the quantity, then runs Check Availability rather than trusting the planner. Planyo answers with the maximum quantity still free and, when the answer is no, the first conflicting time and a readable reason. The agent then runs Get Rental Price so the quote reflects the configured seasonal and unit rules instead of a rate someone half remembers. If the window holds, Make Reservation places the hold and the reply goes back through [Gmail](https://flowrunner.ai/integrations/gmail-service) with the price, the dates, and the pickup instructions attached. The customer gets an answer in minutes with a number that will not be revised later. ### Turnaround Between Two Renters An equipment item is returned. The agent runs Perform Reservation Action to check the current customer out, then Set Reservation Notes to record the condition the item came back in, using the private admin note rather than the customer-facing one. It runs List Reservations for the same resource over the next 48 hours to find who is collecting it next. If the gap is too short for the inspection the business requires, the agent flags it to the depot lead in [Slack](https://flowrunner.ai/integrations/slack) with both reservation IDs and the turnaround window, rather than silently moving the second booking. Notes on the record mean the next person to touch the item is not starting from zero. ### Nightly Reconciliation of the Book Overnight the agent runs List Reservations for the following day with the detail level set to include pricing, then loads each customer with Get User. It writes the day's book to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with the resource, the quantity, the quoted price, and the customer's preapproval status in adjacent columns. Reservations belonging to customers with no preapproval and a prior no-show are grouped at the top of the sheet as [automation exceptions](https://flowrunner.ai/concepts/automation-exceptions) for the counter staff to review with morning coffee. The agent does not cancel, confirm, or flag any of them. It builds the picture and leaves the calls to the people who will face the customer. ## Human-in-Loop Highlight Perform Reservation Action looks like one action, and mechanically it is. But some of what it can do changes a schedule, and some of it writes a verdict about a named person onto their Planyo profile. Confirming a booking is the first kind. Marking a no-show is the second, and it typically carries the site's penalty rules with it. Preapproving a customer is the second kind pointed the other way, granting standing trust that the business will honor on future bookings, and the README documents a fraud marking option in the same lever. So the agent draws its line inside that action rather than around it. It confirms and it checks people in and out on its own. When the option it is about to pass renders a judgment on a customer, it stops and posts to the counter lead in Slack: "Reservation 41822, \[name\], boat 3, booked 09:00 and no contact by 11:30. Get User shows one prior no-show in April and no preapproval. Mark no-show and apply the penalty, extend the hold, or release the resource?" Delete Reservation sits behind the same gate for a related reason. Planyo will optionally delete the customer along with the reservation, and only when that customer has no other bookings, so a routine cleanup can quietly remove a person's entire record from the site. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 14 actions ### Reservations 7 - **Make Reservation** Creates a new reservation for a resource over a given time period. Requires the resource, start and end times, quantity, and the customer first name and email. Admin mode bypasses required reservation form fields, and customer notifications can be switched on or off per call. - **List Reservations** Lists reservations that begin within a given time period, optionally restricted to a single resource and sorted by a chosen field. The basis for daily books, utilization reports, and turnaround checks between renters. - **Get Reservation** Retrieves the full details of a single reservation, including resource, customer, dates, status, pricing, payments, and any custom reservation form values the customer submitted. The evidence step before proposing any change. - **Modify Reservation** Updates an existing reservation, changing the resource, the start and end times, or the quantity. Fields left empty keep their original value, so a single attribute can be corrected without disturbing the rest of the booking. - **Perform Reservation Action** Runs a workflow action on a reservation, such as confirming, canceling, checking a customer in or out, marking a no-show, or preapproving the customer. This is the correct way to change a reservation status rather than editing it directly. - **Set Reservation Notes** Sets the customer-facing notes and the private admin notes on a reservation. Passing the literal text "empty" erases existing notes, which makes it worth handling deliberately in any flow that writes here. - **Delete Reservation** Permanently deletes a reservation, and optionally the customer too when that customer has no other reservations, no Planyo login, and was not entered by an administrator. The operation cannot be undone, so it is routed for confirmation. ### Resources and Pricing 4 - **List Resources** Lists the bookable resources on the site with paging, filtered to published or reservable resources only, and to the resource types worth including such as base resources, bundles, and packages. - **Get Resource** Retrieves detailed settings for a single resource, including available quantity, confirmation mode, category, working hours, base time unit, unit pricing, and named units. - **Check Availability** Checks whether a resource is available for a given time period and quantity. Returns availability, the maximum quantity still free, the first conflicting time when unavailable, and a human-readable reason. - **Get Rental Price** Calculates the rental price for a resource over a time period and quantity using the site pricing rules. Run this before quoting so the number the customer sees is the number the system will charge. ### Customers 2 - **Get User** Retrieves a customer profile by user ID or email address, including custom user properties, reservation history, and preapproval or banned status. The lookup that gives a standing decision its evidence. - **List Users** Lists customers with paging, optionally filtered by first or last name, where the star character matches multiple values. Useful for finding an existing record before creating a duplicate through a booking. ### Account 1 - **Get Site Info** Retrieves configuration and metadata for a Planyo site, including its name, category, admin email, timezone, and default language. For metasite API keys, a specific site ID can be passed to target one location. ## Frequently Asked Questions ### What can FlowRunner do with Planyo? FlowRunner agents can run Make Reservation, List Reservations, and Get Reservation in Planyo, plus 11 more actions. ### Does connecting Planyo to FlowRunner require OAuth? No. Planyo connects to FlowRunner with an API key, no OAuth flow required. ### Can Planyo trigger a FlowRunner workflow automatically? Planyo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Planyo?** This integration exposes Planyo to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/planyo. Site index: https://flowrunner.ai/llms.txt