Integrations
Connect TravelSpurt to the tools you already use. All of these are set up from Settings.
Connect Stripe
Stripe lets clients pay deposits and balances by card, with the money going straight to your own Stripe account. Setup takes about five minutes.
- Go to Settings → Payments and click Connect with Stripe.
- Sign in to your Stripe account, or create one, and approve the connection.
- You're sent back to Settings. When it says Connected — ready to take payments, you're done.
If it says charges aren't enabled yet, Stripe needs more information from you. Finish onboarding in Stripe, then click Refresh status.
Once connected, Open Stripe dashboard takes you to Stripe to see payouts and refunds. Disconnect stops new payment links from being created until you reconnect.
See Quotes, invoices & payments for what happens once Stripe is connected.
WeTravel via Zapier
If you sell seats on WeTravel, TravelSpurt can create the booking and travelers automatically each time someone books. WeTravel keeps handling the payments; TravelSpurt mirrors the booking and traveler details into your CRM and attaches your task checklist.
Set it up
- In TravelSpurt, go to Settings → WeTravel / Zapier and expand the card.
- Click Generate to create a webhook secret, and copy it. It's only shown in full once.
- In Zapier, create a Zap with the WeTravel trigger New Booking or New Participant/Traveler.
- Add the action Webhooks by Zapier → POST. Paste the Webhook URL from TravelSpurt:
https://app.travelspurt.org/api/webhooks/wetravel-zapier. - Add a header named
X-Webhook-Secret, with your secret as the value. - Map the WeTravel fields to the names below, then test and turn on the Zap.
- Optionally, set a Default tour type in TravelSpurt. It's used when WeTravel doesn't send a tour name, and decides which task checklist is attached.
| Field name | What to map |
|---|---|
booking_id | The WeTravel booking ID (required, used to match updates) |
tour_name / tour_type | The trip name |
departure_date | The trip start date |
amount_paid | The amount paid so far |
traveler_first_name, traveler_last_name | The traveler's name |
traveler_email, traveler_phone | The traveler's contact details |
is_lead_traveler | true for the lead booker |
wetravel_participant_id | The participant ID, used to match travelers |
What happens
- A new WeTravel booking creates a TravelSpurt booking in Enquiry. Later events for the same booking update it rather than creating a duplicate.
- Travelers are matched by participant ID, then by email. Details you've already entered are never overwritten; only blanks are filled in.
- The amount paid feeds the payment summary on each traveler's portal. Turn on Payments managed externally as well.
To pause the connection without losing your setup, turn off Connector enabled. If your secret leaks, click Regenerate and update the header in Zapier.
This integration is new. If a field doesn't come through as expected, tell us which WeTravel trigger you're using and we'll help you map it.
Connect an AI assistant (MCP)
TravelSpurt has an MCP server, so AI assistants that support MCP connectors, such as Claude, can look up your bookings when you ask. For example: "Which bookings are still at Quoted?".
- In your AI assistant, add a custom MCP connector with the URL
https://app.travelspurt.org/mcp. - When prompted, sign in to TravelSpurt and click Approve.
The connection is read-only. It can list your bookings, optionally filtered by status, and open a single booking's details. It can't change anything, and it only sees your own organisation's data.