> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/repx-chat/hubspot.md).
# HubSpot
RepX keeps HubSpot in sync with what happens when your website visitors have conversations, so that your CRM is up-to-date with real buying interest. \
\
When you integrate with HubSpot, RepX
* **identifies known leads from HubSpot** when it loads
* **creates and updates lead and contact records** when visitors submit their emails
* **logs conversations as notes** in the lead and contact records
#### Conversation transcript as notes
When a conversation ends, and if activity logging is enabled, **RepX logs the full conversation transcript as a note** on the record in HubSpot. \
\
Your team doesn't have to leave the CRM or open RepX to read what was said - the note carries the entire conversation, along with the attributes RepX extracted from it.
Each note includes:
* If a **lead submitted their email** or **booked a meeting** during the conversation
* **the full conversation transcript**, message by message, exactly as it happened.
* **a conversation summary**, for when someone wants the gist without reading the whole thing.
* **the topics discussed** during the conversation.
* **conversation related metadata**, including the conversation's **duration** and **end time** and
* **a link to the full conversation** in RepX.
{% hint style="info" %}
RepX writes a standard set of conversation attributes into HubSpot properties and notes. If you want a specific [conversation signal](/repx-chat/setting-up-repx/conversation-variables.md) - like `pain points` or `migration size` - to land in a specific HubSpot field, push it through the [Zapier integration](/repx-chat/zapier.md) instead.
{% endhint %}
#### RepX properties available in HubSpot
Besides adding conversation transcripts as notes, RepX also creates and updates these properties with useful information that might help you prioritize leads. The properties include:
| Property name | Applies to (on HubSpot) | Description of the property | Data type |
| --------------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------- |
| **Storylane RepX total messages count** | Company, Lead and Contact objects | Total messages exchanged across RepX conversations by that contact or lead. At the company level, we share the total messages across all conversations exchanged by all leads and contacts associated with that company. | Number |
| **Storylane RepX last conversation at** | Company, Lead and Contact objects | Timestamp of the most recent RepX conversation with that lead or contact. At the company level, we store the timestamp of the most recent conversation had by any of the leads or contacts. | DateTime |
| **Storylane RepX conversation topics** | Company, Lead and Contact objects | List of topics discussed across RepX conversations by a lead or contact. At the company level, we store a cumulative list of topics discussed by all leads or contacts that are associated with that company. | String |
The Demo Suite already pushes information into several HubSpot properties [as listed here](https://docs.storylane.io/integrations/integrations-and-data-flow/hubspot). \
\
If you're already using the Demo Suite with the HubSpot integration and you connect RepX to HubSpot as well, the following properties will start including data based on RepX conversations:
| Property name | Applies to (on HubSpot) | Description of the property | Data type |
| --------------------------- | --------------------------------- | -------------------------------------------------------------------------------------- | --------- |
| **Storylane Sessions** | Lead, contact and company objects | Total number of sessions (includes Demo, Hubs and RepX sessions) | Number |
| **Storylane Buying Intent** | Lead, contact and company objects | Buying intent calculated based on activity on Demos, Hubs and RepX conversation topics | String |
| **Storylane Lead Source** | Lead and contact objects | How the lead was sourced (e.g. Direct, Nurtured, Attributed) | String |
| **Storylane CTA Clicked** | Lead and contact objects | CTA URL clicked on Demos or from RepX Chat | String |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.storylane.io/repx-chat/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 `build a script that syncs our docs to a CMS` 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.