HubSpot
Overview
With the HubSpot source, you can create a one-way or two-way sync between HubSpot and Intempt to unify all your customer data in one platform. This allows you to transfer company, contact, and deal-related data between HubSpot and Intempt, enriching user profiles and enabling targeted engagement and personalization campaigns.
After creating a Hubspot source, you will be able to use these events:
| Event Name | Description |
|---|---|
| Contact created | Triggered when a new contact is added to the HubSpot CRM. This includes capturing all relevant information such as name, email, and any custom fields associated with the contact. |
| Contact updated | Occurs when any details associated with an existing contact are changed. This can include updates to contact information, subscription status, or any modifications in the custom fields. |
| Company created | Triggered when a new company is registered in the HubSpot CRM. This event captures company-specific details such as name, industry, and size, along with other pertinent data. |
| Company updated | Occurs when there is a change or update in the existing company details within HubSpot. Changes might include updates to company size, revenue, contact information, etc. |
| Deal created | Triggered when a new deal is created in HubSpot. This includes all relevant deal details such as associated contacts or companies, deal stage, deal value, and expected close date. |
| Deal updated | Occurs when any details of an existing deal are updated. Updates can include changes in deal stage, adjustments in value, updates in associated contacts or companies, or the timeline for closing. |
How to create a new HubSpot source
Go to Sources and select "Create source" -> Hubspot option.
Connect to a HubSpot account by clicking the "Connect Hubspot" button.
Enter your HubSpot account credentials and confirm connecting the app.
Once connected, configure sync settings:
Merge Options. Choose how to handle records:
- Automatically create new records if they do not exist and update existing records: This option ensures that all new contacts or accounts are created in Intempt if they are not already present, and existing records will be updated with the latest information.
- Only update records that already exist, without creating new ones: This option ensures that only existing records are updated, preventing the creation of new records in Intempt.
User and Account Mapping
Mapping allows you to specify how data fields from HubSpot correspond to fields in Intempt.
User Mapping
- User mapping is required. Every HubSpot contact must have a corresponding user in Intempt.
- Email field cannot be deleted. The email field is the unique identifier and cannot be removed from the mapping configuration.
Account Mapping
- Account mapping is optional. Users can choose whether to sync company data from HubSpot to Intempt.
- If enabled, the domain field is required and cannot be deleted. The domain field acts as the unique identifier for accounts and is essential for mapping organization-level data.
Customizing Mappings
- Users can add new field mappings to align HubSpot data with custom attributes in Intempt.
- Users can delete field mappings as needed, except for required fields (email for users, domain for accounts).
- The Accounts toggle lets users enable or disable syncing for accounts option.
Configure your sync direction
Click the arrows dropdown menu, and select whether the sync is bi-directional or one way between the Hubspot and Intempt or vice versa.
There are three options:
- Data syncs between apps: all new and updated object information will be synced between the two apps. Properties will be merged for records that already exist in both platforms.
- Data syncs only to HubSpot from Intempt.
- Data syncs only to Intempt from Hubspot.
As a final step, configure the sync start date.
By default, Intempt will sync all data available in your store. However, you can also select a custom sync time if you don't want to ingest all of the historical data.
Once the source is created, you can update the sync schedule and frequency in the overview tab.
How users are identified
Intempt maps the fields below to resolve identities across the project.
| Intempt identifier | HubSpot identifier |
|---|---|
| Profile ID | Contact ID |
| User ID | Email, Phone |
| Account ID | Company ID, Company domain |
Attribute reference
Contact updated, contact created
| User attribute name | Description | Example Value |
|---|---|---|
| The primary email address of the contact. | [email protected] | |
| First name | The first name of the contact. | John |
| Last name | The last name of the contact. | Doe |
| Phone | The contact's phone number. | +19995553333 |
| Country | The country associated with the contact's address. | United States |
| City | The city associated with the contact's address. | Los Angeles |
| Website | The contact's personal or company website. | http://example.com |
| State | The state or region associated with the contact's address. | California |
| Work email | The contact's work email address. | [email protected] |
| Postal code | The contact's zip code. | 90001 |
| Company name | The name of the contact’s company. | Microsoft |
| Total revenue | Total dollar amount of all associated deals that have been closed as won. | 5000000 |
| Annual revenue | The annual revenue of the contact's company. | 5000000 |
| Create date | The date and time the contact was created. | 2023-04-01T12:00:00Z |
| Buying role | The role that the contact plays during the sales process. | Champion |
| Created by user ID | The user who created the contact. This value is set automatically by HubSpot. | 987654321 |
| Is unworked | Indicates whether the contact is marked as unworked. | True |
| Lead status | The contact and company property that indicates where the contact or company is within a buying cycle as a lead. | New |
| Record ID | The unique identifier for the contact. This value is set automatically by HubSpot. | 987654321 |
| Timezone | The timezone associated with the contact. | 2023-04-01T12:00:00Z |
| Contact owner | The contact's owner. | [email protected] |
| Team name | The name of the team to which the contact owner belongs. | Inside sales |
| Industry | The industry the contact's company operates in. | Technology |
| Last modified date | The date and time the contact record was last modified. | 2023-04-01T12:00:00Z |
| Lifecycle stage | A property used to indicate at what point the contact is within the marketing/sales process. | Lead |
| Last activity date | The last date on activity. | 2023-04-01T12:00:00Z |
| Mobile phone | The contact's mobile phone number. | +19995553333 |
| Recent deal amount | The amount of the most recent deal associated with the contact. | 500000 |
Good to know
"Updated" type events (e.g. Contact updated, Company updated, Deal updated) will only work for the new events that will be synced to the project. Intempt does not sync "update" type events done before installing the source.
Company created, company updated
| Account attribute name | Description | Example Value |
|---|---|---|
| Domain | The primary domain associated with the company. | example.com |
| Address | The physical address of the company. | 123 Main St, Example City |
| Address 2 | The secondary address of the company. | Suite 100 |
| Website | The company's personal website. | http://example.com |
| Industry | The industry the company's company operates in. | Technology |
| Number of employees | The total number of employees working at the company. | 200 |
| Country | The country associated with the company's address. | United States |
| City | The city associated with the company's address. | Los Angeles |
| State | The state or region associated with the company's address. | California |
| Annual revenue | The annual revenue of the company. | 500000 |
| Close date | The anticipated close date of the next deal associated with the company. | 2023-04-15T12:00:00Z |
| Create date | The date and time the company was created. | 2023-04-15T12:00:00Z |
| Description | A description of the company. | Leading provider of XYZ |
| Created by user ID | The user who created the company. This value is set automatically by HubSpot. | 987654321 |
| Last modified date | The date and time the company record was last modified. | 2023-04-01T12:00:00Z |
| Lead status | The company property that indicates where the contact or company is within a buying cycle as a lead. | New |
| Record ID | The unique identifier for the company. This value is set automatically by HubSpot. | 987654321 |
| Company owner | The email address of the user assigned as the owner of a company. | http://example.com |
| Lifecycle stage | The current lifecycle stage of the company. | Lifecycle stage |
| Company name | The name of the company. | Microsoft |
| Phone | The company's phone number. | +19995553333 |
| Recent deal amount | The amount of the most recent deal associated with the company. | 100000 |
| Recent deal close date | The most recent date a deal associated with the company was closed. | 2023-04-06T12:00:00Z |
| The primary email address of the company. | [email protected] | |
| Timezone | The timezone associated with the company. | 2023-04-01T12:00:00Z |
| Total money raised | The total money raised in the company. | 100000 |
| Total revenue | The total revenue generated from the company. | $500,000 |
| Type | The type of company (e.g., Customer, Partner, Prospect). | Customer |
| Postal code | The ZIP code associated with the company's address. | 90210 |
Deal created, deal updated
| Attribute name | Description | Example Value |
|---|---|---|
| Deal associated company name | The name of the company associated with the deal | Microsoft |
| Deal associated contact name | The name of the contact associated with the deal | John Doe |
| Deal owner’s email | The email address of the user assigned as the owner of a contact. | [email protected] |
| Deal owner’s first name | First name of the contact owner. | John |
| Deal owner’s last name | The last name of the user assigned as the owner of a contact | Doe |
| Team name | The name of the team to which the contact owner belongs. | Inside sales |
| Create date | The date and time the deal record was created. | 2023-03-01T12:00:00Z |
| Is closed | Indicates whether the deal is closed. | False |
| Projected amount | The projected amount for the deal. | 10000 |
| Total contract value | The total contract value associated with the deal. | 15000 |
| Time in appointment scheduled | Duration the deal has been in the "Appointment Scheduled" stage. | 36 hours |
| Time in qualified to buy | Duration the deal has been in the "Qualified to Buy" stage. | 5 days |
| Closed amount | The amount the deal was closed for. | 8000 |
| Closed won date | The date the deal was closed as won. | 2023-04-08T12:00:00Z |
| Closed won count | The count of times the deal was closed as won. | 1 |
| Time in closed won | The duration the deal has been in the "Closed Won" stage. | 14 days |
| Pipeline | The pipeline to which the deal belongs. | Sales Pipeline |
| Days to close raw | The raw number of days from deal creation to deal close. | 30 |
| Deal name | The name of the deal. | Example Deal |
| Number of associated contacts | The total number of contacts associated with the deal. | 3 |
| Time in closed lost | The duration the deal has been in the "Closed Lost" stage. | 7 days |
| Days to close | The number of days from deal creation to deal close. | 45 |
| Priority | The priority level of the deal. | High |
| ACV | The Annual Contract Value of the deal. | 12000 |
| Is closed won | Indicates whether the deal has been closed as won. | False |
| Deal stage | The current stage of the deal within its pipeline. | Proposal sent |
| MRR | The Monthly Recurring Revenue associated with the deal. | 1000 |
| ARR | The Annual Recurring Revenue associated with the deal. | 12000 |
| Deal type | The type of deal, such as new business or renewal. | New business |
| Amount | The amount associated with the deal. | 15000 |
| Close date | The anticipated close date of the deal. | 2023-04-30T12:00:00Z |
| Date entered contract sent | The date the deal entered the "Contract Sent" stage. | 2023-03-23T12:00:00Z |
| Date entered appointment scheduled | The date the deal entered the "Appointment Scheduled" stage. | 2023-03-24T12:00:00Z |
| Latest meeting activity | The most recent meeting activity related to the deal. | 2023-03-16T12:00:00Z |
| Companies | IDs of companies associated with the deal. | ["123456", "789012"] |
| ID | The unique identifier of the deal. | 123456789 |
| Contacts | IDs of contacts associated with the deal. | ["234567", "890123"] |
Good to know
Events "Deals created" and "Deals updated" won't have a correct event count in a project but will have a correct count per user and account. These events indicate that "Deal was created and associated with user/account" or "Deal updated and associated with user/account"
Deals, Contacts, and Companies will have updated and created events. . And created objects already have a flag that they were updated.
Updated 19 days ago