Reservanto
SchedulingConnect AI agents to Reservanto, a Czech online booking system for appointments, classes, and courses. Agents check available start times, create and confirm bookings, and manage customers so reservations stay accurate across locations.
What This Integration Enables
Reservanto is a Czech booking platform for appointments, classes, and courses, and it is built around a permission model rather than around an endpoint list. Every operation in this connector names the right it requires. Reading customers needs Customer_r, writing them needs Customer_w, reading availability needs FreeSpace_r, touching bookings needs Booking_w, and pulling the day's reservations needs Event_r. The merchant grants those rights once, during the authorization redirect that produces the Long Time Token. What an agent can do is therefore decided by a human before the agent ever runs, at the account level, in a form the merchant can inspect. Authentication itself follows the same shape: the token you configure is exchanged internally for a short lived credential valid for thirty minutes, so nothing long lived travels on individual calls.
On top of that model sits a full multi-location booking system. Agents read the catalog through List Locations, List Resources, and List Services, where a resource is a staff member, a room, or a piece of equipment with its own capacity and linked services. They find people through Search Customers and List Customers, create and correct them with Create Customer and Edit Customer, and load credit, loyalty points, purchased passes, and price level through Get Customer Details. They find real open times with Get Available Starts, commit them with Create Booking, move pending reservations forward with Confirm Booking, and report on the whole business through Get Bookings For Period. Agents run all of that inside the rights the merchant granted. Cancellations that would override a policy the merchant wrote go to a person first, which is the human-in-the-loop default FlowRunner builds around. Every operation is built and verified against the Reservanto API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A Web Request Becomes a Confirmed Appointment
A request comes in from a form built in Typeform naming a service, a branch, and a preferred week. The agent runs List Services to resolve the service and its duration, then List Resources filtered to that location to find the staff who actually provide it. Get Available Starts returns the open start times as Unix timestamps for the requested interval. The agent picks the earliest one that fits the customer's stated window, runs Search Customers to avoid creating a duplicate, and commits with Create Booking. Because the connection holds the notification right, Reservanto sends the confirmation by email or SMS itself, in the customer's language, without FlowRunner composing anything.
Clearing the Pending Queue Every Morning
Bookings that need approval sit waiting, and every hour they sit is an hour the slot is neither used nor released. Each morning the agent runs Get Bookings For Period across the next fourteen days and separates the reservations still awaiting confirmation. For each one it loads Get Customer Details to see credit, loyalty standing, and purchased passes, then applies the branch's own rules: an existing customer with a valid pass gets Confirm Booking straight away. Anything ambiguous, such as a first-time customer requesting a high-value service, is posted to the branch manager in Slack with the customer's history attached. The queue clears itself, and the manager only sees the cases that needed a person.
Keeping the CRM and the Book in Step
Reservanto has no triggers, so the sync runs on a schedule instead of on an event. Each night the agent pulls Get Bookings For Period for the following day and List Customers filtered by last modification date to catch anything edited since the last run. Bookings, prices, payment state, and resource assignments are written to HubSpot against the matching contact, and a daily branch summary lands in Google Sheets for the operations review. Records whose email or phone failed Reservanto's own validation on the last write are collected as automation exceptions rather than retried, because a bad phone number on a customer who expects an SMS reminder is a problem a person needs to fix.
Human-in-Loop Highlight
Cancel Booking carries two options that make it more than a schedule change. The first overrides the late cancellation window, which is a rule the merchant set deliberately, usually because late cancellations cost the business a slot it cannot refill and a staff member who already came in. An agent that overrides it is not adjusting a calendar, it is waiving a commercial policy on the merchant's behalf. The second cancels the whole course together, so a request about one Thursday session can remove every remaining session the customer paid for. There is a third wrinkle underneath both: whether the customer is told at all depends on the CustomerNotifications right granted during authorization, which is not visible in the call itself. So the agent stops. It posts to the branch manager: "Cancellation requested for [name], pilates course, session 3 of 10, starts in four hours. This is inside the late cancellation window. Cancel this session only, cancel the remaining course, or hold and ask the customer to move it?" Reads, availability checks, customer records, and Confirm Booking on approved requests run without anyone being asked. Waiving the merchant's own policy, or ending a course somebody paid for in full, does not.
Agent Capabilities
15 actionsMerchant and Catalog
4- Get Merchant Info Returns basic information about the connected merchant, including name, contact details, mailing and invoice addresses, VAT status, and company identifiers. Requires the Merchant_r right, and doubles as a connection check.
- List Locations Lists all business locations of the connected merchant, including address, contact details, and working hours. Requires the Location_r right. The public-only filter returns just the branches customers can see.
- List Resources Lists all booking resources, meaning staff members, rooms, and equipment, with capacity, linked services, and location. Requires the BookingResource_r right and can be filtered to a single location.
- List Services Lists all bookable services with duration, price, VAT rate, category, linked resources, and available price levels. Requires the BookingService_r right. The modified-since filter makes catalog sync cheap to run often.
Customers
5- Create Customer Creates a new customer record, with the email and phone validated by Reservanto before the record is accepted. Requires the Customer_w right and returns the internal customer ID that booking operations need.
- Edit Customer Updates an existing customer by internal ID, changing only the fields supplied. Requires the Customer_w right, and the email and phone are validated the same way as on creation.
- Get Customer Details Returns detailed information for a single customer, including current credit, loyalty points, purchased passes, notes, and price level. Requires the Customer_r right. This is the lookup that gives a booking decision its context.
- Search Customers Searches customers by name, email, or phone text and returns up to fifteen matching records. Requires the Customer_r right and at least one search term. Run it before Create Customer to avoid splitting one person into two records.
- List Customers Lists the merchant's customers, optionally filtered by registration date or last modification date. Requires the Customer_r right. The modification filter is what makes a nightly CRM sync incremental rather than a full reload.
Availability and Bookings
6- Get Available Starts Returns the currently available appointment start times as Unix timestamps for a given service and resource within an interval. Requires the FreeSpace_r right, and its output feeds directly into Create Booking.
- Create Booking Creates a one to one reservation for a customer with the chosen service and resource at a specific start time. Requires the Booking_w right. When the connection also holds the notification right, Reservanto emails or texts the customer itself.
- Confirm Booking Confirms a reservation that is waiting for approval. Requires the Booking_w right. This is the action that clears a pending queue, and it is safe for agents to run against requests that match the branch's own rules.
- Cancel Booking Cancels an existing reservation, with options to override the late cancellation window and to cancel a whole course together. Requires the Booking_w right. Because both options waive or widen a merchant policy, this is routed for confirmation.
- Get Bookings For Customer Returns all bookings for a specific customer within a date range, including service, resource, price, payment info, and appointment details. Requires the Event_r right. The right lookup before answering any question about one person's history.
- Get Bookings For Period Returns all bookings across the merchant within a time interval, including service, resource, price, payment info, and appointment details. Requires the Event_r right, and it is the basis for calendar sync and daily reporting.
Frequently Asked Questions
What can FlowRunner do with Reservanto?
FlowRunner agents can run Get Merchant Info, List Locations, and List Resources in Reservanto, plus 12 more actions.
Does connecting Reservanto to FlowRunner require OAuth?
No. Reservanto connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Reservanto trigger a FlowRunner workflow automatically?
Reservanto doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Reservanto
$100 in credits. No card required. Connect in minutes.