--- title: "SimplyBook.me Integration" description: "Manage SimplyBook.me appointments from AI agents: create and cancel bookings, add clients, list services and providers, and call any admin method directly through the JSON-RPC escape hatch." url: https://flowrunner.ai/integrations/simplybook date_modified: 2026-08-04T10:04:16-07:00 --- # SimplyBook.me [Scheduling](https://flowrunner.ai/integrations/category/project-management-productivity) Manage SimplyBook.me appointments from AI agents: create and cancel bookings, add clients, list services and providers, and call any admin method directly through the JSON-RPC escape hatch. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 9 actions · Session · available [SimplyBook.me website](https://simplybook.me/) · [Platform Documentation](https://simplybook.me/en/api/developer-api) · Capability data verified 2026-08-12 1. A completed intake form arrives with a service request and preferred times 2. List Clients searches by email and phone to see whether this person already exists 3. Add Client registers the new client, or the existing client ID is reused 4. List Services and List Providers resolve the requested service and an available provider 5. List Bookings confirms the requested slot is genuinely open for that provider on that date 6. Create Booking schedules the appointment, and the confirmation posts to the staff channel 7. When the requested slot conflicts or the request is ambiguous, the front-desk lead picks the resolution the client actually gets offered ## What This Integration Enables Appointment businesses lose revenue in the gaps between systems: the lead that filled the form but never got booked, the reminder that never went out, the slot that sat empty because the cancellation was handled but never resold. SimplyBook.me holds the calendar; this connector closes the gaps around it. FlowRunner agents create and cancel bookings, register clients, browse services and providers, and, through the JSON-RPC escape hatch, reach any admin method the dedicated actions do not cover. The position: a booking system's job is to be full. Everything an agent can do here, instant booking from intake, systematic reminders, fast rebooking of freed slots, serves that single metric. - Book new and existing clients into services with a specific provider in one flow - Verify slot availability against real bookings before writing anything - Sync bookings, services, and providers into sheets, CRMs, and channels - Send per-client reminders built from the actual day sheet - Call any SimplyBook.me admin method directly when a workflow needs it ### Without FlowRunner **Booking requests idle in the inbox**: Form submissions and voicemails wait for the front desk to re-enter them, and slow response loses the appointment **Double entry, double error**: The client exists in the form tool, the CRM, and SimplyBook.me, with three spellings and two phone numbers **The day sheet is a morning ritual**: Someone assembles today's appointments and sends reminders by hand, when there is time ### With FlowRunner **Requests become bookings in one pass**: Intake flows register the client, resolve service and provider, verify the slot, and book, minutes after submission **One client record, reused**: Every booking flow searches before it creates, so the client list stays deduplicated by construction **The day runs on schedule flows**: Appointments log to the sheet, reminders go out per client, and staff see new bookings in the channel as they land ## Use Case Scenarios ### Form submission to confirmed appointment A prospect completes a [Typeform](https://flowrunner.ai/integrations/typeform) intake. The agent searches List Clients for a match, calls Add Client if none exists, resolves the requested service and provider, checks the slot against List Bookings, and books it with Create Booking. Staff see the new appointment in [Slack](https://flowrunner.ai/integrations/slack) with service, provider, and time. The client gets booked while their intent is hot, not after the front desk clears the queue. ### The morning that runs itself At 6 a.m., List Bookings pulls today's appointments across providers. The day sheet lands in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the front desk, and each client gets a reminder through [Gmail](https://flowrunner.ai/integrations/gmail-service) with their service, provider, and time. Get Booking Details enriches the reminders for appointments with special intake fields. No-shows drop for the oldest reason in the book: people got reminded. ### Cancellation to resold slot A client emails to cancel. The front-desk lead confirms, the agent cancels the booking, and then the interesting part happens: the flow immediately checks the waitlist kept in the CRM, finds the next client wanting that service and provider, and drafts the offer message with the newly freed slot. On the lead's approval, the offer goes out, and if accepted, Create Booking fills the gap the same day. A cancellation stops being lost revenue and becomes a routing event. ## Human-in-Loop Highlight Cancel Booking does two things at once: it marks a real client's appointment cancelled and frees the slot, and only one of those is recoverable. If an agent misreads an ambiguous email and cancels the wrong booking, the slot can be rebooked, but the client who arrives Thursday to a cancelled appointment cannot be un-disappointed, and in a service business that is the whole ballgame. So FlowRunner flows never cancel on inference: the agent locates the booking, pulls Get Booking Details, and presents client, service, provider, and time to the front-desk lead through a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step before the cancellation runs. Call RPC Method operates under a stricter version of the same policy, since an open door to every admin method is exactly as powerful as it sounds: named methods, reviewed parameters, no free-form agent improvisation against a live calendar. Bookings, syncs, and reminders flow autonomously. Taking an appointment away from a client requires a person who could pick up the phone if it goes wrong. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 9 actions ### Bookings 4 - **List Bookings** Retrieves bookings with filters for date range, service, provider, client, and confirmation status. Dates use YYYY-MM-DD, times HH:MM:SS. Returns booking summaries; the availability check behind every write. - **Get Booking Details** Retrieves a single booking's complete record by ID: client information, service, provider, date and time, status, price, and additional fields collected at booking time. - **Create Booking** Creates a new appointment for an existing client with a chosen service and provider at a specific date and time. End date and time default to the service duration. Takes IDs from List Services, List Providers, and List Clients. - **Cancel Booking** Cancels a booking by ID, freeing the slot and marking it cancelled. Returns true on success. The client-facing write this page's human gate governs. ### Catalog 2 - **List Services** Lists the services offered on the account with name, description, duration, and price, filterable to visible-only or searchable by name fragment. - **List Providers** Lists providers, the staff who perform services, with name, email, phone, and description, filterable to visible-only or searchable by name fragment. ### Clients 2 - **List Clients** Lists clients with contact details, searchable by name, email, or phone, with a result limit. The dedup search that runs before any client is created. - **Add Client** Creates a new client with a name plus email and, or phone depending on the account's client-field configuration, with optional address details. Returns the new client ID for booking. ### Advanced 1 - **Call RPC Method** Escape hatch that calls any SimplyBook.me JSON-RPC method directly: endpoint, method name, and an ordered parameter array per the API documentation, with authentication headers added automatically. For admin operations without a dedicated action, run under reviewed-payload policy. ## Frequently Asked Questions ### What can FlowRunner do with SimplyBook.me? FlowRunner agents can run List Bookings, Get Booking Details, and Create Booking in SimplyBook.me, plus 6 more actions. ### Does connecting SimplyBook.me to FlowRunner require OAuth? No. SimplyBook.me connects to FlowRunner with session-based authentication, no OAuth flow required. ### Can SimplyBook.me trigger a FlowRunner workflow automatically? SimplyBook.me doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at SimplyBook.me?** This integration exposes SimplyBook.me 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/simplybook. Site index: https://flowrunner.ai/llms.txt