> 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.md). # Integrations RepX connects to the tools your revenue team already runs on, so the leads it qualifies and the signals from every conversation land where your team already works. RepX natively integrates with HubSpot, Salesforce, Slack and Zapier. You can connect any integration from **Settings > Integrations**. ### 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 activities** 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 activity, 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 writes an activity to the record in HubSpot to capture: * If a **lead submitted their email** or **booked a meeting** during the conversation * **A conversation summary**, along with its **duration**, **end time**, a **link to the full conversation** in RepX. #### 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 | ### Slack With the Slack integration, your team can get notified in Slack as conversations happen.\ \ When you setup a Slack integrat, you can choose channels that should receive notifications when visitors have conversations on your website through RepX. After each conversation, RepX posts a notification that includes: * **The topics the visitor discussed**, so your team can see at a glance what the conversation was about. * **A short summary** of the conversation, for quick context without opening anything. * **A link to view the full conversation**, for when someone wants the complete picture. If the lead matches an owner in HubSpot, RepX tags that owner directly in the Slack notification, so the right person can stay on top of what their lead was interested in. --- # 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.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.