Connect Claude & ChatGPT to Yoplanning

22 tools for Yoplanning

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• create_customerChanges dataCreate a customer. Pass a new UUID as `id` plus first/last name, email, phone, address, language and note.
• create_orderChanges dataCreate an order (booking). Pass a new UUID as `id`, the `main_client`, `items`, `currency` and optional `note` and `booking_status`.
• create_unavailabilityChanges dataBlock time for a staff member. Pass a new UUID as `id`, `teacher_id`, `start_date`, `end_date` and optional `reason`.
• get_customerGet one customer by `customer_id`.
• get_orderGet one order by `order_id`, with items, customer and payment status.
• get_productGet one product by `product_id`, with price, duration and descriptions.
• get_sessionGet one session (a scheduled activity slot) by `session_id`, with staff, clients and times.
• get_teamGet your Yoplanning team's details.
• list_membersList your team members (staff).
• list_online_productsList the products sold online through your booking engines.
• list_order_paymentsList payments recorded on one order by `order_id`.
• list_ordersList orders (bookings), filtered by creation date or last update range.
• list_paymentsList payments, filtered by `status`, `client_id`, `customer_order_id`, client name, amount or creation date.
• list_product_availabilitiesList upcoming available slots for one online product by `product_id`.
• list_productsList the activities/products your team offers.
• list_resourcesList resources (prices, rentals, options), searchable by `name_contains`, `label_contains` or price.
• list_staff_attendancesList staff assignments to sessions, filtered by `teacher_id`, teacher name, staff status or `start_date` range. Useful to see who works when.
• list_unavailabilitiesList staff unavailabilities, filtered by `staff` and start/end date ranges.
• search_customersSearch customers by `first_name`, `last_name`, `email`, `phone_number`, `city` or last update date. Use before creating to avoid duplicates.
• update_customerChanges dataUpdate a customer by `customer_id` (also pass the same value as `id`). Send the full customer record; fields left out may be cleared.
• update_orderChanges dataUpdate an order by `order_id` (also pass the same value as `id`), e.g. its items, note or booking status.
• update_sessionChanges dataUpdate a session by `session_id` (also pass it as `id`) with `start_date` and `end_date`, plus name, staff, clients, max participants or meeting point.

Questions