> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# HubSpot Voice AI Integration Guide

> Connect DialNexa voice AI with HubSpot to qualify callers, update CRM records, log calls, and create clear sales follow-up tasks.

The **HubSpot voice AI integration** connects phone conversations with your marketing and sales records. Use it to recognize an existing contact, qualify a new enquiry, log the call, and give the right owner a specific next step.

<Warning>
  A catalog page describes a possible workflow. It does not confirm that a native HubSpot connector is enabled in your workspace. Check **Integrations** in the DialNexa dashboard first. If HubSpot is not listed, use a custom function, agent webhook, or external automation service.
</Warning>

## When to use the HubSpot voice AI integration

Use HubSpot when:

* Marketing hands inbound leads to sales in HubSpot.
* The agent should greet known contacts using approved CRM context.
* Call answers should update lifecycle stage, lead status, or qualification fields.
* A booked demo or promised callback should create a task for the record owner.

<Tip>
  **Best first workflow:** After an inbound enquiry call, find the contact by phone number, save the qualification answers, log the call, and create a follow-up task for the owner.
</Tip>

## Before you begin

Prepare the following:

* A published DialNexa agent that has already passed a basic test call.
* Access to the DialNexa workspace **Integrations** page.
* A HubSpot account with permission to read or update the required records.
* One test record that does not affect a live customer.
* A list of actions that can run automatically and actions that require human review.

## Choose how to connect HubSpot

| Connection method                                   | Use it when                                               | Important limit                                                             |
| --------------------------------------------------- | --------------------------------------------------------- | --------------------------------------------------------------------------- |
| Workspace connector                                 | HubSpot appears in your DialNexa **Integrations** page    | Available actions and authentication depend on your workspace               |
| [Custom function](/docs/agent-settings/custom-functions) | The agent needs HubSpot data during the live conversation | Keep the request fast and return only the fields the agent needs            |
| [Agent webhook](/docs/api-access/agent-webhooks)         | HubSpot should receive a result after the call            | Your endpoint must authenticate, retry safely, and prevent duplicate writes |
| External automation                                 | The workflow spans HubSpot and several other systems      | Monitor the external workflow separately from the DialNexa call             |

## Build the HubSpot voice AI workflow

1. Define the exact event that starts the action, such as a confirmed booking, qualified lead, support escalation, or completed call.
2. Choose the connection method from the table above.
3. Map caller identity, the DialNexa call ID, the verified outcome, and the destination record ID.
4. Add a condition so uncertain, sensitive, destructive, or high-value changes go to a human-owned queue.
5. Store the destination record URL or ID with the call result so your team can trace the handoff.
6. Test success, no-match, duplicate, permission-error, and timeout cases before using live traffic.

## Data to map between DialNexa and HubSpot

* Contact ID, phone number, email, company, lifecycle stage, and record owner
* Call ID, call direction, disposition, qualification result, and concise summary
* Product interest, company size, location, budget range, and preferred follow-up time
* Meeting ID or task ID when the caller agrees to a next step
* Recording or transcript link only when your policy and caller consent allow it

## High-value HubSpot voice AI workflows

| Call outcome                    | HubSpot result                                             | Human control                                               |
| ------------------------------- | ---------------------------------------------------------- | ----------------------------------------------------------- |
| New enquiry is qualified        | Create or update the contact and save qualification fields | Review possible duplicate contacts                          |
| Caller books a demo             | Log the call and create a dated task for the owner         | Let the owner change priority or assignment                 |
| Existing lead is not interested | Update lead status and add a short reason                  | Require approval before changing marketing consent          |
| Sales question needs expertise  | Add a note and notify the deal owner                       | Do not let the agent change deal value or forecast category |

## Verify the HubSpot integration

Run a test call and confirm that:

1. The workflow finds the intended HubSpot record instead of creating a duplicate.
2. Only the approved fields change.
3. The DialNexa call ID is stored for traceability and retry protection.
4. A failed request creates a visible error or human-owned task.
5. The receiving owner can open the HubSpot record and understand the next step without reading the full transcript.

## Troubleshoot HubSpot integration issues

| Problem                               | What to check                                                                                                                                     |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| HubSpot is not shown in the dashboard | Use a custom function, webhook, or external automation service, or [request the integration](/docs/dashboard-integrations/requesting-new-integrations) |
| Authentication fails                  | Reconnect the account and verify scopes, workspace ownership, and token expiry                                                                    |
| No matching record is found           | Normalize phone numbers and email addresses, then define a clear create-versus-review rule                                                        |
| Duplicate updates appear              | Use the DialNexa call ID as an idempotency key and make retries safe                                                                              |
| The live call becomes slow            | Move nonessential writes to a post-call webhook and keep live lookups small                                                                       |

## Related pages

* [DialNexa integrations overview](/docs/integrations/overview)
* [Connect dashboard integrations](/docs/dashboard-integrations/connecting-integrations)
* [Use integrations in agents](/docs/dashboard-integrations/using-integrations-in-agents)
* [Use integrations in workflows](/docs/dashboard-integrations/using-integrations-in-workflows)
* [Integration workflow tutorials](/docs/tutorials/integration-workflows)