Triggers and Actions

In Zapier, Triggers are events that start a workflow when something happens in one app, and Actions are the tasks that the workflow performs in response to the trigger in another app. Essentially, a trigger sets the automation in motion, and actions are the steps carried out as a result.

TripMapper Zapier Trigger Events

New Brand

When a new brand is created in TripMapper, this event will be triggered.

New Card

When a new card is created in TripMapper, this event will be triggered.

New Client

When a new client is created in TripMapper, this event will be triggered.

New Trip

When a new trip is created in TripMapper, this event will be triggered.

New User

When a new agent user (team member) is created in TripMapper, this event will be triggered.

Updated Card

When a card is updated in TripMapper, this event will be triggered. This currently only applies to cards updated on a trip. You will need to specify the Trip you want to listen to updates on in the Zap.

In an upcoming update, the requirement to specify a trip when checking for card updates will be removed, allowing you to receive a feed of all card changes across all of your organisation's trips.

Updated Trip

When a trip is updated in TripMapper, this event will be triggered.

TripMapper Zapier Action Events

Create or Update Card

This event will create or update a Card using data from previous Zap steps.

When creating a card, you must specify a name , day (i.e. the day of the trip the card is on), and type . You can read more about our types here. When updating a card, you must send the Card ID. It's common practice, when keeping two platforms in sync to store a unique reference, such as an ID.

When creating a card, this event also supports passing a Trip ID, which will create that card in the selected trip. If you don't send a Trip ID when creating the card, we will add the card to your card templates.

Create or Update Client

This event will create or update a Client using data from previous Zap steps.

When creating a client, you must specify if they are a person or an organisation in addition to a name. When updating a client, you must send the Client ID. It's common practice, when keeping two platforms in sync to store a unique reference, such as an ID.

Create or Update Trip

This event will create or update a Trip using data from previous Zap steps.

When creating a Trip, you must give the Trip a name, a country, a currency, a client id and an owner id. At the moment, we require countries to be sent as a list of two-character ISO codes. You can read more about that here. The currency is the billing currency for the trip. If you only price up trips in a single currency, you can manually type the Currency ISO (e.g. USD into the Zapier form).

If you're creating a trip for a client that has been created as part of the same Zap, ensure that step is before this one. That will mean you can access the client id that was created in the Zap flow.

Finally, the owner id is the ID of the TripMapper business user who should be marked as creating the trip. You can manually set this in the Zap if you plan to use the same person/user for this every time.

Find Client

The 'Find Client' action allows you to locate a client through one of the following methods:

  • Client ID

  • Client Name

  • Client Email

Note that ID and Email are the preferred methods as they represent unique values in the system, whereas name does not. In all cases, the search must find an exact match in order to successfully find the client. You also have the option to fail the zap run if no one is found.

Find Trip

The 'Find Trip' action allows you to locate a Trip by searching with a trip id. If the search is successful, you will be returned an object representing the trip with all the top-level data associated with it.

Anything Missing?

This is just the start of our integration with Zapier. We're already hard at work on a second phase, which includes far more financial information. That said, if you need something specific sooner rather than later, feel free to shoot us an email and let us know about your use case.

Was this helpful?