Resources · Zapier integration

PEAK 15 Zapier integrationAutomate PEAK 15 with Zapier.

PEAK 15 Zapier integration: 3 triggers, 1 action, 1 search. PEAK 15 is a back office for small and mid-size tour operators. On Zapier, its three triggers watch marketing lists and fire instantly, even on the free plan, while the action and the search work on contacts.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PEAK 15 Zapier integration is for

The PEAK 15 Zapier integration connects the marketing lists and contacts of your tour operator back office to your other tools. A Zap (an automation built from one trigger and one or more actions) can start when someone joins or leaves a marketing list, or when a contact on a list changes, then update or look up a contact in PEAK 15.

A newsletter that follows your lists. Member Added to Marketing List can push each new member to the email tool your team sends brochures from, so the two lists stop drifting apart.

A clean opt-out. Member Removed From Marketing List pairs with Update Contact: when someone leaves a list, the Zap can tick Do Not Mail on that contact, and nobody has to remember it.

A synced contact sheet. Contact Updated on Marketing List can copy each change into the sheet or CRM your sales team reads, without manual re-typing. One edit in PEAK 15, one edit everywhere.

What Zapier does not do here: it cannot create a contact, a trip or an invoice in PEAK 15, and its triggers only see marketing lists, not bookings or billing. The single action edits an existing contact; the single search finds one. Everything else, trips and operations included, stays inside PEAK 15. To weigh Zapier against other platforms, see Make vs Zapier or n8n vs Zapier.

Vocabulary

Zapier words, explained once

Eight terms show up on every Zapier screen. Read them once and the rest of the page goes faster.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts a Zap, such as a member joining a PEAK 15 marketing list. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or moves something. Here, updating a PEAK 15 contact.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan counts those and nothing else.
Instant vs polling
An instant trigger is reported by the app when the event happens; a polling trigger is checked on a timer. All three PEAK 15 triggers are instant.
Filter
A step that lets the Zap continue only when the incoming data meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, so the next steps can use what it found. PEAK 15 offers Find Contact.
Connection
Your PEAK 15 account, linked to Zapier one time and then reused by every Zap step that touches PEAK 15.
Cost

What a PEAK 15 Zap costs in tasks

PEAK 15 is not reserved for paid plans: it runs on the free plan.

  • TriggerNever costs a task
  • Successful actionCounted against your plan
  • Failed actionNot counted
  • Free plan100 tasks a month, two-step Zaps

The trigger never costs a task, and Zapier waiting for new events is free as well. Each Update Contact that goes through is counted; one that fails is not. The free plan gives 100 tasks a month, but only two-step Zaps: one trigger, one action. Adding Find Contact, a filter or a second action makes the Zap multi-step, which needs a paid plan. The polling grid below is there for reference only: all three PEAK 15 triggers are instant.

Connect

Connect PEAK 15 in three steps

  1. 01

    Open Apps and add a connection

    In Zapier, open the Apps page and click + Add connection. A dialog with a search box appears. You need a PEAK 15 account first, plus access to any records you do not own but want the Zap to touch.

  2. 02

    Find PEAK 15 and sign in

    Search for PEAK 15, pick it and click Add connection. A new tab opens: sign in with the PEAK 15 account your Zaps should act as, ideally one that sees the marketing lists your team actually uses.

  3. 03

    Grant access

    PEAK 15 asks whether Zapier may use the account. Accept. The connection is then shared by every PEAK 15 step in every Zap, so you set it up once per account, not once per Zap.

First Zap

Your first Zap: mark leavers as Do Not Mail

GoalWhen someone is removed from a PEAK 15 marketing list, find the contact and tick Do Not Mail on it.

  1. 01

    Build: set the trigger

    Start a new Zap, pick PEAK 15 as the app and Member Removed From Marketing List as the event, then select your PEAK 15 connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so you see which values a real removal carries before mapping anything.

  3. 03

    Add Find Contact

    Add PEAK 15 with Find Contact and map the email, or the first and last names, from the test item. This search makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Update Contact

    Add PEAK 15 with Update Contact. Map the Contact ID returned by Find Contact, then set Do Not Mail. Leave the other fields alone unless you mean to change them.

  5. 05

    Test, then publish

    Test each step once and read what came back. When it looks right, click Publish to switch the Zap on. Removals made before that point are not processed.

Triggers

PEAK 15 triggers

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

1

Member Added to Marketing List

Instant trigger

In Zapier“Triggers when a Member is added to a Marketing List.”

Fires a Zap when a member joins one of your PEAK 15 marketing lists, which lets a new traveller land in your newsletter tool or your welcome sequence without an export.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your sales team adds past guests to an "autumn departures" list and the email platform should receive them too.
Watch out
the Zap only sees members added after you publish it; people already on the list stay where they are.
2

Member Removed From Marketing List

Instant trigger

In Zapier“Triggers when a Member is removed from a Marketing List.”

Here the event is a departure: a member taken off a marketing list starts the Zap, which is how an opt-out in PEAK 15 reaches the other tools that still hold that address.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a client asks to stop receiving offers, and the same person must disappear from your email tool as well.
Watch out
this trigger only reports the removal and changes nothing on the contact; to record Do Not Mail in PEAK 15, add Update Contact after it.
3

Contact Updated on Marketing List

Instant trigger

In Zapier“Triggers when a Contact on a Marketing List is updated.”

