> 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-updates/july-14-2026.md).

# July 14, 2026

Hey Storylaners! RepX talks to HubSpot now. Every conversation your agent has lands on the right lead and company record - transcript, summary and a lot more.

### 🤝 HubSpot integration

RepX now keeps HubSpot in sync based on the conversations your RepX agent is having on your website. Your sales team can now get all the context they need ahead of getting on calls with leads who engaged with your RepX agent. \
\
When a visitor submits their email, RepX checks HubSpot first. If the **email already belongs to a lead or contact**, RepX updates that record. If it doesn't, RepX creates one. 

The entire conversation syncs into a **note** in the lead and contact timeline. Each note contains

* the **full transcript**, message by message
* a **summary**, for when someone wants the gist
* the **topics** discussed
* **conversation duration and end time**
* **if a CTA was clicked**, and which one
* a **link to the full conversation** in RepX

The transcript also carries what RepX presented - it surfaces<br>

* if a demo, image or video was shown - if so, which one
* if a meeting link was suggested and which one&#x20;

\
RepX also updates several properties in HubSpot. You can find those [here](https://docs.storylane.io/repx-chat/integrations/hubspot).&#x20;


---

# 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.storylane.io/repx-updates/july-14-2026.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.