1. Help Center
  2. Avoma Scheduler

Data pushed by Avoma Router to HubSpot and Salesforce

When prospects interact with Avoma router, Avoma updates your CRM with the information about the prospect and the meeting they book.

Table of Contents

  1. Data pushed to HubSpot by Avoma Router
    1. HubSpot Contact Properties
    2. HubSpot Meeting Engagement
  2. Data pushed to Salesforce by Avoma Router
    1. Salesforce Lead/Contact fields
    2. Salesforce Meeting Event.

Data pushed to HubSpot by Avoma Router :

The Avoma router has the capability to push prospect details to the contact object in HubSpot, as long as the necessary fields are created for the HubSpot contact object. Additionally, when a meeting is booked, the Avoma router automatically creates a meeting and associates it with the contact that booked the meeting. Any updates made to the meeting in Avoma will also be reflected in HubSpot.

HubSpot Contact custom properties

HubSpot admins will need to create the following fields against HubSpot contact so that Avoma can update these fields with the latest information. For better organization, you can group them under a separate group . For e.g  "Avoma Contact Details",  "Avoma Meeting Details"

In order to ensure correct updation of fields, the names and internal names of these fields will have to be exactly as suggested below -

  1. Avoma Booking Source : This will be the name of the Router.

    1. Field label : Avoma Booking Source

    2. Internal Field Name : avoma_booking_source

    3. Field Type : Text Field

  2. Avoma Booking Status : The value of this property will be “Booked” when the prospect books a meeting after form submission and “Abandoned” when the prospect fills a form but does not book a meeting.

    1. Field label : Avoma Booking Status

    2. Internal Field Name : avoma_booking_status

    3. Field Type: Text Field

  3. Avoma Meeting Creation Date : The date-time of the most recent meeting created through Router.

    1. Field label : Avoma Meeting Creation Date

    2. Internal Field Name : avoma_meeting_creation_date

    3. Field Type : Date Field

  4. Avoma Meeting Outcome :  The outcome of the most recent meeting that was created through Router as updated in Avoma .

    1. Field label : Avoma Meeting Outcome

    2. Internal Field Name : avoma_meeting_outcome

    3. Field Type : Text Field




These properties allow you to create customized workflows in HubSpot. For example, you can set up a workflow to automatically start an email sequence if the Avoma Booking status is "Abandoned".

HubSpot Meeting Engagement

The Avoma router is also capable of generating a Meeting engagement in HubSpot when a prospect schedules a meeting after submitting a form. This functionality is based on a configuration setting in the "Advanced Settings" section of the router.

Note : If your reps have enabled the calendar sync with HubSpot, and if the above configuration setting is also enabled, it will create duplicate events in HubSpot. However, the one that is created through calendar sync will not have Meeting Type and Outcome set. These fields could be used to ignore these Meeting Engagement records in reporting or segmentation. 

The meeting engagement will be updated with the following properties

  1. Meeting Type : The purpose of the scheduling page that was shown to the lead . To ensure a valid value for this property, please ensure that all the scheduling pages that will be used in the router have the conversation type field set. 

  2. Outcome : When the meeting engagement is created, this will be updated to Scheduled. The values this property can take are - Scheduled,  RescheduledCanceled,  No-Show or any other outcome based on the meeting outcome in Avoma.

  3. Duration : Auto-calculated by subtracting the meeting start time and end times.

  4. Meeting Title : Event title that is configured for each scheduling page that is used in Avoma router as a route.

  5. Meeting Description : Event description that is configured for each scheduling page that is used in Avoma router as a route.

Any updates made to the outcome for this meeting engagement will also be synced back to Avoma. 

Data pushed to Salesforce by Avoma Router :

Avoma router can push lead/contact details to Salesforce provided the required fields are created in Salesforce.

Salesforce Lead/Contact custom fields :

In order for Avoma to update the necessary fields with the latest information, Salesforce administrators will need to create the following fields against Salesforce Lead/Contact. To ensure proper updating of fields, it is important to use the suggested names and internal names listed below -

  1. Avoma Booking Source

    1. Field Label : Avoma Booking Source

    2. Internal Field Name : Avoma_Booking_Source__c

    3. Field Type : Text (100)

  2. Avoma Booking Status

    1. Field Label : Avoma Booking Status

    2. Internal Field Name : Avoma_Booking_Status__c

    3. Field Type : Text (100)

  3. Avoma Meeting Creation Date

    1. Field Label : Avoma Meeting Creation Date

    2. Internal Field Name : Avoma_Meeting_Creation_Date__c

    3. Field Type: Date

  4. Avoma Meeting Outcome

    1. Field Label : Avoma Meeting Outcome

    2. Internal Field Name : Avoma_Meeting_Outcome__c

    3. Field Type: Text (100)

Salesforce Meeting Event 

The Avoma router is also capable of generating a meeting event in Salesforce when a prospect schedules a meeting after submitting a form. This functionality is based on a configuration setting in the "Advanced Settings" section of the router.

The meeting event will be updated with the following properties

  1. Subject : This will be the title of the meeting event as configured in Avoma.

  2. Start : This will be the meeting start time as written by Avoma
  3. End : This will be the meeting end time as written by Avoma
  4. Description: This will be the event description as configured in the Event Description field in the scheduling page through which this event was booked.
  5. Assigned To: This will be the host of the meeting.
  6. Type : The type of this event will be "Meeting"
  7. Name : This will contain the name of associated lead or contact.
  8. Related To : This will contain the name of associated account or deal. 

Along with the above properties, Avoma also writes two more properties to this event - Avoma Meeting Type and Avoma Meeting Outcome. 

It is important to note that these properties are custom fields and must be created in Salesforce for Activiy object. Once created, they can be added to the Event page layout. To create custom fields for Avoma Meeting Type and Avoma Meeting Outcome, please follow the steps below.

  1. In your Salesforce account, go to the Setup area. 
  2. In the platform tools section, click Objects and Fields > Object Manager

  3. In the Object Manager list, select Activity. 
  4. In the activity configuration, click on Fields and Relationships and create two new custom fields 

  5. Please ensure that these two new fields adhere to the following configuration :
    1. Avoma Meeting Type
      1. Field Label : Avoma Meeting Type
      2. Field Name : Avoma_Meeting_Type
      3. Field Type : Text (100)
      4. Internal Field Name : Avoma_Meeting_Type__c
    2. Avoma Meeting Outcome
      1. Field label : Avoma Meeting Outcome
      2. Field Name : Avoma_Meeting_Outcome
      3. Field Type : Text (100)
      4. Internal Field Name : Avoma_Meeting_Outcome__c
  6. After creating these two fields, go back to Object Manager and in the Object Manager list, select Event.
  7. In the  Event configuration, go to Page Layout > Event layout to edit the event layout. 
  8. To include Avoma Meeting Type and Avoma Meeting Outcome in the event layout, simply drag the two custom fields you created earlier from the Fields section to the Event Detail section. 

After completing these steps, Avoma will automatically update the event properties whenever a meeting is booked through the Avoma Router.