# HubSpot

Integrating HubSpot with Reo.Dev enables seamless two-way data sync, empowering your teams to map and leverage custom account lifecycle and deal stages to drive actionable insights. With this integration, you can read lifecycle stages for contacts and accounts, map custom CRM fields, and sync developer and account insights directly into HubSpot.

Requirements:

* You must be admin of Reo.Dev app
* You must be an admin of your HubSpot CRM instance

### Connect HubSpot

**Step 1**: Go to Settings > Integrations 

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FG0QgcZexgow2f3wotbdG%2Fimage.png?alt=media&#x26;token=71d4d1f2-6cf9-41c4-ad02-ebde0088b9dd" alt=""><figcaption></figcaption></figure>

**Step 2:** Go to Output Integrations > CRM > Click on Connect on the Hubspot Card.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FxhqOiCWYeFUJlXewFVbi%2Fimage.png?alt=media&#x26;token=8787e944-ccfe-4aef-80df-940a8d0d297a" alt=""><figcaption></figcaption></figure>

**Step 3**: You will be redirected to the Authorization flow. Select your HubSpot account and click **Choose Account**.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/a66e57fb-1700-455b-92e0-656fd3a6d464/7a571c99-c8f9-476d-b553-073fa51d5963/images/96e66c81-ce6f-439e-997d-eb67f7e3170f.png)

**Step 4:** Review the requested scope and click **Connect App.**

**Note:** Reo.Dev will request access to read and write contacts and companies and read and edit contact and company properties.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/a66e57fb-1700-455b-92e0-656fd3a6d464/7a571c99-c8f9-476d-b553-073fa51d5963/images/c15b06ae-25e9-4f01-b35c-060ab56a8896.png)

{% hint style="info" %}
In case you have already connected HubSpot app, you will need to Update the HubSpot App permissions. Instead of Connect CTA you will get Update option.
{% endhint %}

And your HubSpot instance will be integrated with Reo.Dev. Click on Continue to configure export and sync settings on Reo.&#x20;

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FJhMBnVpokpwzMYLWikYB%2Fimage.png?alt=media&#x26;token=b395eb7f-88fa-48ac-9028-1b312a713377" alt=""><figcaption></figcaption></figure>

### HubSpot Export Settings

After the HubSpot App is connected, you will be redirected to HubSpot Settings screen to configure the Export and Sync settings.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FuY7durJJWhV9iJ2G9kZs%2Fimage.png?alt=media&#x26;token=7a6e12fe-749f-49b7-8668-88e39bcca4a4" alt=""><figcaption></figcaption></figure>

There are two options to Export data from Reo.Dev

1. **Accounts**

   You can select Accounts if you want to only export accounts from Reo.Dev to HubSpot.
2. **Accounts and Contacts**

   You can select Accounts and Contacts if you want to only export accounts from Reo.Dev to HubSpot. Under Accounts and Contacts, you have an option to sync contacts associated with an account automatically or manually. To sync it automatically, turn on the toggle 'Automatically sync contacts associated with an account'. In this case, all developers tied to a synced account get pushed to CRM even if they don’t match a Reo segment. So Contacts can be synced to HubSpot in two ways:

* **Via Reo segments** **→** Contacts synced this way will have a **Segment** value.
* **Via account association ->** All developers linked to an account are pushed to HubSpot — even if they don’t match a Reo segment. These contacts will have **activity and company data**, but **no segment value.**&#x20;

### HubSpot Field Mapping

Map all the fields from Reo.Dev that you want to send to HubSpot and update existing Accounts and Contacts. This mapping will be used to create new accounts and contacts in HubSpot. You can also select which fields should be updated in HubSpot whenever there is any change in Reo.Dev.

Please note that when we export data from Reo.Dev, we check if the company or contact exists in the HubSpot record or not. If the record is present, we update the corresponding fields based on the mapping preference selected by you and in case the record is not present, we create a new records.

We use the following fields as unique identifiers to prevent duplication:

* Accounts → Company Domain Name
* Contact → email ID

### **Accounts Field Mapping**

We have provision to export following fields for Accounts object to HubSpot.

| **Reo.Dev Field**             | **HubSpot Field**             |
| ----------------------------- | ----------------------------- |
| Company Name                  | Company Name                  |
| Company Domain                | Company Domain Name           |
| Country                       | Country/Region                |
| State                         | State                         |
| City                          | City                          |
| Employee Range                | Employee Range                |
| Annual Revenue                | Annual Revenue                |
| Founded In                    | Year Founded                  |
| Last Activity Date            | REO: Last Activity Date       |
| LinkedIn Company Page         | LinkedIn Company Page         |
| REO Customer Fit Score        | REO: Customer Fit             |
| REO Developer Activity Score  | REO: Developer Activity Score |
| REO: Activity Score (Numeric) | REO: Activity Score (Numeric) |
| REO Segment Name              | REO: Segment Name             |
| REO Account Link              | REO: Account Link             |
| REO Account Summary           | REO: Account Summary          |
| REO Tags                      | REO: Account Tags             |
| REO: Audience Name            | REO: Audiences                |
| REO: Tech Functions           | REO: Tech Functions Summary   |

