Scheduling & Booking · Integration
YouCanBook.me
Add YouCanBook.me to your product for your customers, and give your AI agents governed access to it.
YouCanBook.me sits on top of a calendar rather than replacing it. A customer connects their Google or Microsoft calendar, defines a booking page with the hours they will accept, the questions a booker must answer and the buffers between appointments, and availability is then computed from the real calendar instead of stored separately. An integration has to respect where that leaves it: free time is derived, so what you read is a current answer rather than a saved one, and a meeting created directly in the calendar immediately changes what the page will offer. An embedded integration reads booking pages and their settings, lists and reads bookings along with the answers a booker submitted, reschedules or cancels within the customer's own rules, and reacts when a booking is made or dropped. fastn keeps each account's authorisation per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own YouCanBook.me account so appointments land on the calendar they already keep.
Read live availability before your product suggests a time, since free slots are computed from the underlying calendar.
Read the answers a booker gave on the form so your product has the context before the meeting starts.
React when a booking is made, moved or cancelled, and drive the follow-up from your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds an open slot and books it on a customer's own page within scoped permissions.
An agent reports tomorrow's bookings together with what each person submitted on the form.
An agent reschedules or cancels a booking it is permitted to touch, with the change attributed.
Example prompt
What is booked for tomorrow, and what did each person say when they filled in the form?
Set up YouCanBook.me in 4 steps
- 01Enable the YouCanBook.me connector in your fastn dashboard.
- 02Have each customer authorise their own account, which carries the calendar their availability is derived from.
- 03Map their booking pages, the form questions you read, and the notice and buffer rules your product must honour.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the YouCanBook.me integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a YouCanBook.me integration without building it. Your customers connect their own YouCanBook.me account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a YouCanBook.me update is not your on-call problem.
- One integration serves your product and your agents. The same governed YouCanBook.me connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Compare with
Calendly
TimeTap
YAROOMSOften used alongside
Tools the same teams tend to run next to YouCanBook.me, across other categories.
Slack
Microsoft Teams
Twilio
AircallYouCanBook.me integration FAQ
How do I add a YouCanBook.me integration to my product?
Enable the YouCanBook.me connector in your fastn dashboard, then let each customer authenticate their own YouCanBook.me account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no YouCanBook.me client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own YouCanBook.me account?
Yes. Every connection is scoped to the individual customer, so each authorises their own YouCanBook.me account and only ever sees their own bookings, events and availability. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this YouCanBook.me integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent finds an open slot and books it on a customer's own page within scoped permissions.
Who maintains the YouCanBook.me integration?
fastn does. When YouCanBook.me changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create, reschedule or cancel bookings in YouCanBook.me automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in YouCanBook.me?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the YouCanBook.me integration?
A common starting point: let each customer connect their own YouCanBook.me account so appointments land on the calendar they already keep. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the YouCanBook.me integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding YouCanBook.me does not change your per-connector cost. You can start free with 3 connected accounts.
Add YouCanBook.me to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.