> For the complete documentation index, see [llms.txt](https://docs.pulseinsights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulseinsights.com/integrations/integrations-overview/hubspot.md).
# Hubspot
## What the integration accomplishes
This integration enables you to take responses from Pulse Insights and insert them into the appropriate user's Hubspot record so you can personalize future marketing and servicing communications and experiences.
For example you might:
* Capture a shopping preference and use that to personalize marketing emails
* Capture a communication channel preference and then use that utilize the preferred channel
* Capture data such as location or birthday to trigger or personalize offer emails
* Capture feedback like satisfaction to inform models.
* Capture email feedback like email relevance to suppress disinterested audiences
{% hint style="info" %}
Pulse Insights will get the data into Hubspot. From there, it will be up to you to leverage that data to provide superior service and marketing.
{% endhint %}
## Integration Flow
## Prerequisites
Email links that capture user feedback will need to ingest the Hubspot Contact ID in order to update the appropriate record in Hubspot. You can ingest the Contact ID by appending the following to the Pulse Insights links.
```
&hscid={{contact.hs_object_id}}
```
Learn more about [link creation here](/implementing-pulse-insights-dev/implementing-in-email.md).
## Inputs we'll need from you
In order for us to configure the integration, we'll ask you tell us how you'd like it to work via [**this form**](https://www.pulseinsights.com/client-forms/submit-custom-integration-instructions).
* Endpoint details
* Access Token (if this changes frequently, we will need to know updated Token to avoid interruption in data send)
* Object Type (e.g. "Contacts) and Group (e.g. Contact Activity)
* UserID (often contact.id). Please see more details on Client Key [here](/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/client-key.md).
* Property Name/Label of where the data will be hosted
* Field Type (e.g. single-line text or Number)
* Frequency (batch or near real-time)
* Update or create
---
# 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.pulseinsights.com/integrations/integrations-overview/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.
