All Collections
Integrations
Booking Platforms
How to set up the Airship connector in LiveRES
How to set up the Airship connector in LiveRES

How to automatically send data from LiveRES to your Airship database.

Oskar Smith avatar
Written by Oskar Smith
Updated over a week ago

Switching on the LiveRES / Airship connector means that each time a customer makes a booking, the customer and booking data will be automatically sent to your Airship database.

Getting started

To get started, provide confirmation in writing to your LiveRES Account Manager that your data can be shared with Airship.
​ 
Once permission has been given, Airship will send API access details to your LiveRES Account Manager. Zonal will configure your account to send data to Airship.Your LiveRes Account Manager will inform you of any specific prerequisites before the Airship connector can be enabled for your account.
​ 
Data will be sent from LiveRES in near real-time.

What data is sent?

  • Contact data - Title

  • Contact data - First name

  • Contact data - Last name

  • Contact data - Mobile number

  • Contact data - Email address

  • Contact data - Email opt in

  • Booking data - Unit

  • Booking data - Type

  • Booking data - Enquiry Date

  • Booking data - Party Date

  • Booking data - Covers

  • Booking data - Status

  • Booking data - Notes

View your data in Airship

Once the connector is enabled, you will be able to see data flowing into your Airship account, by navigating to Folders & Groups.
​ 
To access your Contact Folders in Airship, scroll down to “Contacts” in the main menu and select “Folders & Groups”.

You’ll be able to select your Booking/LiveRES Group to see contacts within that Group that have been added via the LiveRES connector.
​ 
To view the booking data, open a contact record and click “View booking data”. This screen will show the booking record details for the customer.

Notes

Note that cancellations will be passed through to Airship, but only those made via the LiveRES reservations widget. Bookings cancelled via another source (Tables, API Integration, Auto cancel etc.) will not be passed through to Airship.

Did this answer your question?