> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/integrations/marketing-automation/hubspot.md).
# HubSpot
HockeyStack's HubSpot integration pulls your marketing automation data into HockeyStack and connects it with the rest of your customer data. This includes Marketing Emails and Form Submissions.
## How It Works
When you integrate HubSpot, HockeyStack pulls certain actions and properties from it. Each action comes with action properties that give more information about it.
For a list of the objects we pull from HubSpot marketing automation, see [HubSpot Pulled Objects List ](/integrations/marketing-automation/hubspot/hubspot-pulled-actions-list.md).
## Caveats
* We pull the data from HubSpot on a daily basis.
* If you're using both Salesforce (as CRM) and HubSpot (as marketing automation platform), HockeyStack doesn't pull deal object from HubSpot (not to duplicate Salesforce data). It's important to connect Salesforce to HockeyStack first, in this case.
---
# 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.hockeystack.com/integrations/marketing-automation/hubspot.md?ask=&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.