Skip to main content

Aloware-HubSpot integration: Contact property mapping

Laarni D avatar
Written by Laarni D
Updated over a week ago

Understanding contact property mapping settings

Contact property mapping in Aloware controls how contact data flows between Aloware and HubSpot, allowing you to connect any HubSpot contact property (default or custom) to corresponding Aloware fields. This system determines what data gets synchronized, in which direction, and under what conditions the sync occurs, ensuring data consistency and automated synchronization across your platforms.


Accessing and understanding the interface

The mapping interface is in your Aloware admin panel and provides visual indicators to help you understand the status and capabilities of each field mapping: πŸ”’ for locked mappings, 🚫 for fields already mapped, and πŸ—‘οΈ for removable mappings.


Core mapping principles

Unlike basic integrations, Aloware-HubSpot property mapping follows specific rules and behaviors that are important to understand:

Best practice: HubSpot as source of truth

For optimal data consistency, HubSpot should serve as your primary data repository. This means:

  • Most data flows from HubSpot into Aloware

  • Changes in HubSpot automatically update Aloware

  • Your team maintains consistent data across platforms

  • Reduces data conflicts and synchronization issues

Three (3) types of field mapping categories

  1. Default locked fields - these are essential, permanent mappings that form the backbone of the integration:

    1. Include core contact properties like email and phone

    2. Cannot be modified or removed

    3. Automatically sync based on preset rules

    4. Marked with a πŸ”’ in the interface

  2. Default open fields - pre-configured mappings that offer flexibility:

    1. Can be modified or removed as needed

    2. Include properties like Last Call Dispositions

    3. Allow customization of sync direction

    4. Support your specific workflow needs

  3. Custom fields - user-defined connections between systems:

    1. User-created mappings

    2. Connect custom properties between systems

    3. Maximum flexibility in configuration


Configuring your contact property mappings

After understanding the basic principles, your property mapping configuration involves several key components that maintain data consistency between Aloware and HubSpot. Each component serves a specific function in ensuring proper data flow between systems.

Default field mappings

These are often automatically established and adhere to the best practice of HubSpot serving as the primary source of data, meaning Aloware primarily reads this information. Verify these mappings are present. Modifications are typically not allowed or recommended.


Special field types

Contact disposition status

A contact disposition (in Aloware) or lead status (in HubSpot) refers to the status or outcome associated with a contact in Aloware or HubSpot. This could indicate different stages of engagement or interaction, such as New Lead, In progress, or Contacted.

The sync behavior for this mapping is fixed and one-directional:

HubSpot β†’ Aloware ONLY (Contact Disposition Status ← Lead Status)

If you change the lead status in HubSpot, the change will automatically update the Contact Disposition Status in Aloware.

If you change the contact disposition status in Aloware, the change will not update the Lead status in HubSpot.

What your agents see in Aloware Talk

In Aloware Talk, your agents will only see Lead Statuses that are available and synced from your HubSpot account. These options are marked with a πŸ” icon to indicate their HubSpot origin.

If you ever disconnect and reconnect the HubSpot integration, this mapping automatically resets to HubSpot β†’ Aloware, which is its permanent fixed direction.


Contact ownership mapping

Contact ownership mapping determines which user is assigned as the owner of a contact in both systems. This mapping requires configuration of both field selection and sync direction.

For field selection, you can map Aloware's contact owner field to either:

  • HubSpot's standard contact owner field

  • A custom text field you've created in HubSpot

The sync direction offers three (3) configurations:

  1. Bi-directional sync: Contact owner (Aloware) β†”οΈŽ Contact owner (HubSpot)

    Changes in either system update the other automatically.

  2. Aloware to HubSpot: Contact owner (Aloware) β†’ Contact owner (HubSpot)

    Only Aloware changes update HubSpot. HubSpot changes won't affect Aloware, even with integration card sync.

  3. HubSpot to Aloware: Contact owner (Aloware) ← Contact owner (HubSpot)

    Only HubSpot changes update Aloware. This is the default if the integration is reset.

Mapping Aloware's contact owner to a HubSpot custom field

When using a custom HubSpot field for contact owner mapping, updates require manual synchronization. Users must click the Sync with HubSpot button on the contact's integration card in Aloware to reflect HubSpot changes.

User list for contact owner selection

