TripWorks integrates with Zapier using a set of “Instant” triggers that allow you to connect your TripWorks events (like new customers, payments, trips, and waivers) to thousands of third-party apps.
This guide provides a complete list of supported triggers and example data fields you can use in your automations.
Supported Trigger Events
These events run in real-time (“Instant”) and can be used as the starting point for a Zap:
Trigger Event |
Description |
|---|---|
| Customer Created | Fires when a new customer is added |
| Customer Updated | Fires when a customer record is modified |
| Payment Created | Fires when a payment is processed |
| Payout Created | Fires when a payout is initiated |
| Trip Created | Fires when a new trip is created |
| Trip Reserved | Fires when a new trip is reserved |
| Trip Updated | Fires when trip details are changed. Specifically triggered when:
|
| Waiver Signed | Fires when a waiver is signed |
Example Data Fields Sent with Triggers
When a trigger fires, Zapier receives a payload of structured data. Below is a representative table showing some of the available fields for a Customer Created event (though most fields are available across other events too, depending on context):
Field Name |
Example Value |
|---|---|
Full Name |
John Smith |
First Name |
John |
Last Name |
Smith |
Email |
john@email.com |
Phone |
+1 555 555 5555 |
Customer Country Name |
United States |
Customer is VIP |
false |
Custom is Opt In |
true |
Waiver Type Name |
Liability Waiver |
Waiver First/Last/Full Name |
Jenna Santos |
Trip Order Experience Name |
Fishing |
Trip Method Name |
Phone Inbound |
Trip Order Status |
Booked |
Booking Resource Name |
Boat A |
Booking Resource Duration |
120 |
Booking Resource Start/End Time |
2026-11-21T15:00:00Z |
Custom Field Internal Name |
Fishing License |
Custom Field Values |
false |
Customer Portal Url |
https://demo.tripworks.com/customerPortal/abc123/index |
Trip Order 1 Customer Portal Url |
https://demo.tripworks.com/customerPortal/abc123/index?to=456 |
Trip Order 1 Booking 1 Customer Portal Url |
https://demo.tripworks.com/customerPortal/abc123/index?b=789&to=456 |
Important Note
The data fields available will vary depending on the trigger type. For example, Waiver-related fields will only be included in waiver-related triggers.
Customer Portal URLs
Trip-related Zapier triggers include customer_portal_url fields at three levels. Each is a direct, login-free link to the TripWorks customer portal for that reservation.
Field |
Scope |
Available in |
|---|---|---|
Customer Portal Url |
Full reservation — all activities, all guests, totals, waiver status | Trip Created, Reserved, Updated, Cancelled |
Trip Order 1 Customer Portal Url |
A specific activity within the trip — useful when a reservation covers multiple activities | Trip Created, Reserved, Updated, Cancelled |
Trip Order 1 Booking 1 Customer Portal Url |
An individual guest's booking — useful for per-guest waiver links or check-in messages | Trip Created, Reserved, Updated, Cancelled, Booking Updated, Addon Updated |
A common use: map Customer Portal Url from the Trip Reserved trigger to a Twilio SMS step to automatically send customers a link to their reservation after booking.
Use Case Examples
- Send an SMS from Twilio when a new trip is reserved
- Add a row to Google Sheets when a payment is created
- Add a customer to your CRM when a customer is created
- Trigger a Slack message when a waiver is signed
- Send the customer portal link via email or SMS right after a reservation is confirmed