Scheduling & Booking · Integration
TimeTap
Add TimeTap to your product for your customers, and give your AI agents governed access to it.
TimeTap is appointment scheduling for businesses that book people rather than rooms, so the record at the centre is an appointment holding a client, a member of staff, a location and a reason for the visit. An embedded TimeTap integration books, reschedules and cancels those appointments, reads the availability behind them so your product only ever offers a slot that genuinely exists, and keeps client records aligned with whatever your product already knows about the same person. Availability is the part worth respecting: it is assembled from a staff member's working hours, the location's opening times, the service duration and whatever is already booked, so computing it yourself from a calendar feed will eventually double book somebody. Each business configures its own locations, services and booking rules, and fastn holds their credentials per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each business connect their own TimeTap account so bookings your product creates land on the same calendar their front desk works from.
Read genuine availability for a staff member and service before offering a slot, rather than inferring it from a calendar.
Reschedule or cancel from inside your product when the thing that prompted the appointment changes.
Keep client records aligned so the person your product knows and the person on the booking are recognisably the same one.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the next slot that suits a client and the staff member qualified to take it.
An agent books or moves an appointment within scoped permissions, with the change attributed to the tenant that authorised it.
An agent reports which appointments were cancelled this week and how much time that freed up.
Example prompt
Find the next three openings for this service at our downtown location and tell me who is covering each.
Set up TimeTap in 4 steps
- 01Enable the TimeTap connector in your fastn dashboard.
- 02Have each business authorise their own TimeTap account so bookings run under their credentials.
- 03Map the location, staff, service and client fields your product uses, and decide how availability is read before a slot is offered.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the TimeTap integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a TimeTap integration without building it. Your customers connect their own TimeTap 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 TimeTap update is not your on-call problem.
- One integration serves your product and your agents. The same governed TimeTap 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
Appointlet
Chili PiperOften used alongside
Tools the same teams tend to run next to TimeTap, across other categories.
Slack
Microsoft Teams
Twilio
AircallTimeTap integration FAQ
How do I add a TimeTap integration to my product?
Enable the TimeTap connector in your fastn dashboard, then let each customer authenticate their own TimeTap account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no TimeTap client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own TimeTap account?
Yes. Every connection is scoped to the individual customer, so each authorises their own TimeTap 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 TimeTap 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 slot that suits a client and the staff member qualified to take it.
Who maintains the TimeTap integration?
fastn does. When TimeTap 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 TimeTap 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 TimeTap?
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 TimeTap integration?
A common starting point: let each business connect their own TimeTap account so bookings your product creates land on the same calendar their front desk works from. 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 TimeTap integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding TimeTap does not change your per-connector cost. You can start free with 3 connected accounts.
Add TimeTap to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.