Please note that this is a WeTravel Pro feature.

Connect WeTravel to hundreds of other apps with Zapier

Zapier lets you connect WeTravel to 2,000+ other web services. Automated connections called Zaps, set up in minutes with no coding, can automate your day-to-day tasks and build workflows between apps that otherwise wouldn't be possible.

Each Zap has one app as the Trigger, where your information comes from and which causes one or more Actions in other apps, where your data gets sent automatically.

Getting Started with Zapier

Sign up for a free Zapier account, from there you can jump right in. To help you hit the ground running, here are some popular pre-made Zaps.

How do I connect WeTravel to Zapier?

1. Log in to your Zapier account or create a new account.

2. Navigate to "My Apps" from the top menu bar.

3. Now click on "Add connection" and search for "WeTravel"

4. Use your credentials to connect your WeTravel account to Zapier. You can find the Zapier API Key in your WeTravel profile page. Click on the "Generate API Key" button to get the Key and paste it into Zapier.

5. Once that's done you can start creating an automation! Use a pre-made Zap or create your own with the Zap Editor. Creating a Zap requires no coding knowledge and you'll be walked step-by-step through the setup.

6. Need inspiration? See everything that's possible with WeTravel and Zapier

If you have any additional questions, you can reach out to contact@zapier.com.

Available Triggers

New customer

This Zap is triggered each time you get a new booking. You can use the following data in your Zap:

Email

Full Name

Enrollment date - the date the first booking was made

Type - Buyer or Participant
Status - Going, Canceled or Waitlist

Trip Title

Date created - Date the first purchase was made

User ID

Trip UUID

New transaction

This Zap is triggered each time you get a new row in your transaction reporting. You can use the following data in your Zap:

uuid - transaction ID

amount - the gross amount of the transaction (with WeTravel's fees not withheld yet)

customer_facing_amount - total amount paid by participant (incl. card fees)

amount_refunded - amount refunded

amount_disputed - amount disputed

net_amount - the net amount of the transaction (with WeTravel's fees withheld already).

currency_object

currency - the currency used for the transaction

code - currency code

sign - currency sign

transaction_id - payout transaction ID from Stripe

bank_name

brand - card brand

last4 - last 4 digits of the card/bank account

beneficiary_name - beneficiary name of payout/vendor transfer

beneficiary_email - beneficiary email of payout/vendor transfer

payout_account_type - payout account type

humanized_status - status of transaction (successful/failed)

note - notes added for payouts/vendor transfers

description - description of payment

payment_method - card/bank/cash for payments

discount_code

trip

title - trip title

trip_id - trip ID of your choice

end_date - trip end date

start_date - trip start date

location - trip location

all_year - all year trip (yes/no)

uuid - trip ID WeTravel

participants

emails helen@wetravel.com

names

traveler

firstname

lastname

email

type - type of transaction: payment, refund, dispute, vendor payment, payout, wire, card, top-up, adjustment

payment_processing_fee - WeTravel payment processing fee

organizer_card_fee - debit/credit card fees paid by you, the travel organizer for this payment (populated if card fee is absorbed by you)

customer_card_fee - debit/credit card fees paid by the participant for this payment (populated if card fee is passed on to participants)

running_balance - running balance of your account after each specific transaction

created_at_formatted - the date the transaction was initiated on

updated_at_formatted - the date this transaction was last modified

transfer_creation_date_formatted - the date the transaction was initiated on in another format

Did this answer your question?