TripWorks gives Zapier a set of instant triggers — events that start a Zap the moment they happen in your account. This article lists every trigger, explains what data each one sends, and points out the fields worth mapping into your other apps.
In this article
New to Zapier? Start with Set up your Zapier integration to connect the two accounts first.
Available triggers
You'll pick one of these 13 triggers when you create a Zap. Each is instant, so it fires within seconds of the event — no polling or delay.
| Trigger | Fires when |
|---|---|
| New Customer Lead | A new customer with an email address is added |
| Customer Updated | An existing customer's details change |
| Payment Created | A payment (or refund) is processed |
| Payout Created | A payout is sent to your bank account |
| Trip Created | A new trip is created — including drafts and abandoned carts |
| Trip Reserved | A trip moves to Reserved (usually the first payment) |
| Trip Updated | An existing trip changes — see the note below |
| Trip Cancelled | An activity (trip order) in a trip is cancelled |
| Booking Updated | One guest's booking changes |
| Add-On Updated | An add-on is added to, changed on, or removed from a booking |
| Note Created | A reservation note is added to a trip |
| Note Updated | A reservation note is edited |
| Waiver Signed | A guest signs a waiver |
Trip Updated covers changes to an existing trip that don't have their own trigger, such as reschedules, guest-count and custom-field edits, and resource changes. Cancelling an activity fires Trip Cancelled instead of Trip Updated, and booking, add-on, and note changes each have their own trigger. To act on one case only, add a Filter step in your Zap on the field that matters.
The data each trigger sends
When a trigger fires, Zapier receives a structured record you can map field-by-field into your action app. The available fields depend on the trigger:
- Customer triggers send the customer's name, email, phone, location, VIP and opt-in flags, and their confirmation code.
- Payment / Payout triggers send the amount, type, direction (payment vs. refund), status, and the linked trip.
- Trip triggers (Trip Created, Reserved, Updated, and Cancelled) send the whole reservation — the trip's totals and status, the customer, and each activity (trip order) with its guests (bookings), ticket types, add-ons, custom fields, and time slots.
- Booking Updated sends the one guest's booking — its status, the customer, ticket type, resources, waiver, custom fields, and products — along with the activity and trip it belongs to.
- Add-On Updated sends the booking the add-on belongs to, the activity's add-ons with their names and prices, and the trip.
- Note triggers send the note's text, when it was written, and the trip it is on.
- Waiver Signed sends the signer's details, the waiver type, the activity, and a link to the signed PDF.
A representative set of fields from a customer or trip event:
| Field | Example |
|---|---|
| Full Name | Jordan Avery |
| jordan@example.com | |
| Phone | +1 555-0100 |
| Customer is VIP | false |
| Customer is Opt In | true |
| Confirmation Code | BOOK-1234 |
| Trip Order Experience Name | Sunset Kayak Tour |
| Trip Method Name | Online |
| Trip Order Status | Booked |
| Ticket Type | Adult |
| Waiver Type Name | Liability Waiver |
| Custom Field Internal Name | Fishing License |
Money values are whole numbers in the smallest unit of your account's currency, such as cents for US dollars or pence for pounds. A total of 24200 is 242.00 in a currency with two decimal places. Convert amounts to your own currency in your Zap before you write them to a spreadsheet or invoice.
Customer portal links
Trip triggers include a customer portal URL — a direct, login-free link to a reservation in TripWorks — at three levels, so you can send guests exactly the right link:
| Link | Points to | Good for |
|---|---|---|
| Trip portal URL | The whole reservation — every activity and guest | A booking-confirmation email or SMS |
| Trip order portal URL | One activity within the reservation | Reminders for a specific tour when a booking has several |
| Booking portal URL | One individual guest's booking | Per-guest waiver links or check-in messages |
A popular setup: map the trip portal URL from the Trip Reserved trigger into a Twilio SMS or a Gmail step, so every guest automatically gets a link to manage their reservation right after they book.
Want the raw payload?
This article describes the data as friendly fields for no-code Zaps. If you're a developer who wants the exact JSON — field names, nesting, and types — the webhooks integration fires on the same events and documents the full payload for each one.
Try these
- Alert your team when an activity is cancelled — use Trip Cancelled and send a Slack message with the confirmation code and activity name.
- Tell a guest about their add-on — use Add-On Updated to send an SMS or email when an add-on is added to their booking.
- Share notes with your crew — use Note Created to post each new reservation note to a team channel.
Frequently asked questions
What's the difference between Trip Updated, Booking Updated, and Add-On Updated?
Trip Updated sends the whole reservation when the trip changes in a way that doesn't have its own trigger. Booking Updated sends one guest's booking when it changes. Add-On Updated sends the booking when an add-on is added, changed, or removed. Pick the narrowest trigger that matches what you want to react to, so your Zap runs only when it should.
How do I run a Zap when an activity is cancelled?
Use the Trip Cancelled trigger. It fires when an activity in a trip is cancelled and sends the whole reservation. A cancellation doesn't also fire Trip Updated, and the trip's own status doesn't change, so don't filter Trip Updated on status to look for cancellations.
Why didn't Booking Updated run when a guest signed their waiver?
When the only change to a booking is the waiver becoming signed, TripWorks fires Waiver Signed instead of Booking Updated. Use Waiver Signed for waiver automations.
Why didn't a new customer trigger my Zap?
The New Customer Lead and Customer Updated triggers only fire for customers that have an email address. A customer added without an email won't start the Zap.
Can I use these triggers to send data back into TripWorks?
No — these are triggers only. TripWorks starts your Zap; the action happens in your other app. TripWorks can't be used as a Zapier action, so Zapier won't create or edit records inside TripWorks.
Related
Built for attractions, tours & activities
Automate the work after the booking
See how attractions, tours, and activities turn every booking, payment, and waiver into an automatic workflow with TripWorks and Zapier. Book a demo and make the switch.