> For the complete documentation index, see [llms.txt](https://answeringservicecare.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://answeringservicecare.com/docs/useful-resources/integrations/hubspot.md).

# HubSpot

Connect Answering Service Care to HubSpot to automatically create contacts and tickets, and optionally sync companies, from every call and message.

## How to connect HubSpot to ASC

HubSpot lets Answering Service Care send caller and message details to your HubSpot CRM. Contacts, tickets, and companies stay where your team tracks follow-up work.

Add HubSpot as a delivery method on the on-call calendar. You control which messages flow to HubSpot.

### Quick answer

First, open **Integrations** in the Client Portal. Select **Connect HubSpot** to authorize the app.

Then add **HubSpot** as a delivery method on the on-call calendar. Messages create HubSpot records only where you add that delivery method.

### What this integration does

Connecting under **Integrations** authorizes ASC for your HubSpot account. It does not send any records on its own.

Records are created when a message reaches a **HubSpot delivery method** on your on-call calendar. The delivery method works in two modes:

1. **Default.** Add HubSpot without further configuration. Each delivered message finds the caller by **email**, then **phone**. ASC creates a Contact only when no match exists. It creates a **Ticket** in your portal's default pipeline and first stage.
2. **Configured.** Open the delivery method settings. Choose a **HubSpot Object**, ticket pipeline and stage, property mappings, and matching behavior.

{% hint style="info" %}
The default mode creates records only. It never updates existing records. To update a matching contact, company, or ticket, configure **Match Existing Records By** on the delivery method.
{% endhint %}

### Before you start

Before you start, confirm these basics:

* You can sign in as the **account owner** or a user with **integration access**.
* Your HubSpot user can install apps and grant permissions.
* The HubSpot integration is enabled for your ASC account.

{% hint style="warning" %}
If HubSpot is not available in Integrations, contact your account manager or email <success@answeringservicecare.com> to request access.
{% endhint %}

### Step 1: connect HubSpot

{% stepper %}
{% step %}

### Open Integrations

Open **Integrations** in the Client Portal and find the **HubSpot** card.

If it shows **Connect HubSpot**, you can start setup. If it already shows **HubSpot Connection**, HubSpot is already connected.
{% endstep %}

{% step %}

### Authorize the app

Select **Connect HubSpot**.

Sign in to HubSpot if prompted, and choose the HubSpot account you want to connect if you manage more than one.

Review the requested permissions, then authorize the app. ASC requests access to contacts, companies, tickets, and property definitions.
{% endstep %}

{% step %}

### Confirm the connection

ASC returns you to Integrations with a confirmation that HubSpot connected successfully.

The HubSpot card now shows the connected portal.
{% endstep %}
{% endstepper %}

### Step 2: add HubSpot as a delivery method

Add HubSpot to the on-call contact that should send messages to HubSpot. With no further setup, messages create a Contact when needed and a Ticket.

{% stepper %}
{% step %}

### Add the HubSpot delivery method

On the phone or on-call contact where you want HubSpot delivery, add a delivery method and choose **HubSpot**.
{% endstep %}

{% step %}

### Choose the HubSpot object

To use a different setup, select **Contact**, **Ticket**, or **Company**.
{% endstep %}

{% step %}

### Choose the pipeline and stage

For tickets, choose the **pipeline** and **stage**. New tickets then reach the correct workflow.
{% endstep %}

{% step %}

### Map properties

Map HubSpot properties to message details, including name, phone, email, company, and script answers. The picker includes standard and custom properties from your portal.
{% endstep %}

{% step %}

### Set matching and duplicate prevention

**Match Existing Records By** defaults to **Always create new**. Choose a property, such as email, to update a matching record.

Optionally, enable **Prevent Duplicate Records**. Choose an existing single-line text property to store the unique record key. ASC uses this key to update a record after a retried send.
{% endstep %}

{% step %}

### Save and test

Save the delivery method. Then send a test message through the same path. Confirm the record appears in HubSpot with the expected fields.
{% endstep %}
{% endstepper %}

### What data is shared

| Data                                    | Direction    | Notes                                                                                                        |
| --------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------ |
| Contacts                                | To HubSpot   | Matched by email or phone. Created only when no match exists. Updated only with a configured match property. |
| Tickets                                 | To HubSpot   | Created for messages delivered to HubSpot. Use the selected pipeline and stage, or your portal defaults.     |
| Companies                               | To HubSpot   | Created or updated only through a configured delivery method.                                                |
| Contact, ticket, and company properties | From HubSpot | Property definitions support mapping. Contacts and companies are searched for matching and linking.          |

Tickets are linked to an existing Contact matching the caller's email. They are also linked to an existing Company matching the email domain.

Nothing is deleted in HubSpot by this integration.

### If a sync fails

If HubSpot is briefly unavailable, ASC retries with increasing delays. A record may appear a few minutes later.

If the Integrations card says **HubSpot needs to be reconnected**, select **Connect HubSpot**. New-message delivery resumes after authorization.

### Disconnect HubSpot

**From ASC:** Open **Integrations**, select **Disconnect** on the HubSpot card, and confirm. New messages stop syncing immediately.

**From HubSpot:** Go to **Settings → Integrations → Connected Apps**. Find **Answering Service Care**, then select **Uninstall**.

{% hint style="warning" %}
Disconnecting or uninstalling stops future syncing. Existing contacts, companies, and tickets remain in HubSpot.
{% endhint %}

Reconnecting later resumes delivery for new messages.

### HubSpot FAQ

<details>

<summary>Does the integration update my existing contacts?</summary>

Not by default. ASC creates a Contact only when nothing matches by email or phone. To update records, configure **Match Existing Records By** on the delivery method.

</details>

<details>

<summary>Can I sync Company records?</summary>

Yes. Configure the delivery method with **Company** as the object type.

</details>

<details>

<summary>Which pipeline do tickets go to?</summary>

Tickets use the pipeline and stage selected on the delivery method. Without configuration, they use your portal's default pipeline and first stage.

</details>

<details>

<summary>Why don't I see new contacts or tickets in HubSpot?</summary>

Confirm a HubSpot delivery method is on the on-call path the message used. Confirm the Integrations card still shows connected. Reconnect it if prompted.

After a HubSpot outage, retries can delay records for a few minutes.

</details>

<details>

<summary>Does disconnecting or uninstalling delete anything in HubSpot?</summary>

No. Existing contacts, companies, and tickets remain in your account. Only future syncing stops.

</details>

### Related pages

* [Integrations](/docs/useful-resources/integrations.md): Review how HubSpot fits into ASC integration workflows.
* [Oncall calendar](/docs/app/client-portal/oncall-calendar.md): Manage delivery methods and escalation paths in the Client Portal.
* [Accounts and users](/docs/app/client-portal/accounts-and-users.md): Manage who can access and manage integrations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://answeringservicecare.com/docs/useful-resources/integrations/hubspot.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.