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

# HubSpot

Scout reads your HubSpot to understand your pipeline, and updates it as you when you ask.

Scout reads your HubSpot to understand your pipeline, who you've won and lost and why, and which deals need you. When you ask, it updates HubSpot as you.

## Connect

HubSpot connects in two steps:

1. **Your company's HubSpot connects to Spara once.** Whoever manages integrations for your team does this; if you signed up on your own, that's you. Scout's card offers it, or do it from your [**Scout**](https://app.spara.co/scout) page under **Organization**.
2. **You connect your own HubSpot login**, from Scout's card or from your Scout page under **Accounts**.

Scout acts under your own HubSpot permissions. What you can't see or change in HubSpot, Scout can't either.

## What Scout does with it

* **Reads your pipeline**: contacts, companies, deals and their stakeholders, owners, pipelines, lists, sequences and engagement timelines.
* **Updates records when you ask**: logs a note, adds a task, updates a contact, as you. Say what you want changed in conversation, and Scout does it.
* **Brings you changes from jobs.** A job that runs on its own doesn't write to HubSpot. When it would, it delivers the change for you to apply.

{% hint style="info" %}
Your Spara team's HubSpot connection also powers Spara's CRM sync for your inbound leads. See [HubSpot CRM](https://docs.spara.com/integrations/crm-integrations/hubspot-crm) for how that works.
{% endhint %}


---

# 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.spara.com/scout/connections/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.