Scheduling & Booking
Connect Planyo Online Booking to Your AI Agents
Let your WKIL agents use verified Planyo Online Booking actions for controlled business workflows after the right authentication is configured.
Authentication: API key
What you can do
- Tool to create a new reservation
- Tool to add a new user in Planyo
- Tool to retrieve a list of add-ons
- Tool to retrieve a list of coupons
Available capabilities may vary by authentication and workspace configuration.
Actions supported by the connector
Add Reservation
Tool to create a new reservation.
Add User
Tool to add a new user in Planyo.
Get Add-on List
Tool to retrieve a list of add-ons.
Get Coupon List
Tool to retrieve a list of coupons.
Get Resource Availability
Tool to check resource availability within a specified date/time range.
Get Resource Blackouts
Tool to fetch blackout periods for a resource.
Get Resource Reviews
Tool to fetch reviews and ratings for a specific resource.
Practical agent use cases
- A WKIL agent can use Planyo Online Booking to support workflows involving planyo Online Booking is a reservation system for rentals, courses, tours, and appointments.
- A team can review Planyo Online Booking data or actions in WKIL before sensitive changes are made.
How it works with WKIL
- 1Choose the integrationAdd Planyo Online Booking to your agent from inside the WKIL platform.
- 2Grant the permissions it needsDefine precisely what the agent can access and perform.
- 3Test, then run itTest actions before they go live, with human approval where needed.
Permissions always stay in your control — you can scope access and require human approval before any sensitive action.
Related integrations
FAQ
What does the Planyo Online Booking integration support?
It exposes verified Planyo Online Booking actions that can support controlled workflows after authentication. Available actions depend on the connected account and permissions.
Does WKIL need access to a Planyo Online Booking account?
Yes. The integration requires the appropriate Planyo Online Booking authentication and should be scoped to the permissions your workflow needs.

