Zapier Tables for mapping data

You may need to maintain data mappings to utilise the power of TripMapper and Zapier fully. In this guide, we'll step through the different areas we've established as good candidates for Zapier Tables.

Card Types

TripMapper maintains its own list of Card Types and Subtypes to express the nature of the card and enable additional functionality. However, the items in whatever platform you're connecting to may not always align exactly with our workflow. To avoid this, we recommend setting up a Zapier Table with mappings so that you can send and receive data on your terms.

Card Types

Our card types are defined as follows:

• ACCOMMODATION

• ACTIVITY

• FOOD

• OTHER

• TRAVEL

We then have subtypes that belong to some of those types. They are:

• ACCOMMODATION

  • ACCOMMODATION_ALL_INCLUSIVE

  • ACCOMMODATION_BED_AND_BREAKFAST

  • ACCOMMODATION_BED_ONLY

  • ACCOMMODATION_FULL_BOARD

  • ACCOMMODATION_HALF_BOARD

• TRAVEL

  • TRAVEL_BOAT

  • TRAVEL_BUS

  • TRAVEL_COACH

  • TRAVEL_CYCLE

  • TRAVEL_DRIVE

  • TRAVEL_FLIGHT

  • TRAVEL_MOTORCYCLE

  • TRAVEL_PRIVATE_TRANSFER

  • TRAVEL_SCOOTER

  • TRAVEL_SHARED_TRANSFER

  • TRAVEL_TAXI

  • TRAVEL_TRAIN

  • TRAVEL_TRAM

  • TRAVEL_TUBE

  • TRAVEL_WALK

For the purposes of this example, let's say you plan to create trips in your CRM and have them sync to TripMapper. To do this, we'd define the different types you want to map in the 'Key' column of the Zapier table, and then the corresponding TripMapper types in the second column.

Countries

For consistency and predictability, we send and require country information on a Trip to be formatted as the two-character ISO code for the country. For example, the United Kingdom is GB, Spain is ES, Australia is AU etc. You can find a full list of these ISO codes here.