YouCanBookMe
SchedulingConnect AI agents to YouCanBookMe scheduling. Agents list and inspect bookings across your booking pages, create a booking on a customer's behalf, cancel bookings during rescheduling flows, and read profile and account settings for reporting.
What This Integration Enables
YouCanBookMe's model is deliberately small: an account owns booking pages, and booking pages receive bookings with the booker's form answers attached. That small model is what makes it a clean scheduling backend for agent workflows, because everything an agent needs lives in three objects. FlowRunner agents read the schedule across every booking page, carry booker form answers into the systems that need them, reserve slots on a customer's behalf, and handle cancellations inside governed rescheduling flows instead of ad hoc email threads. - Sync upcoming bookings into spreadsheets, CRM records, and calendars on a schedule - Post daily schedule summaries with booker context, not just names and times - Reserve slots programmatically during support calls or sales handoffs - Run rescheduling flows where the cancel step waits for the host - Audit booking pages and account settings across the whole account Scheduling is where automation meets a commitment culture: every booking is a promise two people made each other, which is why pure automation tools handle the happy path and quietly dump the exceptions back on humans. FlowRunner is built for the exceptions. The sick-day scramble, the double-booked slot, the customer who needs someone else to do the clicking, these are flows where the agent does the assembly and a [human-in-the-loop](/concepts/human-in-the-loop) gate holds the irreversible step. The result is scheduling that runs itself on normal days and degrades gracefully, with a person in command, on the abnormal ones.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The morning schedule that briefs the whole team
At 7am the agent calls List Bookings for the next 48 hours, pulls each booking's form answers with Get Booking, and posts the day to [Slack](/integrations/slack): who is coming, on which booking page, and what they said they want to discuss. The same pass appends rows to [Google Sheets](/integrations/google-sheets) for the bookings tracker. Hosts walk into their first call already knowing the booker asked about pricing migration, because the intake answer traveled instead of dying on the booking page.
Booking on the customer's behalf, mid-conversation
A support conversation ends with "can you just set that up for me?" The agent calls List Profiles to find the right consultation page, then Create Booking with the customer's details mapped to the profile's form field codes and a start time on an open slot. A [Zoom](/integrations/zoom) meeting gets created, the invite lands via [Gmail](/integrations/gmail), and the host's calendar blocks through [Google Calendar](/integrations/google-calendar). The customer never had to leave the conversation to click through a booking page.
Rescheduling around a sick day without the scramble
A host goes down for the day. The agent pulls the day's bookings with List Bookings, drafts the plan: three bookings to cancel and rebook next week, one to hand to a colleague's booking page. The operations lead reviews the plan, adjusts one, approves. Only then does Cancel Booking run on each approved appointment, with each booker notified per the page's settings, and Create Booking reserves the replacement slots. Every affected booker gets a resolution the same morning, and no appointment vanishes without a person having decided it should.
Human-in-Loop Highlight
Cancel Booking cannot be undone, and it does not just delete a row: it removes a reservation someone made in good faith and typically fires a cancellation notice straight to that booker. An agent that cancels the wrong appointment has broken a commitment in your name, and the slot it freed may be gone by the time anyone notices the mistake. So in every FlowRunner rescheduling flow, the agent assembles the case but never swings the axe alone: "Thursday 2pm with M. Okafor on the Strategy Call page, booked Monday, intake answers attached. Cancel and offer next Tuesday?" The host confirms, the cancellation runs, the rebooking follows in the same flow. Create Booking gets the same respect when the agent books on a customer's behalf, because a wrong slot claims real calendar time for two people. Reading schedules is the agent's job. Breaking or making commitments is a person's.
Agent Capabilities
7 actionsBookings
4- List Bookings Retrieves bookings across the account, optionally bounded by After and Before ISO 8601 timestamps. Returns scheduled times, the booker's submitted answers, and status. The read behind daily summaries, CRM sync, and rescheduling sweeps.
- Get Booking Retrieves one booking in full: scheduled time, the booking page it belongs to, the booker's form answers, and current status. The enrichment step before prep docs and follow-ups.
- Create Booking Creates a booking on a booking page at a specific start time, with answers keyed by the profile's form field codes. How agents reserve a slot on a customer's behalf, on an available slot only.
- Cancel Booking Cancels a booking by ID, removing the reservation and typically notifying the booker per the page's settings. Irreversible, and the operation this page's human gate exists for.
Profiles
2- List Profiles Lists all booking pages in the account with ID, title, and public URL. The discovery step for routing the right kind of meeting to the right page.
- Get Profile Retrieves one booking page's full configuration, including its title, public URL, and booking settings. Used to audit pages and to learn a page's form field codes before creating bookings against it.
Account
1- Get Account Retrieves account identifiers, the owner, plan information, and default settings. Used to confirm credentials and read account-level configuration in reporting flows.
Frequently Asked Questions
What can FlowRunner do with YouCanBookMe?
FlowRunner agents can run List Bookings, Get Booking, and Create Booking in YouCanBookMe, plus 4 more actions.
Does connecting YouCanBookMe to FlowRunner require OAuth?
No. YouCanBookMe connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can YouCanBookMe trigger a FlowRunner workflow automatically?
YouCanBookMe doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with YouCanBookMe
$100 in credits. No card required. Connect in minutes.