Any change to a contact who sits on a marketing list can open a Zap, so a corrected phone number or a new email reaches the other copies of that record.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the sheet your guides read must reflect contact details edited in PEAK 15.
Watch out
pairing it with Update Contact on the same contact makes the Zap write where its own trigger watches, and it can set itself off again and again.
Actions

PEAK 15 action

PEAK 15 gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Update Contact

Action

In Zapier“Update a Contact's details in Peak15.”

Edits the details of a contact that already exists in PEAK 15, including the Do Not Mail flag, using values carried by earlier steps.

When to use it
an unsubscribe recorded in your email tool or a form should switch the matching PEAK 15 contact to Do Not Mail.
Watch out
the Contact ID is required, and the action cannot create a contact, so put a step that supplies that ID before it.
Searches

PEAK 15 search

1 search step looks for data that already exists in PEAK 15, so a later step can use it.

A search step finds something that already exists so later steps can use it. In the editor, PEAK 15's search sits at the bottom of the Action event list, under the SEARCH heading.

1

Find Contact

Search

In Zapier“Finds a Contact based on their email, or first and last names.”

Looks up a PEAK 15 contact by email, or by first and last names, and hands what it found, the Contact ID included, to the next steps.

When to use it
just before Update Contact, to turn an email arriving from another app into the ID that action requires.
Watch out
searching by names can match more than one traveller; prefer the email whenever the earlier step carries it.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there, and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. PEAK 15 exposes no find-or-create variant for Find Contact, so on this app the search only finds.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a PEAK 15 Zap breaks

Zapier ties no help article to PEAK 15, so the cases below are the general limits that apply to any Zap built on it.

None of them shows as an error inside PEAK 15. You notice them as a contact that never changed, or a task count that climbs too fast. When you are stuck, the Zapier troubleshooting page is the next stop.

  • No catch-up on the past

    A Zap only reacts to what happens after you switch it on. List changes made before you publish never go through it; moving them is a separate job.

  • The update loop

    Contact Updated on Marketing List followed by Update Contact on the same person writes where the trigger watches. The Zap sets itself off again and burns tasks.

  • Flood protection after a bulk import

    Loading a large list in one go can make a trigger return a huge batch at once. Zapier may hold it back instead of running every member through the Zap.

  • A search that stops the Zap

    If Find Contact matches nobody and the setting stays on its default, the Zap stops there and Update Contact is skipped. Check the email you map.
Need help

Need help automating PEAK 15 with Zapier?

A person reads every message.

FAQ

PEAK 15 Zapier integration: questions people ask

01Is the PEAK 15 Zapier integration free?
Yes, within limits. PEAK 15 is not reserved for paid plans, so it works on the Zapier free plan. That plan gives 100 tasks a month and unlimited Zaps, but every Zap stops at two steps: one trigger, one action. Member Removed From Marketing List followed by Update Contact fits. Add Find Contact, a filter or a second action and the Zap becomes multi-step, which needs a paid plan. Prices move too often to quote here; the plans table on zapier.com has the current ones.
02How many tasks does a PEAK 15 Zap use?
Only completed actions are billed. A member joining or leaving a list costs nothing, nor does a contact change on a list, and Zapier waiting for those events is free too. Each Update Contact that goes through is counted; a failed one is not. With several actions, each successful one counts on its own, so three actions use three times what one does. Watch out for the update loop, which can spend the 100 tasks of the free plan quickly.
03Is PEAK 15 on Zapier real time?
Yes, for all three triggers. Member Added to Marketing List, Member Removed From Marketing List and Contact Updated on Marketing List are instant: PEAK 15 reports the event itself, so the Zap starts right away instead of waiting for a scheduled check. That holds on every plan, the free one included. Most Zapier triggers are polling ones, checked every 15 minutes on the free plan, so this is a real advantage. A lightning bolt in the editor confirms it.
04What does connecting PEAK 15 to Zapier require?
A PEAK 15 account, plus read or write access on any records you do not own yourself but want the Zap to touch. The steps run from the Apps page of Zapier: + Add connection, search PEAK 15, sign in on the tab that opens, then grant access. Think about the account you sign in with. Your Zaps act as that user, so it should see the marketing lists and contacts the automation is meant to handle.
05Why does Update Contact need a Contact ID?
Because it edits a contact that already exists, and the Contact ID is how PEAK 15 knows which one. The field is mandatory, and the action cannot create a missing contact. In practice, place Find Contact before it: the search takes an email, or first and last names, and returns the matching contact with its ID. Map that ID into Update Contact. If the search finds nobody and its setting stays on the default, the Zap stops before the update.
06What if the PEAK 15 operation you need is missing?
Then it is not in the catalog, and no setting will reveal it. Zapier offers five PEAK 15 operations: three marketing-list triggers, Update Contact and Find Contact. Nothing creates a contact, a trip or an invoice, and no trigger watches bookings. Two ways around it: do that part in PEAK 15 itself, or let a PEAK 15 trigger pass the data to another app that has the missing action. Recheck the PEAK 15 page on zapier.com before a new build, since catalogs change.
07Zapier, Make or n8n for PEAK 15?
Decide on criteria, not on a ranking. On Zapier the facts are simple: three instant marketing-list triggers that fire right away on every plan, one contact update, one contact search, and a free plan capped at two-step Zaps and 100 tasks a month. If your need fits one trigger and one action, Zapier handles it as is. If it needs Find Contact before the update, or several actions, you are on a paid plan anyway, which is the moment to compare what each platform offers for PEAK 15.
Same platform

Other docs you might need on this stack.

Browse all integrations