Resources · Zapier integration

FareHarbor Zapier integrationAutomate FareHarbor with Zapier.

The FareHarbor Zapier integration gives you 3 triggers, 0 actions and 0 searches. All three are instant: FareHarbor tells Zapier about a new, changed or cancelled booking, and your other tools react. Nothing ever flows back into FareHarbor.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the FareHarbor Zapier integration does for a tour desk

Connecting FareHarbor to Zapier means a booking event starts work in your other apps without anyone copying it over. Your Zap listens to FareHarbor for new, changed and cancelled reservations, then writes, sends or moves something elsewhere. FareHarbor only speaks here. It never listens.

Three results come up again and again. A team alert: New Booking pings the guides' channel as soon as a seat is sold. A cancellation log: Cancelled Booking adds a line to a sheet, so the month's lost bookings sit in one place. A single change feed: Updated Booking fires on creation, edits and cancellation alike, handy when one tool has to mirror everything. All three start the Zap the moment FareHarbor reports the event, even on the free plan, so the guide on the dock hears about a booking without waiting for any timer.

What Zapier does not do here: it cannot create, edit or look up a booking in FareHarbor. The app exposes no action and no search step, so FareHarbor is always the first card of the Zap, never a later one. Bookings made before the Zap goes live are not replayed either (more on that below).

The same app is also covered on the Make side: FareHarbor Make integration. To weigh the two platforms against each other, open Make vs Zapier.

Vocabulary

Zapier words in one minute

Eight words cover everything on this page. Each one comes back later without a second explanation.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Here it is always a FareHarbor booking that was created, changed or cancelled.
Action
The step that follows the booking event: a Slack post, a sheet row, a calendar entry, always in an app other than FareHarbor.
Task
What Zapier bills: one action that went through. On a FareHarbor Zap, every booking event costs as many tasks as it has successful actions.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A gate after the trigger: only bookings that match your rule, a given tour for instance, go any further; the rest stop there.
Connection
Your FareHarbor login handed to Zapier one time; every later FareHarbor trigger picks it from a list instead of asking again.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What it really costs in tasks

FareHarbor is not a premium app, so it runs on the free plan. The bill depends on what comes after it.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Cost of the trigger0 tasks
  • FareHarbor triggers3, all instant

The trigger never costs a task, and neither does Zapier waiting for the next booking. Only an action that goes through is counted: a Zap that posts to Slack and then adds a sheet row spends two tasks per booking. A failed action costs nothing. The free plan gives 100 tasks a month and builds two-step Zaps only. Add a filter or a second action and the Zap turns multi-step, which needs a paid plan. The interval grid concerns polling triggers; all three FareHarbor triggers are instant, so it never slows them.

Connect

Connect your FareHarbor account

  1. 01

    Open the Apps page

    In your Zapier account, open the Apps page, then click + Add connection. Have a FareHarbor account ready, plus access to any bookings the Zap should see that you do not own yourself.

  2. 02

    Pick FareHarbor

    Type FareHarbor in the search box of the dialog, select it, then click Add connection. A new tab opens where FareHarbor asks you to sign in with your account.

  3. 03

    Grant access

    Sign in, then allow Zapier to use the account. The connection now lives on the Apps page, and every Zap you build later reuses it without a new sign-in.

First Zap

Your first Zap: alert the guides on each new booking

GoalPost a Slack message for each new booking on one specific tour, so the guide on duty hears about it right away.

  1. 01

    Create the Zap

    In Zapier, start a new Zap. For the trigger, pick FareHarbor, choose the New Booking event and select the connection made above.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent bookings of the account, so you work on a real one. Spot the value that names the tour you care about.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then fill the three boxes: the field holding that tour value, a text rule, and the tour itself. A number rule would never pass on text.

  4. 04

    Add Slack

    Add the Slack action that sends a channel message, connect Slack, then map the booking details from the trigger into the message text.

  5. 05

    Test and publish

    Test each step and read what came back. When the message looks right, click Publish to switch the Zap on. The filter makes it multi-step, so this one needs a paid plan.

Triggers

FareHarbor triggers

3 events start a Zap when something happens in FareHarbor, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Cancelled Booking

Instant trigger

In Zapier“Triggers when a booking is cancelled.”

Starts the Zap whenever a reservation is cancelled in FareHarbor. The news reaches your other tools on its own, without anyone forwarding an email or updating a list by hand.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
freeing a resource elsewhere, such as removing a guest from a shared rental calendar or telling a partner hotel that the pickup is off.
Watch out
Updated Booking also fires on cancellations, so running both on the same bookings spends tasks twice for one event.
2

New Booking

Instant trigger

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

