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

# HubSpot 

> With the HubSpot integration, you can send information collected during a chat to HubSpot and create a Contact record.

![HubSpot integration connected state](https://mintcdn.com/wotnot/IgY-Q46pOTb5_NPe/images/Screenshot-2026-08-25-125639.png?fit=max\&auto=format\&n=IgY-Q46pOTb5_NPe\&q=85\&s=24f330408f2104edef9079c0f8e5e3a7)

> [!NOTE]
>
> The native HubSpot integration currently supports **creating Contact records**.

> [!NOTE]
>
> The HubSpot integration is available on the **STARTER plan and above**.

# What you can do

The native HubSpot integration lets you create a **Contact** in HubSpot using information collected during a chatbot conversation.

The integration currently supports the following operation:

| Operation | What it does |
| - | - |
| **Create Contact** | Creates a new Contact record in HubSpot using values collected during the chat. |

> [!NOTE]
>
> The native integration currently supports **Contact creation only**. It does not provide Contact lookup or fetch operations, and it does not create **Companies** or **Deals**.

# Before you start

Make sure you have:

* A **WotNot Starter plan or above**.
* Access to the HubSpot account you want to connect.
* WotNot variables containing the information you want to send to HubSpot, such as `name`, `email`, and `phone`.
* Any custom Contact properties you want to populate already created in HubSpot.

> [!NOTE]
>
> If you are mapping custom HubSpot properties, create them in HubSpot before configuring the WotNot action block. Use the property's internal name when the mapping requires it, rather than assuming the display label is the property name.

# Connecting HubSpot

Follow these steps to connect your HubSpot account to WotNot:

1. Open your chatbot in the **Bot Builder**.
2. Click **+** to add a new action block.
3. Select **HubSpot**.
4. Click **+ Add account**.
5. A HubSpot authentication window opens.
6. Select the HubSpot account you want to connect.
7. Review and authorize the requested permissions.
8. Return to WotNot and confirm that the HubSpot account is connected.
9. Select the connected HubSpot account from the account dropdown.
10. Map the HubSpot properties to the corresponding WotNot variables.

> [!TIP]
>
> Make sure your browser allows pop-ups. The HubSpot authentication window may not open if pop-ups are blocked.

WotNot's native integration uses **HubSpot OAuth** for the account connection. You do not need to enter a legacy HubSpot API key.

# Using HubSpot in a flow

Once your HubSpot account is connected, add the **HubSpot** action block at the point in your chatbot flow where you want to create the Contact.

1. Open the chatbot in the **Bot Builder**.
2. Click **+**.
3. Select the **HubSpot** action block.
4. Select your connected HubSpot account.
5. Map the HubSpot properties to the WotNot variables containing the required values.
6. Continue the flow through the appropriate output path.

For each HubSpot action block, you will see two output paths:

> [card] SUCCESS
>
> The Contact was successfully created in HubSpot. The chat flow continues through the **SUCCESS** path.

> [card] FAILURE
>
> The Contact could not be created. The chat flow continues through the **FAILURE** path.

![HubSpot execution logs](https://mintcdn.com/wotnot/IgY-Q46pOTb5_NPe/images/Screenshot-2026-08-25-131848.png?fit=max\&auto=format\&n=IgY-Q46pOTb5_NPe\&q=85\&s=5d46d2b2152914516d5ebec423ededfb)

## Viewing execution logs

You can view the result of each HubSpot action execution from:

**App Market → HubSpot → Logs**

# Mapping fields

Map each HubSpot property to the WotNot variable that contains the value you want to send.

For example, if your chatbot collects a visitor's first name, last name, email, and phone number, map those variables to the corresponding HubSpot Contact properties.

| **WotNot variable** | **HubSpot property** | **Required** |
| - | - | - |
| `first_name` | `firstname` (First Name) | Yes |
| `last_name` | `lastname` (Last Name) | Recommended |
| `email` | `email` (Email) | Recommended |
| `phone` | `phone` (Phone Number) | Recommended |

![HubSpot field mapping](https://mintcdn.com/wotnot/rF4EZt89f2IBfLLk/images/Screenshot-2026-08-25-132557.png?fit=max\&auto=format\&n=rF4EZt89f2IBfLLk\&q=85\&s=432a7396886dc0694c6c7ce6e9dd5159)

> [!NOTE]
>
> HubSpot requires at least one of **email**, **firstname**, or **lastname** when creating a Contact. We recommend collecting and mapping the visitor's email whenever possible because HubSpot uses email as a unique identifier for Contacts.

## HubSpot property names

HubSpot properties have both a **display label** and an **internal property name**.

For example:

| Display label | Internal property name |
| - | - |
| First Name | `firstname` |
| Last Name | `lastname` |
| Email | `email` |
| Phone Number | `phone` |

When mapping fields, make sure you use the property expected by the HubSpot integration. A mismatch between the display label and internal property name can cause the request to fail.

## Custom properties

You can also map custom Contact properties created in your HubSpot account.

Before mapping a custom property:

1. Create the property in HubSpot.
2. Confirm that the property exists on the **Contact** object.
3. Use the correct HubSpot property name when configuring the WotNot action.
4. Make sure the value stored in the WotNot variable matches the property's expected format.

For dropdown, radio-select, and other enumeration properties, the value sent by WotNot must match a valid HubSpot option.

> [!NOTE]
>
> You can map up to **50 fields** in a HubSpot action block.

## Empty values

If a mapped WotNot variable is empty, WotNot sends the available value for that field. If HubSpot requires a property that is missing or empty, Contact creation can fail.

If the Contact is not created:

1. Check the **FAILURE** path.
2. Open the HubSpot execution logs.
3. Check which property caused the error.
4. Make sure the corresponding WotNot variable contains a valid value before the HubSpot action runs.

# Troubleshooting

> [accordion] The HubSpot connection no longer works
>
> The HubSpot authorization may have expired or been revoked. Reconnect the HubSpot account and authorize the requested permissions again.

> [accordion] I get an insufficient scopes or permissions error
>
> The connected HubSpot account may not have granted the permissions required by the integration. Reconnect the account and make sure all requested permissions are authorized.

> [accordion] The Contact is created but some properties are blank
>
> Check the field mapping and make sure the corresponding WotNot variable contains a value before the HubSpot block runs. Also verify that you mapped the correct HubSpot property.

> [accordion] A duplicate Contact is created
>
> Check the email value being sent by WotNot and compare it with existing Contacts in HubSpot. HubSpot uses email as a unique identifier for Contacts, but the WotNot native action is designed to create a Contact rather than provide a general-purpose duplicate-checking or upsert workflow.

> [accordion] A property value is rejected
>
> Verify that the value matches the HubSpot property's expected format. This is especially important for dropdown, radio-select, and other restricted property types. Also check that you are using the correct internal property name.

> [accordion] The Contact creation fails because a required field is empty
>
> Make sure at least one of the required Contact properties is populated. For HubSpot Contact creation, at least one of `email`, `firstname`, or `lastname` must be provided.

> [accordion] The request hits a rate limit
>
> HubSpot applies API usage and rate limits based on the app and HubSpot account configuration. If the integration is being used at high volume, check the HubSpot account's API usage and the WotNot execution logs. A rate-limit response can prevent the Contact from being created.

# Disconnecting HubSpot

To disconnect a HubSpot account from WotNot:

1. Go to your **Dashboard → App Market**.
2. Open the **HubSpot** integration settings.
3. Click **Remove** next to your connected HubSpot account.

> [!WARNING]
>
> Disconnecting the HubSpot account prevents live bots from using that connection. If a live bot reaches a HubSpot action while the account is disconnected, the Contact creation can fail and the flow will follow the **FAILURE** path.
>
> Reconnect the HubSpot account before using the HubSpot action in a live bot again.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.