* **Company Domain** is a mandatory field and is already mapped.
* Fields with prefix REO are automatically created in HubSpot and mapped to corresponding Reo.Dev field.
* For Rest of the fields you can map the corresponding field in HubSpot from the dropdown. If you select Auto Overwrite checkbox, then we will overwrite the existing data in HubSpot during creation and sync operations.

{% hint style="info" %}
**Recommendation:** Fields with prefix REO should always have Auto-Overwrite checkbox as TRUE.
{% endhint %}

### Contacts Field Mapping

We have provision to export following fields for Contacts object to HubSpot.

| **Reo.Dev Field**             | **HubSpot Field**             |
| ----------------------------- | ----------------------------- |
| First Name                    | First Name                    |
| Last Name                     | Last Name                     |
| Business Email ID\*           | Email                         |
| Company Website               | Website URL                   |
| Designation                   | Job Title                     |
| Country                       | Country/Region                |
| State                         | State                         |
| City                          | City                          |
| LinkedIn ID                   | REO: Linked In Profile        |
| Last Activity Date            | REO: Last Activity Date       |
| REO: Developer Summary        | REO: Developer Summary        |
| REO: Segment Name             | REO: Developer Segment Name   |
| REO: Tags                     | REO: Developer Tags           |
| REO: Activity Score (Numeric) | REO: Activity Score (Numeric) |
| REO: Audience Name            | REO: Audiences                |

* **Business email ID** is a mandatory field and is already mapped. We fetch the Business email ID of the developers from third part enrichment service providers.
* In addition to the Business Email ID, **Personal Email IDs** will also be synced **if collected through first-party sources**, including:
  * Signup Forms on your website or documentation pages
  * Product login or signup forms.
* In the Reo.Dev UI, when users hover over the email icon on a profile, if a Personal Email has been enriched and mapped to that profile, it will be displayed alongside the Work Email.
* Fields with prefix REO are automatically created in HubSpot and mapped to corresponding Reo.Dev field.
* For Rest of the fields you can map the corresponding field in HubSpot from the dropdown. If you select Auto Overwrite checkbox, then we will overwrite the existing data in HubSpot during creation and sync operations.

***

### **How Reo.Dev Handles Multiple Email Records in HubSpot**

For each **unique email ID** we treat it as a **separate contact record** in HubSpot. Depending on whether an email already exists in the CRM, the contact is either **updated or created** as per the following scenarios:

| **Scenario**                                      | **Action in HubSpot**                                                          |
| ------------------------------------------------- | ------------------------------------------------------------------------------ |
| **One Email ID exists in CRM**                    | Update existing contact with latest REO data                                   |
| **One Email ID does not exist in CRM**            | Create a new contact record                                                    |
| **Two Email IDs → First exists, second does not** | Update existing contact for first email, create a new contact for second email |
| **Two Email IDs → Neither exists**                | Create two separate contact records (one for each email)                       |
| **Two Email IDs → Both exist in CRM**             | Update both contacts separately with latest REO data                           |

***

### Send developers only with LinkedIn ID to Hubspot CRM&#x20;

You can send contacts with only LinkedIn IDs to Hubspot CRM. If the email ID is not available for a developer, Reo will match contacts by the LinkedIn profile to avoid duplicates and create/update contacts.&#x20;

To enable this, click on the LinkedIn tab under Contacts - Field Mapping in Field Mapping section

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FGn6MpGDSoW6y4md7cZ6Y%2Fimage.png?alt=media&#x26;token=eb88ab49-eea1-4b14-b90d-e1006b5b743d" alt=""><figcaption></figcaption></figure>

Next, select your custom LinkedIn profile field to map the contacts. And in case you are using the custom field created by Reo as the preferred field for mapping the LinkedIn profile - then choose REO:LinkedIn Profile as the field from the drop-down.&#x20;

Note: This mapping will be used to create new contacts with only LinkedIn ID in the CRM

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FIPBn70RMLmaLTnFU4krD%2Fimage.png?alt=media&#x26;token=f293df8c-5037-40b2-b62b-472458b8b2b7" alt=""><figcaption></figcaption></figure>

Once done, click on save.&#x20;

{% hint style="info" %}

### Quick Note on how this works:&#x20;

**Scenario 1: If LinkedIn Profile Mapping is not present:**

* Only developers with a valid email ID (business or First party) are created/updated in CRM
* LinkedIn profile is updated to REO: LinkedIn Profile field

**Scenario 2: If LinkedIn Mapping is present:**