When setting up contact owner mapping in Aloware, the dropdown list of users available for selection will only show users who are properly synced between Aloware and HubSpot. Users not synced with the CRM will not appear in this list.

Mapping modification rules

The contact owner mapping cannot be deleted, though you can modify its field connection and sync direction. When selecting contact owners in Aloware, only users properly synced between both systems will appear as options.

Red indicates locked (non-editable), green indicates unlocked (editable)


Other fixed mappings (Aloware β†’ HubSpot)

These mappings send specific pieces of information from Aloware to custom fields you create in HubSpot. The direction is Aloware β†’ HubSpot ONLY.

Field name in Aloware

Field name in HubSpot

Field type

DNC

Custom in HubSpot

(e.g., "DNC")

Single checkbox

Line type

Custom in HubSpot

(e.g., "Line type checkbox"

Dropdown select

Last inbound text message date

Custom in HubSpot

Date picker

Last outbound text message date

Custom in HubSpot

Date picker

Last inbound text message

Custom in HubSpot

Multi-line text

Last outbound text message

Custom in HubSpot

Multi-line text

Total inbound text messages

Custom in HubSpot

Number

Total outbound text messages

Custom in HubSpot

Number

Last inbound call date

Custom in HubSpot

Date picker

Last outbound call date

Custom in HubSpot

Date picker

Total inbound calls

Custom in HubSpot

Number

Total outbound calls

Custom in HubSpot

Number

Last inbound call time

Custom in HubSpot

Single-line text

Last outbound call time

Custom in HubSpot

Single-line text

Last inbound message time

Custom in HubSpot

Single-line text

Last outbound message time

Custom in HubSpot

Single-line text

Last call disposition

Custom in HubSpot

Single-line text

Last inbound call disposition

Custom in HubSpot

Single-line text

Last outbound call disposition

Custom in HubSpot

Single-line text

Last inbound and outbound engagement

Custom in HubSpot

Date and time picker

Last inbound engagement

Custom in HubSpot

Date and time picker

Last outbound engagement

Custom in HubSpot

Date and time picker

First inbound call date time

Custom in HubSpot

Date and time picker

First outbound call date time

Custom in HubSpot

Date and time picker

First inbound text message date time

Custom in HubSpot

Date and time picker

First outbound text message date time

Custom in HubSpot

Date and time picker

First inbound engagement date time

Custom in HubSpot

Date and time picker

First outbound engagement date time

Custom in HubSpot

Date and time picker

One-way mappings (HubSpot β†’ Aloware)

These sample mappings demonstrate how HubSpot data can be sent to Aloware. These mappings are one-directional (HubSpot to Aloware only).

Field name in Aloware

Field name in HubSpot

Field type

Contact disposition status

Lead status

Radio select

Selectable direction (Inbound/ Outbound/ Bidirectional)

These fields support configurable sync directions. You can choose whether data flows from HubSpot to Aloware (inbound), from Aloware to HubSpot (outbound), or both.

Field name in Aloware

Field name in HubSpot

Field type

Contact owner

Contact owner

Select

Address

Street address

Single-line text

City

City

Single-line text

Country

Country/region

Single-line text

State

State/region

Single-line text

Zipcode

Postal code

Single-line text

Company name

Company name

Single-line text

Date of birth

Date of birth

Single-line text

First name

First name

Single-line text

Last name

Last name

Single-line text

Website

Website URL

Single-line text

Time zone

Time zone

Dropdown select

Lead source

Custom in HubSpot

-

Incoming number

Custom in HubSpot

-

Custom field 1

Custom in HubSpot

-

Custom field 2

Custom in HubSpot

-

TCPA Approved

Custom in HubSpot

-

Aloware contact link

Custom in HubSpot

Multi-line text

Aloware contact ID

Custom in HubSpot

Single-line text

Lifecycle stage

Custom in HubSpot

Radio select


Synchronizing call disposition options from HubSpot

To ensure consistency in call logging, Aloware dynamically displays the list of call dispositions (e.g., "Left voicemail," "Connected," "No Answer") that are defined and managed within your HubSpot account.

What agents see in Aloware Talk

When logging a call, the disposition options available for selection by agents in Aloware are directly sourced from HubSpot. These options are often marked with a πŸ” (lock icon) to indicate they are synced from HubSpot, ensuring standardized terminology across platforms.

Did this answer your question?