Scheduling & Booking · Integration
TidyCal
Add TidyCal to your product for your customers, and give your AI agents governed access to it.
TidyCal is scheduling without the enterprise apparatus: a person defines booking types, each with its own duration, availability and questions, shares the link and takes appointments against their connected calendar. Some of those booking types are paid, which is the detail that changes an integration, because a paid booking only exists once the payment has gone through and treating an abandoned checkout as a confirmed appointment puts a slot on somebody's calendar that nobody bought. Beyond that the objects are the ones you would expect: booking types, the open slots computed from the underlying calendar, bookings with the answers the person gave, and the contacts behind them. Availability is derived from a live calendar rather than stored, so it is read at the moment of offering rather than cached. fastn keeps each account's key per tenant and maintains the connector.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own TidyCal account so appointments booked through your product land on their calendar.
Read the open slots for a booking type before offering a time, since availability comes from a calendar that keeps moving.
Create or cancel a booking from your product and carry across the answers the booker gave.
Handle paid booking types correctly, treating an appointment as confirmed only once its payment has completed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the next open slot on a booking type and books it, with the booking attributed to the agent.
An agent reports the week's bookings and which of them are still unpaid.
An agent cancels or moves an appointment on request and confirms what the booker was told.
Example prompt
What is booked in TidyCal for next week, and are there any paid sessions where the payment did not complete?
Set up TidyCal in 4 steps
- 01Enable the TidyCal connector in your fastn dashboard.
- 02Have each customer generate a key in their own TidyCal account and authorise it once.
- 03Choose the booking types your product works with and map the questions each one asks.
- 04Call it from your product and expose the same governed connection to your agents.
Why teams use the TidyCal integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a TidyCal integration without building it. Your customers connect their own TidyCal 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 TidyCal update is not your on-call problem.
- One integration serves your product and your agents. The same governed TidyCal 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
Cal.com
AppointletOften used alongside
Tools the same teams tend to run next to TidyCal, across other categories.
Slack
Microsoft Teams
Twilio
AircallTidyCal integration FAQ
How do I add a TidyCal integration to my product?
Enable the TidyCal connector in your fastn dashboard, then let each customer authenticate their own TidyCal account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no TidyCal client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own TidyCal account?
Yes. Every connection is scoped to the individual customer, so each authorises their own TidyCal 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 TidyCal 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 the next open slot on a booking type and books it, with the booking attributed to the agent.
Who maintains the TidyCal integration?
fastn does. When TidyCal 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 TidyCal 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 TidyCal?
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 TidyCal integration?
A common starting point: let each customer connect their own TidyCal account so appointments booked through your product land on their calendar. 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 TidyCal integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding TidyCal does not change your per-connector cost. You can start free with 3 connected accounts.
Add TidyCal to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.