> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.nimbata.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# HubSpot integration: how to set it up in Nimbata

### How to set up your HubSpot integration

| The integration is configured at the project level. Make sure you're editing the correct project before proceeding.

### Step 1. Connect your HubSpot account

* Go to [Integrations > HubSpot](https://app.nimbata.com/integrations/service/hubspot) and click **Sign in with HubSpot**.
* A popup will appear asking you to choose a HubSpot account. 
* Select your account and click **Choose Account**.

You'll then be shown the permissions Nimbata is requesting. 
Review them and click **Connect app** to complete the connection.

![](https://storage.crisp.chat/users/helpdesk/website/-/2/f/4/5/2f459a49cf382400/screenshot-2026-03-17-181235_1os58j0.png)

### Step 2. Configure what happens when a new lead calls

Expand the **"When the Caller ID is not found"** section.
Define what Nimbata creates in HubSpot when an unknown caller dials your tracking number. 

**Common setup:**

**1. Create a Contact**
* Set a recognizable name, e.g. First Name: *Nimbata*, Last Name: *Lead*
* Map the caller's phone number automatically from the Nimbata log. 
* You can also include the GCLID or FBCLID and set the lead status to *New*.

**2. Create an Inbound Call Activity**
* Log who called, which number they called, the talk duration, and marketing details:
* E.g. utm_source, utm_medium, utm_campaign, call page, and a link to the recording

Click **+ Add object** to add each item, then expand it to map the fields you want to populate.

|| SHORTCUT: Click Use Default Config to auto-populate the recommended field mapping.

### Step 3. Configure what happens when an existing customer calls

Expand the **"When the Caller ID is found"** section. First, set two matching preferences:

**1. Which entity to enrich**
* Choose **Contact**, **Company**, or **Both**

**2. How to handle duplicates**
* If the same Caller ID appears across multiple records, choose **Handle 1st**, **Handle all**, or **Ignore all**

Then, use the **Update** tab to define which HubSpot properties should be updated with call data: 

Nimbata maps the **Tracking Source** field on the Contact object to the Configured Tracking Source (default).
Click **+ Add property** to map additional fields, or click **Use Default Config** to apply the recommended setup automatically.

![](https://storage.crisp.chat/users/helpdesk/website/-/2/f/4/5/2f459a49cf382400/screenshot-2026-03-17-185234_sshshn.png)

### Step 4. Test and save

Click **Send Test and Save** at the bottom of the page.
This will verify that call data is reaching the right HubSpot properties before going live.

### Step 5. Set up a workflow to control when data is sent

By default, the integration will fire after every call. 
You can filter which calls get sent to HubSpot by setting up a workflow in Nimbata.

Detailed Guide: [**How to set up your first Workflow**](https://help.nimbata.com/en/article/how-to-set-up-your-first-workflow-example-included-q8c5v5/)
---

🎉 That's it! From now on, calls that meet your workflow criteria will automatically be logged in HubSpot.
---