> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/helpdesk-integrations/hubspot/install-and-set-up.md).

# Install and set up

Connect HubSpot, add the Screendesk card to your help desk sidebar, and choose its settings.

You need admin access to the Screendesk workspace and permission to install apps in HubSpot.

{% embed url="<https://app.screendesk.io/recordings/e4288fa3-6dd2-4247-8e1b-1f203175e938>" %}

1. In Screendesk, open **Settings → Integrations**. Under **Helpdesk**, find **HubSpot** and click **Connect**.
2. HubSpot asks you to **Choose an account**: pick the account and click **Choose Account**, then approve access. You're returned to Integrations, and the HubSpot card says **Connected**.
3. In HubSpot, click the settings icon and go to **Tools → Inbox & Help Desk → Help Desk**. Under **Help desk customization**, click **Sidebar customization**.

   <figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2Fis7sH6L7siIZL9VbNYWL%2Fhubspot-sidebar-customization.png?alt=media" alt="Customize the Sidebar in HubSpot&#x27;s help desk settings"><figcaption></figcaption></figure>
4. Click the view your team uses, such as **Default view**. In the layout editor, click **+** (**Add card**) where you want the card, open **App cards** and click **Add** on **Screendesk**. Then click **Save and exit**.

   <figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2Frly8fxVRis8q7xwGbKdE%2Fhubspot-card-library.png?alt=media" alt="The Screendesk card under App cards, added"><figcaption></figcaption></figure>
5. Invite your agents to the Screendesk workspace with the same email address they use in HubSpot. Any role except **Watch only** can use the card.
6. Open a test ticket, find **Screendesk** in the sidebar and click **Get started**, then **Request a recording**. If HubSpot says the link is copied, setup is done.

## Settings

Click **Configure** on the HubSpot card in **Settings → Integrations**. The settings follow the way a recording travels.

**Ask from a ticket**

* **Recordings in the card**: what agents see under the actions, the customer's recordings (**From this customer**) or the ticket's (**On this ticket**).

**Let customers record on their own**

* **Where customers record**: shown when your workspace has websites with the Screendesk snippet. It sets where the link below opens.
* **Snippets, emails and forms**: the link for [snippets](https://docs.screendesk.io/helpdesk-integrations/hubspot/snippets.md), [marketing emails](https://docs.screendesk.io/helpdesk-integrations/hubspot/marketing-emails.md) and [forms](https://docs.screendesk.io/helpdesk-integrations/hubspot/forms.md).
* **Chatbot and Breeze token**: for a [HubSpot chatbot or Breeze Customer Agent](https://docs.screendesk.io/helpdesk-integrations/hubspot/chatbots-and-agents.md).

**When a recording arrives**

It's added to the ticket as a note and reopens a closed ticket.

* **Mark the tickets**: ticks values on a **Screendesk activity** ticket property that Screendesk adds to HubSpot, such as **Recording requested** and **Recording received**. Use it to filter views, run workflows and report on tickets that got a recording. See [Analytics](https://docs.screendesk.io/helpdesk-integrations/hubspot/analytics.md).

If the sheet says **Allow chat conversations**, reconnect HubSpot and allow conversations, so a recording asked for in a chat comes back in that chat and AI resolution can read the ticket's messages.

## Disconnect

In **Settings → Integrations**, click **Disconnect** on the HubSpot card. Screendesk loses access to your HubSpot account, and new recordings no longer add notes to tickets.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/helpdesk-integrations/hubspot/install-and-set-up.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
