How to build an agent-ready automation stack for the future of travel

If you run a tour or activity business, it’s possible that your tools don't talk to each other. Booking engine, CRM, payment processor, email marketing - each works fine on its own, but nothing syncs automatically.

That's becoming a problem. AI agents are entering travel distribution. Soon, a traveler won't browse your website. They'll ask an AI assistant to find and book a tour directly. On the operator side, AI tools will handle inventory, follow-ups, and reporting. None of that works if your systems are disconnected.

Your booking engine is the closest thing you have to a single source of truth. It knows who your customers are, what they booked, what they paid, and what's available. But that data stays locked in one system. Your CRM and accounting tool don’t see it, and your marketing platform keeps emailing people who have already converted.

Make lets you fix that. Here’s how. 

Why "agent-ready" matters

AI travel assistants are starting to help travelers plan and book through conversation. When someone asks an AI agent to "find a sunset sailing tour in Santorini for four people next Thursday," that agent needs live availability, real pricing, and the ability to complete a booking programmatically.

Protocols like MCP (Model Context Protocol) are making this possible, giving AI agents standardized access to booking systems. But they only work when the data is accurate and current. If your CRM is out of sync with your booking engine, an AI agent gives wrong answers. If availability isn't real-time, it tries to book a full tour.

The automation stack you’ll build today is what makes your business readable to AI agents. 

Without it, you don't show up.

How it works: CaptainBook, Make & your CRM

CaptainBook recently joined Make as a technology partner. The native integration means you can set up triggers and actions inside Make without building custom API connections. Here's how to build a two-way CRM sync, the most common starting scenario.

Example: You run a dive school. CaptainBook handles bookings, and HubSpot handles customer relationships.

Step 1: Create a new scenario in Make

Open Make, click "Create a new scenario," and search for CaptainBook in the app directory. Select it as your trigger module.

Step 2: Set your trigger to a new booking

Choose "New Booking" as the trigger event. This fires every time a booking is confirmed in CaptainBook, sending structured data into Make:

• Customer name and email

• Activity type and date

• Amount paid

• Number of participants

Step 3: Search for the customer in your CRM

Add a CRM module (we'll use HubSpot as an example). Use "Search Contacts" with the customer's email as the lookup field. This tells you whether they're already in your system.

Step 4: Route - update or create

Add a Router with two paths:

• Path A: Customer exists - update their record with the new booking data

• Path B: New customer - create a contact and populate it with the booking details

Step 5: Tag and enroll in a follow-up sequence

After the contact is updated or created, tag them based on the activity type they booked and add them to the right email sequence. A customer who is a discovery diver gets a nudge toward certification. An advanced diver gets information about specialty courses.

Step 6 (optional): Reverse sync - CRM back to CaptainBook

Create a second scenario triggered by changes in the CRM. For example, when a contact is marked VIP or assigned a sales owner, push that tag back into CaptainBook. Next time the customer books, you already know who they are.

This same pattern works for other integrations - booking engine to accounting software, to team scheduling, to marketing platforms.

Getting started

You don't need to automate everything at once.

Start with one scenario. Pick the integration that saves you the most manual work today. For most operators, that's the booking-to-CRM sync. Set up the trigger, map the fields, test it with a few bookings, and refine.

Once that's running, add the next one. Payment events flowing to your accounting tool. Cancellations updating availability. New customers entering onboarding sequences.

Each scenario you add makes your business a bit more structured and considerably more ready for how travel distribution is going to work in the next few years.