This article lists all fields that OnceHub makes available via Zapier. Any of these fields can be used to integrate with a third-party app.
Booking data
This section includes the data directly related to the booked appointment.
| Field | Description |
| Booking - Attachment | A link to the file attached by your Customer in the Booking form |
| Booking - Creation date | The time and date when the booking was created, e.g. Mon, Mar 23, 2015, 11:00 AM |
| Booking - Duration in minutes | The length of the meeting in minutes |
| Booking - Duration in seconds | The length of the meeting in seconds |
| Booking - Invoice line item* | Subject, Meeting time in Customer's time zone, Duration, Booking page Owner |
| Booking - Last updated | The last time any booking details were changed |
| Booking - Meeting time | The scheduled date and time of the meeting |
| Booking - Meeting time in Customer's time zone | The time the meeting will start in the Customer's time zone, e.g. Mon, Mar 23, 2015, 10:30 AM - 10:45 AM |
| Booking - Meeting time in UTC | Starting time in UTC time zone. e.g. Mon, Mar 23, 2015, 10:30 AM |
| Booking - Meeting time in Owner's time zone | The time the meeting will start in the Owner's time zone, e.g. Mon, Mar 23, 2015, 10:30 AM - 10:45 AM |
| Booking - Mode | The booking mode: Automatic booking or Booking with approval |
| Booking - Number of sessions scheduled | The number of sessions in a session package that were scheduled |
| Booking - Physical location | The address where the meeting will take place, as specified in the Conferencing / Location section of the Booking page |
| Booking - Starting time in Customer's time zone | The time the meeting will start in the Customer's time zone, e.g. Mon, Mar 23, 2015, 10:30 AM |
| Booking - Starting time in Owner's time zone | The time the meeting will start in the Owner's time zone, e.g. Mon, Mar 23, 2015, 10:30 AM |
| Booking - Status | The lifecycle phase or activity status of the booking |
| Booking - Subject | The subject of the meeting, as provided by Customer or Owner |
| Booking - Summary (long)* | Customer name, Company, Subject, Starting time, Duration, Location, Email, Phone, Mobile phone, Note |
| Booking - Summary (short)* | Customer name, Company, Location, Notes |
| Booking - Tracking ID | A unique ID automatically assigned to every OnceHub booking |
| Booking – Package ID | A unique ID automatically assigned to every OnceHub session package |
| Booking - Virtual location | The communication details required for connecting to the virtual meeting, as specified in the Conferencing / Location section of the Booking page. This could be a phone number, video conferencing information, a Skype ID, etc. |
| Booking - Virtual or physical location | The virtual or physical location of the meeting, as specified in the Conferencing / Location section of the Booking page |
| UTM source - Found in the Conversation lifecycle triggers | The source defined in the UTM parameter when the customer booked the meeting |
| UTM medium - Found in the Conversation lifecycle triggers | The medium defined in the UTM parameter when the customer booked the meeting |
| UTM campaign - Found in the Conversation lifecycle triggers | The campaign defined in the UTM parameter when the customer booked the meeting |
| UTM term - Found in the Conversation lifecycle triggers | The term defined in the UTM parameter when the customer booked the meeting |
| UTM content - Found in the Conversation lifecycle triggers | The content defined in the UTM parameter when the customer booked the meeting |
* Composite fields: These fields are considered Summary fields and contain a list of values from other fields separated by commas. These are best used for Description fields in 3rd party apps. Learn more about composite fields
Customer data
This section includes the data provided by the person who made the booking. You can search for a specific contact in Zapier by email.
| Field | Description |
| Customer - Company | The company name provided by the Customer in the Booking form |
| Customer - Country | The country selected by the Customer in the Booking form |
| Customer - Email | The email provided by the Customer in the Booking form |
| Customer - First name | The Customer’s first name, as extracted from the Name field provided by the Customer |
| Customer - Last name | The Customer’s last name, as extracted from the Name field provided by the Customer |
| Customer - Location | The country, US state, or Canadian province selected by the Customer in the Booking form |
| Customer - Mobile phone | The mobile phone number provided by the Customer in the Booking form |
| Customer - Name | The Customer’s full name, as provided by the Customer in the Booking form |
| Customer - Note | The note provided by the Customer in the Booking form |
| Customer - Phone | The phone number provided by the Customer in the Booking form |
| Customer - State | The state selected by the Customer in the Booking form |
| Customer - Time zone | The time zone selected by the Customer |
Cancel/reschedule data
This section includes the data related to cancellation and rescheduling activities.
| Field | Description |
| Cancel/reschedule - Initiated by customer name | The name of the Customer who performed the cancellation or reschedule action |
| Cancel/reschedule - Initiated by user name | The name of User who performed the cancellation or reschedule action |
| Cancel/reschedule - Reason | The reason given for canceling or rescheduling a meeting |
| Cancel/reschedule - Summary (long)* | Reschedule indication, Reschedule reason + long booking summary |
| Cancel/reschedule - Summary (short)* | Reschedule indication, Reschedule reason + short booking summary |
| Cancel/reschedule – Customer link | The cancel/reschedule link to be used by the Customer |
| Cancel/reschedule – Tracking ID (canceled booking) | The Tracking ID of the canceled original booking |
* Composite fields: These fields are considered Summary fields and contain a list of values from other fields separated by commas. These are best used for Description fields in 3rd party apps. Learn more about composite fields
Booking page data
This section includes the data related to properties of the booking page used to make the booking.
| Field | Description |
| Booking page - Category | The category to which the Booking page has been assigned |
| Booking page - Internal label | The internal label of the Booking page |
| Booking page - Public link | The public link for the Booking page |
| Booking page - Public name | The public name of the Booking page |
| Master page - Internal label | The internal label for the Master page |
| Master page - Public link | The public link for the Master page |
| Master page - Public name | The public name of the Master page |
| Booking page - Owner | The User whose time is being booked via the Booking page |
| Booking page - Time zone | The time zone of the Booking page |
Event type data
This section includes the data related to properties of the Event types selected during the booking process.
| Field | Description |
| Event type - Category | The Category of the Event type selected by the Customer |
| Event type - Description | The description of the Event type selected by the Customer |
| Event type - Name | The name of the Event type selected by the Customer |
| Event type - Price | The price of the Event type selected by the Customer |
| Event type - Currency | The currency of the Event type selected by the Customer |
Custom fields
OnceHub provides support for custom fields in Zapier. When you add new custom fields, they will appear alongside your system fields when you map trigger fields to action fields.
Below is a description of how each OnceHub custom field is passed through Zapier.
| OnceHub custom field | Target app field format | Example |
| Single-line text field | {Plain text} | This is a single-line example |
| Multi-line text field | {Plain text} | This is a multi-line example |
| Dropdown | {Option value} | This is a dropdown selection example |
| Checkbox | {Option value}, {Option value}, … * Each checked checkbox will be appended at the end separated by a comma ',' | This a one checkbox, This is another checkbox, This is the last checkbox |
| Attachment | {Link} | http://www.example.com/sample.gif |