> 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.md).

# HubSpot

Request customer recordings, send video replies, and share calls and booking links from HubSpot.

Bring visual context into your HubSpot support workflow. Request a screen recording when a customer reports an issue, explain a solution with your own video, reuse a library recording, or share a video call or booking link.

## Choose your workflow

| I want to…                                            | Guide                                                                                           |
| ----------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Connect Screendesk and add the sidebar card           | [Install and set up](/helpdesk-integrations/hubspot/install-and-set-up.md)                      |
| Ask a customer to show an issue on an existing ticket | [Request from the sidebar](/helpdesk-integrations/hubspot/request-via-sidebar.md)               |
| Save the wording agents use for requests              | [Use snippets](/helpdesk-integrations/hubspot/snippets.md)                                      |
| Offer a recording alongside a support form            | [Forms](/helpdesk-integrations/hubspot/forms.md)                                                |
| Include a recording request in an acknowledgment      | [Automated emails](/helpdesk-integrations/hubspot/automated-emails.md)                          |
| Explain a solution or reuse a tutorial                | [Send and share recordings](/helpdesk-integrations/hubspot/send-and-share-recordings.md)        |
| Work through an issue together                        | [Video calls](/helpdesk-integrations/hubspot/video-calls.md)                                    |
| Let a customer choose a meeting time                  | [Booking links](/helpdesk-integrations/hubspot/booking-links.md)                                |
| Compare tickets that received recordings              | [Analytics and ticket property](/helpdesk-integrations/hubspot/analytics.md) — upcoming feature |

\| Request recordings automatically during a chat | [Chatbots and Breeze Customer Agent](/helpdesk-integrations/hubspot/chatbots-and-agents.md) — development preview | | Set up a rule-based recording flow | [Rule-based chatflows](/helpdesk-integrations/hubspot/rule-based-chatflows.md) — development preview | | Configure an AI agent to request and check recordings | [Breeze Customer Agent](/helpdesk-integrations/hubspot/breeze-customer-agent.md) — development preview |

## What comes back to HubSpot?

When a customer submits a recording requested from a ticket's Screendesk sidebar, Screendesk adds a viewing link as a note on that ticket. The HubSpot connection must remain active and the ticket must still exist.

Recorder links use a source parameter that selects the submission behavior:

| Flow                                             | Recorder parameters            | Result                                                                                                |
| ------------------------------------------------ | ------------------------------ | ----------------------------------------------------------------------------------------------------- |
| Request for an existing HubSpot ticket           | `src=rrht` and `hid=TICKET_ID` | Adds a note to that ticket when the customer submits                                                  |
| Form integration on a page you control           | `src=wf`                       | Sends the submitted recording UUID to the popup opener; your form integration must save it in HubSpot |
| General request used in a fixed snippet or email | `src=rria`                     | Collects the recording in Screendesk; an agent matches it to the support request                      |

Preserve the source in generated links. A source is not an arbitrary campaign label. Changing it alone cannot identify a future ticket or populate a HubSpot form field. See each guide for the required handoff.

The upcoming [chatbot integration](/helpdesk-integrations/hubspot/chatbots-and-agents.md) creates signed, per-request recording links using a dedicated workspace token. Its destination is saved when the request is created. Follow that guide rather than assembling a chatbot link from these legacy source parameters.

## Before you start

An admin connects the workspace and adds the card to the Help Desk layout. Agents need an active Screendesk membership using their HubSpot email address. Calls and scheduling depend on the workspace's enabled features and the user's permissions.

The guides describe the installed sidebar. For screenshots of the upcoming navigation, see [Sidebar design preview](/helpdesk-integrations/hubspot/sidebar-preview.md). That page shows a local test version, not a release announcement.

[Troubleshooting](/helpdesk-integrations/hubspot/troubleshooting.md)


---

# 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.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.