* **In case, email and LinkedIn ID are both available:**&#x20;
  * Sync is done using only the email ID of the developer
* **In case, only Email is available**
  * Sync is done using the email ID of the developer
* **In case, only LinkedIn is available**

  The System checks for the LinkedIn ID present in Reo in the LinkedIn profile field mapping

  * If the LinkedIn ID is found
    * Developer is synced to the existing profile
  * If the LinkedIn ID is not found
    * A new contact is created in Hubspot with the LinkedIn ID as the unique identifier. From the next sync, the same contact is updated
      {% endhint %}

### **Do We Delete Data from Your CRM?**

Reo.Dev does **not delete any data** from your connected HubSpot CRM instance with Reo.Dev — with the **only exception being occasional cleanups** of records that were originally created by Reo.Dev.

These cleanups are **rare and limited strictly to Reo.Dev-originated data**, and are performed to maintain data accuracy and reliability. For example, if a developer contact's work email becomes invalid (e.g., they’ve switched jobs), and a new valid email is identified, Reo.Dev may update or clean up the outdated email to ensure your CRM reflects the most current information.

Rest assured, no third-party or manually added CRM data is ever deleted by Reo.Dev.

***

### **What Happens When a Contact is Updated?**

* If an email already exists in HubSpot, Reo.Dev **updates the mapped fields** (as configured in CRM settings) with the latest developer data.
* Updates **do not overwrite existing CRM data outside the mapped REO fields**.

***

### **How New Contact Records Are Linked to the Same Company/Account**

When Reo.Dev creates new contacts, all the captured data—including the **Company Website (Domain Name)**, job title, LinkedIn profile, and other mapped fields—remains the same across contact records associated with the same company.

**This ensures that:**

* You can easily identify multiple contacts belonging to the same organization in HubSpot.
* Company-wide insights remain consistent, regardless of whether contacts have different email IDs.
* Your CRM data stays structured and organized, preventing fragmented company records.

By maintaining consistent company-level details, Reo.Dev enables seamless account-based contact tracking, helping sales and marketing teams engage with all relevant stakeholders.

{% hint style="info" %}
**Recommendation:** Fields with prefix REO should always have Auto-Overwrite checkbox as TRUE.
{% endhint %}

***

### **Send Tags to Your CRM**

You can now send **Account Tags** and **Developer Tags** directly to your CRM. These tags are fully customizable and provide quick context and insights on already enriched data.

**Why it matters:**\
Tags make it easy to:

* Identify key account traits or developer activities at a glance.
* Segment and prioritize accounts more effectively.
* Provide your sales team with richer, actionable insights to drive better conversations.