Fires once for each booking created in FareHarbor, which makes it the cleanest way to act on fresh sales only. Later edits to that booking are left to the other two triggers.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
announcing sales to the crew, adding the guest to a mailing list, or opening a prep task for the boat or the bikes.
Watch out
the Zap only sees bookings created after it is published, so last week's reservations stay where they are.
3

Updated Booking

Instant trigger

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

The widest of the three: it reacts when a booking is created, edited or cancelled. One Zap catches every movement in the reservation book, which suits a tool that has to mirror FareHarbor.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keeping a dispatch sheet in step with every change, rather than juggling three separate Zaps.
Watch out
creations and cancellations set it off too, so a Zap meant for edits alone still runs, and spends tasks, on every new and every cancelled booking.
When it breaks

When it breaks

Zapier attaches no help article to FareHarbor, and no limit specific to the app is published. What goes wrong comes from Zapier's general rules.

Four cases to keep in mind before you publish. None of them shows up as a red error, which is exactly why they catch people out. For problems beyond these, the team keeps a page on Zapier troubleshooting.

  • Last season stays in FareHarbor

    The Zap starts counting the day it goes live. Reservations taken before that never pass through it; bringing them over takes a separate import.

  • A wave of bookings held back

    A migration or a bulk import that creates a huge number of bookings in one go can trip Zapier's flood protection, which holds the batch instead of firing it all.

  • Two Zaps, one booking

    Updated Booking also fires on new and cancelled bookings. Pair it with New Booking or Cancelled Booking and the same event spends tasks in both Zaps.

  • Nothing writes back

    FareHarbor has no action on Zapier. A Zap can read its bookings but never change one, so any fix inside FareHarbor stays a manual step.
Need help

Need help automating FareHarbor with Zapier?

A person reads every message.

FAQ

Questions people ask before connecting FareHarbor

01Is the FareHarbor Zapier integration free?
Yes, the FareHarbor Zapier integration works on the free plan, because FareHarbor is not a premium app. That plan gives 100 tasks a month and builds Zaps of two steps: one FareHarbor trigger and one action in another app. The trigger itself costs nothing. The limit shows up as soon as you want more: a filter or a second action turns the Zap into a multi-step Zap, and that requires a paid plan. No price is quoted here, because plan grids change too often to stay accurate on a page.
02How many tasks does a FareHarbor Zap use?
One task per action that succeeds, for each booking event. The FareHarbor trigger is free, and so is Zapier waiting for the next booking. A Zap that posts one Slack message spends one task per booking; add a sheet row as a second action and it spends two. An action that fails is not counted. For a busy season, multiply the bookings you expect by the number of actions, then compare the result with the 100 tasks of the free plan or the allowance of a paid one.
03Does the FareHarbor trigger work in real time?
Yes, all three FareHarbor triggers are instant. FareHarbor tells Zapier the moment a booking is created, changed or cancelled, so the Zap starts straight away, whatever your plan. The interval grid, 15 minutes on Free down to 1 minute on Team and Enterprise, only concerns polling triggers, which Zapier checks on a timer. None of the FareHarbor triggers works that way. In the editor, a Zap built on an instant trigger shows a lightning bolt, a quick way to confirm it.
04What does it take to connect FareHarbor to Zapier?
A FareHarbor account, plus access to any bookings you do not own yourself but want the Zap to touch. On the Zapier side, open the Apps page, click + Add connection, search for FareHarbor and confirm with Add connection. A tab opens where you sign in to FareHarbor and grant Zapier access to the account. From then on the connection is reused by every Zap that needs FareHarbor, so there is nothing to repeat when you build the next one.
05Why can one booking start two Zaps?
Because Updated Booking is broader than its name suggests. It fires when a booking is created, edited or cancelled, so it overlaps with both New Booking and Cancelled Booking. If one Zap uses Updated Booking and another uses New Booking, a fresh reservation starts both, and each spends its own tasks. Pick one trigger per job: New Booking for fresh sales, Cancelled Booking for cancellations, Updated Booking only when a single Zap should mirror everything. A filter can narrow it further, on a paid plan.
06What if the FareHarbor operation you want is missing?
Then this integration cannot do it, and it is better to know before building anything. FareHarbor offers three triggers on Zapier and nothing else: no action, no search. A Zap can react to bookings but never create, edit or look one up inside FareHarbor. The workable route is to keep FareHarbor as the starting point and do the work in another app that Zapier can write to. Anything that has to change inside FareHarbor itself stays a manual step for the team.
07Zapier, Make or n8n for FareHarbor?
It depends on what the automation must do, not on a ranking. On Zapier, FareHarbor gives three instant triggers, runs on the free plan and needs no premium upgrade, which suits a team that wants alerts or logs running quickly. The limits are just as clear: two-step Zaps on the free plan, tasks billed per successful action, and no way to write into FareHarbor. If those limits fit the job, Zapier fits. If the job means changing bookings, check what each platform offers for FareHarbor before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations