> 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/integrations/hubspot.md). # HubSpot RepX keeps HubSpot in sync with what happens in conversation, so your CRM reflects real buying interest. RepX * **Identifies known leads from HubSpot** when it loads * **Creates or updates lead and contact records** when visitors submit their emails * **Logs conversations as notes** in the lead and contact records When RepX loads on a webpage, it checks whether the visitor is already a known lead in HubSpot. That check decides whether RepX creates a new record or updates the one that already exists, so you don't end up with duplicates. Every conversation attaches to the right record on HubSpot. * RepX creates a new lead on HubSpot and logs the conversation as an note, if the email they submit during the conversation was not associated with any record in the CRM. * If the email was already associated with a lead or contact in your HubSpot CRM, RepX updates the existing record with an activity. #### Activities logged in HubSpot When a conversation ends, and if activity logging is enabled, **RepX logs the full conversation 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 conversation itself, 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 attributes**, including the conversation's **duration** and **end time**, and whether the **lead submitted their email** or **booked a meeting**. * **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/conversation-signals.md) - like `pain points` or `migration size` - to land in a specific HubSpot field, push it through the [Zapier integration](/repx/integrations/zapier.md) instead. {% endhint %} #### Properties available in HubSpot | 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.storylane.io/repx/integrations/hubspot.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.