**Want to learn more?**\
Check out our [Tags Handbook](https://www.reo.dev/tags-handbook) — a comprehensive guide to tagging and segmenting developers in Reo.Dev. It includes **15+ use case examples** designed to help DevTools GTM teams prospect smarter, increase pipeline, and close deals faster.

***

#### CRM to Revenue: Data In Playbooks

* [Revive Cold Opportunities in your CRM Using Developer Activity Signals](https://www.reo.dev/playbook/revive-cold-opportunities-in-your-crm-using-developer-activity-signals)
* [Monitor Dev Activity in your assigned CRM accounts](https://www.reo.dev/playbook/monitor-dev-activity-in-your-assigned-crm-accounts)
* [Detect Deal Stalls Early: Monitor & Act on Active CRM Opportunities](https://www.reo.dev/playbook/detect-deal-stalls-early-monitor-act-on-active-crm-opportunities)

**Explore the Playbooks Now** → [View All](https://www.reo.dev/playbook-collection/crm)

***

#### CRM to Revenue: Data Out Playbooks

* [Sync Reo.Dev Segments to HubSpot & Run LinkedIn Ads](https://www.reo.dev/playbook/sync-reo-dev-segments-to-hubspot-run-linkedin-ads)
* [Sync High-Intent Accounts to HubSpot & Auto-Assign to Your Sales Team](https://www.reo.dev/playbook/sync-high-intent-accounts-to-hubspot-auto-assign-to-your-sales-team)
* [Sync Reo.Dev Tags Intel to HubSpot & Automate Emails](https://www.reo.dev/playbook/sync-reo-dev-tags-intel-to-hubspot-automate-contextual-emails)
* [Create Custom HubSpot Views with Reo.Dev Intel](https://www.reo.dev/playbook/create-custom-hubspot-views-with-reo-dev-intel)

**Explore the Playbooks Now** → [View All](https://www.reo.dev/playbook-collection/reo-hubspot-workflows)

***

### **User Settings**

You can manage permissions for your team by defining specific users who can send data to HubSpot.

Click on **Configure** in User Settings.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FrzsLA4Vch2X4gCxi6KBj%2Fimage.png?alt=media&#x26;token=928f5018-4a6c-4e7c-862e-84901ebaedea" alt=""><figcaption></figcaption></figure>

You will be redirected to Users Section. You can turn on the toggle button in the CRM access column to allow specific users to send data to HubSpot.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FC0xROMXn9I3pisLQ9og9%2Fimage.png?alt=media&#x26;token=61e508e9-936f-4be8-be78-e263c5a9a840" alt=""><figcaption></figcaption></figure>

#### Export and Sync Frequency

Users will have options to send:

* **Segments to HubSpot**

  User can create a segment and click on **Send to HubSpot**
* **Accounts to HubSpot**

  User can select an account(s) from the Account list and **Send to HubSpot**
* **Developers to HubSpot**

  If Manual contact sync is selected for contacts, users can select developer(s) from the developer tab under Account Details screen and Send to HubSpot

In case of Accounts and Developer, the export happens in real time and HubSpot icon will appear against the record on UI immediately but for segments it may take some time depending on the size of segment.

Once the Accounts and Developers are exported, Reo.Dev will sync data back to HubSpot on a daily basis.

All the accounts and developers that have been synced with HubSpot, will have a HubSpot Icon next to the name.

***

### Map and Tag Custom CRM Account and Deal Stages

#### **Map Account Stages**

Select the "Stages" subtab in the Account - Field Mapping section

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FN0m9ewWVhb9jS4fBoAMR%2Fimage.png?alt=media&#x26;token=e881b111-1207-4d57-ae1b-ef4cfda476ce" alt=""><figcaption></figcaption></figure>

Choose a **Custom Account CRM** field to map as the **Account Lifecycle Stage**.

{% hint style="info" %}
**Note:** Only fields classified as **"Picklist"** in your CRM are available for selection.
{% endhint %}

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2Fq5ZO59npKWhKjFtnXjQz%2Fimage.png?alt=media&#x26;token=aeb3f9ec-7a8e-44d2-927a-ab06bf7ee63c" alt=""><figcaption></figcaption></figure>

Pick all Custom CRM Account Stages you want to define as **"Customer"** in **Reo.Dev**. Multiple stages can be mapped as "Customer" to fit your sales cycle. For example, classify accounts by product line (Cloud vs. Open Source) or customer size (Enterprise vs. SMB).

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F4Hdphwen21wSifBI4Wbz%2Fimage.png?alt=media&#x26;token=0c76dc2e-14cf-4a66-b0e7-199a748d36ec" alt=""><figcaption></figcaption></figure>

**Save the Configuration**

After mapping, click **Save**.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FU8sbfYhmyC4zmrAIUHom%2Fimage.png?alt=media&#x26;token=e4c6e58c-cd60-474e-9117-dee7189048a6" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** Backend updates are applied immediately, but changes in the UI reflecting the new mappings will take up to **24 hours** to refresh.
{% endhint %}

#### **Map Deal Stages**

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FHwVNesNffl2cdqiPtp8U%2Fimage.png?alt=media&#x26;token=8bd7f4a2-6f0d-4a72-a812-dd90624a8b78" alt=""><figcaption></figcaption></figure>

Select a **Pipeline** from the dropdown, as HubSpot supports custom pipelines tied to deal stages.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F7R8ar2djR6fnP7NVuEUn%2Fimage.png?alt=media&#x26;token=11cb340f-69f1-4478-8e14-41e1bbe381dd" alt=""><figcaption></figcaption></figure>

**Next,** select the corresponding deal stage field for the selected pipeline.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FRRJX3Ye7OdS6loO8pHPm%2Fimage.png?alt=media&#x26;token=6a36cef4-d6f4-41cf-a72f-8fe2b12a7eee" alt=""><figcaption></figcaption></figure>

**Save the Configuration**

After mapping, click **Save.**

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/a66e57fb-1700-455b-92e0-656fd3a6d464/7a571c99-c8f9-476d-b553-073fa51d5963/images/7163eaad-f5f9-4036-ab2e-a5e64753ee19.png)

{% hint style="info" %}
**Note:** Backend updates are applied immediately, but changes in the UI reflecting the new mappings will take up to **24 hours** to refresh.
{% endhint %}

### **Learn More About Custom CRM Stages**

To dive deeper into setting up and leveraging **Custom CRM Account and Deal Stages**, refer to our detailed [Custom CRM Stages](https://docs.reo.dev/accounts/custom-crm-stages) guide for step-by-step guidance, use cases, and advanced tips to maximize the value of your Hubspot CRM integration with Reo.Dev.

***

### **Disconnect HubSpot**

You can disconnect HubSpot from the Integrations section

1. **Open Reo.Dev**
2. Navigate to **Integrations → CRM** and click Configure
3. Under HubSpot and click Disconnect at the top right corner

{% hint style="danger" %}
Please note that all the field mappings and user permissions will be lost.
{% endhint %}