Scheduling & Booking · Integration
YAROOMS
Add YAROOMS to your product for your customers, and give your AI agents governed access to it.
YAROOMS is workplace booking: meeting rooms, desks, parking spaces and the hybrid schedule saying who is in the office on which day. An embedded integration reads locations, floors and the resources on them, creates and cancels bookings, checks availability for a window, and registers users so somebody added in your product can book without a second account of their own. What makes it more than a shared calendar is occupancy. Unused bookings are released, a check in confirms somebody actually turned up, and the resulting numbers are how a workplace team decides how much space they need, which is usually the most valuable read to surface in a product built for facilities or people teams. Each customer's locations, working hours and booking policies are their own configuration rather than anything you can assume. fastn keeps the credentials 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 YAROOMS account so bookings your product makes appear on the floor plan their staff already use.
Create or cancel a room, desk or parking booking from your product, honouring that customer's own booking rules.
Check availability for a location and time window before your product offers anybody a slot.
Read occupancy and check in data so a workplace team can see which spaces are genuinely used.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds a room that fits a group at a given time and books it within scoped permissions.
An agent reports who is scheduled to be in the office this week and how much desk space that implies.
An agent cancels a booking it is permitted to touch, with the cancellation attributed.
Example prompt
Book a room for six people tomorrow afternoon at this location, and tell me what else is free.
Set up YAROOMS in 4 steps
- 01Enable the YAROOMS connector in your fastn dashboard.
- 02Have each customer authorise their own account so bookings are made under their credentials.
- 03Map that customer's locations, resource types, working hours and booking rules as configuration.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the YAROOMS integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a YAROOMS integration without building it. Your customers connect their own YAROOMS 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 YAROOMS update is not your on-call problem.
- One integration serves your product and your agents. The same governed YAROOMS 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
Envoy
Calendly
TimeTapOften used alongside
Tools the same teams tend to run next to YAROOMS, across other categories.
Slack
Microsoft Teams
Twilio
AircallYAROOMS integration FAQ
How do I add a YAROOMS integration to my product?
Enable the YAROOMS connector in your fastn dashboard, then let each customer authenticate their own YAROOMS account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no YAROOMS client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own YAROOMS account?
Yes. Every connection is scoped to the individual customer, so each authorises their own YAROOMS 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 YAROOMS 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 a room that fits a group at a given time and books it within scoped permissions.
Who maintains the YAROOMS integration?
fastn does. When YAROOMS 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 YAROOMS 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 YAROOMS?
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 YAROOMS integration?
A common starting point: let each customer connect their own YAROOMS account so bookings your product makes appear on the floor plan their staff already use. 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 YAROOMS integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding YAROOMS does not change your per-connector cost. You can start free with 3 connected accounts.
Add YAROOMS to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.