# HubSpot Nimbata's HubSpot integration sends call data to HubSpot. When a caller is not in HubSpot yet, Nimbata creates the records you choose, such as a contact and an inbound call activity. When the caller already exists, it updates the HubSpot properties you map. A workflow decides which calls are sent. **Before you start** - Permissions: HubSpot, under Integrations, in your Nimbata role - A HubSpot account you can sign in to. - The Nimbata project whose calls you want to send: the integration is set up per project. ## Connect HubSpot > **Tip:** The integration is configured at the project level. Make sure you're editing the correct project before proceeding. 1. (1) **Open the HubSpot integration** Go to **Integrations** and click **Go to integration** on the **HubSpot** tile (1), or go straight to [Integrations > HubSpot](https://app.nimbata.com/integrations/service/hubspot). [The HubSpot tile on the Integrations page, with Go to integration marked 1] *Open the HubSpot tile (1).* 2. (1) **Click Connect** Click **Connect** (1). [The HubSpot integration page before it is connected, with the Connect button marked 1, above the Caller not found and Caller found sections and Send Test and Save] *Click Connect (1). The two sections below fill in once HubSpot is connected.* 3. **Choose your HubSpot account** - A pop-up asks you to choose a HubSpot account. - Select your account and click **Choose Account**. You're then shown the permissions Nimbata is requesting. Review them and click **Connect app** to complete the connection. ![The HubSpot OAuth pop-up, Connecting Nimbata to HubSpot, with an account selected and Choose Account.](https://help.nimbata.com/_astro/01-screenshot-2026-03-17-181235_1os58j0.DoBbYrND_Z2ntuIj.webp) ## Configure HubSpot Each setup, such as **HubSpot Settings 1**, has a **CRM** tab and a **Form** tab. The **CRM** tab, open by default, has two sections: **Caller not found**, what Nimbata creates when the caller is not in HubSpot, and **Caller found**, what it updates when they are. To send different calls to HubSpot in different ways, click **Set up HubSpot** to add another setup; each workflow picks the setup it sends. 1. **Configure what happens when a new lead calls** Expand the **Caller 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, for example 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, for example 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. > **Note:** SHORTCUT: click Use Default Config to auto-populate the recommended field mapping. 2. (1) **Configure what happens when an existing customer calls** Expand the **Caller found** section. First, set two matching preferences: 1. **Which entity to enrich** (1): choose **Contact**, **Company**, or **Both**. 2. **How to handle duplicates** (2): if the same Caller ID appears across multiple records, choose **Handle first**, **Handle all**, or **Ignore all**. Then use the **Update** tab (3) 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). Use **Add property** under the fields to map additional fields, or click **Use Default Config** to apply the recommended setup automatically. [The HubSpot Caller found section: the entity question with Contact chosen, marked 1, the duplicates question with Handle first chosen, marked 2, and a Contact on the Update tab, marked 3, with Mobile Phone Number, Tracking Source and Date - Time of call mapped] *Choose the entity (1) and how to handle duplicates (2), then map the properties to update on the Update tab (3).* ## Test the integration 1. **Click Send Test and Save** Click **Send Test and Save** at the bottom of the page. This verifies that call data is reaching the right HubSpot properties before going live. A panel opens with a box for each Nimbata field your mapping uses. 2. **Send a test event** Fill in test values, including a **Caller ID**, and click **Send event**. The test follows the same rules as a call: if the Caller ID is already in HubSpot, Nimbata runs your **Caller found** actions, otherwise your **Caller not found** actions. Nimbata shows the result at the top of the panel, then check HubSpot for the record. 3. **Save the setup** Click **Save**. ## Send calls with a workflow Nimbata sends a call to HubSpot when a workflow with a **HubSpot** action runs for it. A workflow that runs when a call ends, with no filter, sends every call, and its filters (for example call outcome or tracking number) narrow it down. 1. **Create a workflow** Go to **Workflows**, click **Create** and choose **From Scratch**. Keep the **Inbound Call** trigger with **Call Ends**, and add any filters you need. 2. (1) **Add the HubSpot action** Click the **+** plus sign, select **Perform action**, and choose **HubSpot** under **Integrations**. Pick your setup under **Select configuration** (1), then click **OK**. [The HubSpot pop-up of the workflow builder, with the HubSpot Settings 1 setup selected and marked 1] *Pick the HubSpot setup to send (1), then click OK.* 3. (1) **Enable the workflow** Click **Enable** (1). [A workflow firing on Inbound Call, Call Ends, with a HubSpot action sending HubSpot Settings 1, and the Enable button marked 1] *The workflow sends every inbound call to HubSpot when it ends. Click Enable (1).* Detailed guide: [Create a workflow](https://help.nimbata.com/workflows/workflows#create-a-workflow) ## Check it worked The HubSpot page now shows the workflow that uses the integration, and the setup lists it. Place a test call to one of your tracking numbers: once it ends, the record appears in HubSpot. [The connected HubSpot integration, used in 1 workflow, with HubSpot Settings 1 used by the HubSpot calls workflow] *The page shows Used in 1 workflow, and the setup lists the workflow that sends it.* 🎉 That's it! From now on, calls that meet your workflow criteria are automatically logged in HubSpot. ## Send calls to a HubSpot form Instead of creating records, a setup can submit each call to one of your HubSpot forms, so phone leads arrive the way your web leads do. 1. **Open the Form tab** Once HubSpot is connected, click the **Form** tab in your setup. The setup's badge changes from **CRM** to **Form**. 2. **Choose the form** Under **Hubspot Form Settings**, pick the form Nimbata should submit call details to. 3. **Enter your email domain** HubSpot only processes a form submission with an email address, so Nimbata submits each call with the calling number at the domain you enter, for example `4155550123@harborpine.example`. 4. **Add the call fields to a HubSpot form** When the form is a HubSpot form, Nimbata lists the fields it must include: **email**, **phone**, **tracking_source**, **tracking_number**, **call_status**, **duration_seconds**, **utm_source**, **utm_medium** and **click_id**. The setup is sent by a workflow, as above. ## Troubleshooting ### The HubSpot tile says Disconnected Nimbata has lost its connection to HubSpot. Your HubSpot settings are saved, but nothing is sent until you reconnect: open the integration and click **Reconnect** in the red **Disconnected.** banner. [The HubSpot tile on the Integrations page with a red Disconnected badge] *A disconnected integration shows a red Disconnected badge on its tile.* ### Send Test and Save is greyed out - Connect HubSpot first: the button stays off until the integration is connected. - Map at least one field under **Caller not found** or **Caller found**. - If the test answers "Please provide a valid caller id", fill in the **Caller ID** box in the test panel. ### Calls are not reaching HubSpot - Check that a workflow with a **HubSpot** action is enabled, and that its filters let the call through. - Check that the workflow's HubSpot action uses the setup you configured, under **Select configuration**. - Check that the HubSpot tile does not say **Disconnected**. - Send a test from **Send Test and Save** to see the error HubSpot returns. ### You can't remove the setup **Remove setup**, in the three-dot menu of the HubSpot page, is greyed out while workflows use the integration, and shows how many ("Used by 1 workflow"). Remove the HubSpot action from those workflows first. ## Remove the HubSpot app > **Tip:** To uninstall the HubSpot + Nimbata integration, follow these four steps. 1. **Open HubSpot Settings** Log in to your HubSpot account and go to **Settings**, at the top right of your screen. ![The HubSpot top navigation bar with the Settings icon marked.](https://help.nimbata.com/_astro/01-hubspot_1vvrf3c.B405YI5C_1Ddv4t.webp) 2. **Open Connected Apps** Expand the **Integrations** tab and click **Connected Apps**. ![The HubSpot Settings menu with Integrations expanded and Connected Apps selected.](https://help.nimbata.com/_astro/02-integrations_1cbhrey.B_XuQA_U_Z15lHCe.webp) 3. **Find Nimbata** Search for **Nimbata** in your connected apps list and click the **Actions** button in the Nimbata card. ![HubSpot Connected apps filtered to Nimbata, with the Actions button on the Nimbata card.](https://help.nimbata.com/_astro/03-image_1acd035.CqgJn9Xf_ZKdjqO.webp) 4. **Uninstall the app** Select **Uninstall**. ![The Nimbata card's Actions menu: Contact support, Documentation and Uninstall.](https://help.nimbata.com/_astro/04-284171931484795336666339880016_1137dkt.Cxmzxxfa_Z1O9xxw.webp) > **Note:** Uninstalling the integration won't affect your HubSpot accounts and call data. 🎉 That's it! You have successfully uninstalled the HubSpot + Nimbata integration.