Resources · Make integration

FareHarbor Make integrationAutomate FareHarbor with Make.

Every booking in FareHarbor can set off work in your other tools. The FareHarbor Make integration gives you 3 instant triggers: new, updated and cancelled bookings. This guide is for tour and activity operators, and it walks you from connection to a first live scenario.

Try the FareHarbor integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the FareHarbor Make integration do for you?

The FareHarbor Make integration lets a booking event start an automation. Make calls that automation a scenario: a chain of modules, where each module is one brick, such as a trigger that listens to FareHarbor. On this app, all 3 modules are triggers, so FareHarbor starts the work and another app finishes it.

A welcome message on every sale. Watch New Booking hands Make each fresh reservation as a bundle, which is one item passed from module to module. From there, a module of your email or messaging app can greet the guest with the details they just booked.

A clean follow-up when someone drops out. Watch Cancelled Booking reacts only to cancellations. A guide roster, a spreadsheet of seats or a CRM record can be updated the moment a slot frees up, without anyone copying the change by hand.

One feed for every change. Watch Updated Booking fires on creation, on edits and on cancellation. It suits a log or a dashboard that must mirror FareHarbor as a whole, where splitting the three events would only add scenarios.

Know the limits before you start. FareHarbor has no action or search module in Make, and no Make an API Call module either: Make can listen to FareHarbor, it cannot write back to it. If you are weighing platforms, the n8n vs Make comparison lays out the criteria, and our Make review covers the editor itself. Teams who want the scenario built for them can talk to our Make agency.

Connect

How do you connect your FareHarbor account to Make?

  1. 01

    Open the connection window

    Add any FareHarbor trigger to your scenario and click Create a connection. A connection is your FareHarbor account linked to Make once, then reused by all three triggers, so this step happens a single time.

  2. 02

    Name it so you can find it later

    Giving the connection a name is optional, but it helps when you run several FareHarbor companies or test accounts. Something like the business name is enough to pick the right one from the list in future scenarios.

  3. 03

    Authorize Make and save

    Follow what the window asks for: either approve Make on the FareHarbor page that opens, or paste the key FareHarbor gives you. Then click Save, and the trigger is ready to be configured.

First scenario

Build your first scenario with FareHarbor

GoalWhen a guest books in FareHarbor, Make passes the booking to the tool your team already works in.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Nothing runs yet, the canvas simply waits for its trigger.

  2. 02

    Add Watch New Booking

    Search for FareHarbor, pick Watch New Booking and select the connection you made earlier, or click Create a connection if this is your first FareHarbor module.

  3. 03

    Send the booking somewhere useful

    Click the + on the right of the trigger and add a module from the app your team reads: email, chat or a spreadsheet. Map the booking data from the trigger into its fields.

  4. 04

    Test with Run once

    Click Run once, then create a test booking in FareHarbor. Read the bundles each module received and check that the right details landed in the second app.

  5. 05

    Switch it on

    Look at the clock on the first module, then flip the scenario on. Each booking now counts operations, one per module it runs through, which is what Make tallies on your plan.

Triggers

Which FareHarbor events can start a scenario?

3 modules start a scenario when something happens in FareHarbor. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by FareHarbor as soon as it happens.

FareHarbor1Watch Cancelled Booking

Watch Cancelled Booking

Instant trigger

In Make“Triggers when a booking is cancelled.”

This trigger gives you a scenario that runs only when a guest cancels, so the rest of your stack learns about the freed seat without anyone checking FareHarbor. It stays quiet on new bookings and edits.

How it fires
instant: FareHarbor calls Make through a webhook as soon as the cancellation happens, and the module carries a lightning badge.
When to use it
free up a guide. Or update the seat count in a shared sheet and send the guest a note offering another date.
Watch out
if a scenario based on Watch Updated Booking already handles cancellations, adding this one too means the same cancellation gets handled twice.
FareHarbor2Watch New Booking

Watch New Booking

Instant trigger

In Make“Triggers when a new booking is created.”

Pick this one when the scenario should start at the moment a reservation is made, and ignore everything that happens to it afterwards. It is the simplest entry point for a first FareHarbor scenario.

How it fires
instant: FareHarbor calls Make through a webhook as soon as the booking is created, with a lightning badge on the module.
When to use it
a confirmation email with extra practical information, a new row in a revenue sheet, or a heads-up in the team chat for a guide.
Watch out
edits and cancellations of that same booking never reach this scenario, so a spreadsheet fed only by it will drift from FareHarbor.
FareHarbor3Watch Updated Booking

Watch Updated Booking

Instant trigger

In Make“Triggers when a new booking is created, an existing booking is updated, or an existing booking is cancelled.”

With one module, you catch the whole life of a booking: its creation, every later change and its cancellation. That makes it the natural source for anything meant to stay in sync with FareHarbor.

How it fires
instant: FareHarbor calls Make through a webhook as soon as a booking is created, edited or cancelled, shown by the lightning badge.
When to use it
a booking log, a CRM record per guest, or a dashboard that must match the FareHarbor calendar.
Watch out
because three kinds of events arrive through the same door, switch to Watch New Booking or Watch Cancelled Booking when only one of them matters to the scenario.
Need help

Need help automating FareHarbor with Make?

A person reads every message.

FAQ

FareHarbor and Make: common questions

01Is the FareHarbor Make integration free?
Yes. FareHarbor is a standard app in Make, so it works from the Free plan. That plan has limits worth knowing: 2 active scenarios, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Scheduled runs cannot be closer than 15 minutes apart on Free, while paid plans go down to 1 minute and allow unlimited active scenarios. Usage is counted in operations, one per module per bundle, so a busy season means more operations. The page does not quote any price for FareHarbor itself or for Make.
02What do you need to connect FareHarbor to Make?
A FareHarbor account and a Make account. The official documentation gives no specific prerequisite and no dedicated connection steps, so the generic Make flow applies: add a FareHarbor trigger, click Create a connection, name the connection if you like, then either authorize Make on the FareHarbor page or paste the key FareHarbor provides, and click Save. The connection is reused by all three triggers. If the authorization is refused, the account owner on the FareHarbor side is the person to check access with.
03Do FareHarbor triggers in Make fire in real time?
Yes. All three FareHarbor triggers in Make are instant: FareHarbor calls Make through a webhook as soon as a booking is created, edited or cancelled, depending on the trigger you picked. In the editor you recognize them by the lightning badge on the module, as opposed to the clock badge of scheduled triggers that Make checks on the scenario's schedule. The scenario still has to be switched on to receive these calls, and Run once is the way to watch a single event pass through during a test.
04What if the FareHarbor module you need is missing in Make?
It depends on what you need. The FareHarbor app in Make only listens: 3 triggers, no action, no search, and no Make an API Call module to reach other parts of FareHarbor. So creating or editing a booking from a scenario is not possible with this app. The usual answer is to do the writing in another app, such as your CRM or spreadsheet, and keep FareHarbor as the source of events. For a need beyond that, the team behind this page can look at your case and suggest a route.
05Should you use Make or n8n for FareHarbor?
It depends on your criteria rather than on a winner. On Make, FareHarbor offers three instant triggers on every plan, including Free, and no module that writes back to FareHarbor. The same app often has an n8n node too, so check the n8n catalog for FareHarbor before deciding, and compare what each side can actually do with bookings. Then weigh where your other automations already live and who will maintain them. Neither tool is ranked here, and no cost or speed comparison is made between them.
Same platform

Other docs you might need on this stack.

Browse all integrations