Scheduling & Booking · Integration
CampLife
Add CampLife to your product for your customers, and give your AI agents governed access to it.
Embed a CampLife integration so your customers can work their own reservations, bookings, and availability from inside your product instead of switching systems. Each customer connects their own CampLife account, and the fields and statuses their property uses are mapped per tenant as configuration rather than code. fastn handles per-customer authorisation and API upkeep, so onboarding another property is a mapping change rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own reservations and booking details into your product, mapped to their records.
Create and update bookings from inside your product so staff do not re-key details.
Read availability so your product does not act on a stale picture of what is open.
Trigger your product when a reservation is created, changed, or cancelled.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up a guest's reservation before answering an enquiry.
An agent updates or cancels a booking within governed permissions, with the action audited.
An agent reacts to a new reservation and starts the guest communication workflow.
Example prompt
List reservations arriving this weekend that still have an incomplete guest record.
Set up CampLife in 4 steps
- 01Open the CampLife connector from your fastn dashboard.
- 02Have each customer authenticate their own CampLife account with least-privilege credentials.
- 03Map the reservation fields and statuses your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the CampLife integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a CampLife integration without building it. Your customers connect their own CampLife 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 CampLife update is not your on-call problem.
- One integration serves your product and your agents. The same governed CampLife 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
Works well with
Stripe
HubSpot
SlackOften used alongside
Tools the same teams tend to run next to CampLife, across other categories.
Microsoft Teams
Twilio
Aircall
GongCampLife integration FAQ
How do I add a CampLife integration to my product?
Enable the CampLife connector in your fastn dashboard, then let each customer authenticate their own CampLife account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no CampLife client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own CampLife account?
Yes. Every connection is scoped to the individual customer, so each authorises their own CampLife 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 CampLife 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 looks up a guest's reservation before answering an enquiry.
Who maintains the CampLife integration?
fastn does. When CampLife 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 CampLife 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 CampLife?
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 CampLife integration?
A common starting point: read their own reservations and booking details into your product, mapped to their records. 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 CampLife integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding CampLife does not change your per-connector cost. You can start free with 3 connected accounts.
Add CampLife to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.