> 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/integrations/integrations-and-data-flow/hubspot/hubspot-integration-features.md).

# HubSpot Integration Features

There is quite a lot you can do within HubSpot using Storylane data (workflows, reporting, email campaigns, etc.) See more below! 👇

{% @storylane/embed subdomain="app" linkValue="m27lvdr8tnbk" url="<https://app.storylane.io/share/m27lvdr8tnbk>" %}

#### Activity Tracking

* Open a contact
* Navigate to Activity tab
* Include Storylane in “Filter Activity”

#### Email Campaign&#x20;

* Navigate to your demo
* Click Share > Email Campaign
* Copy the HubSpot link
* Add this link to any element in your HubSpot email
* **⭐️ We highly recommend exporting your demo as a GIF, adding to HubSpot email, and linking to the HubSpot email campaign demo link.**
* Review and send your email. Each recipient will receive a personalized link with their email in the URL, which will send analytics to HubSpot.

#### Workflows

* Create a new Workflow from Scratch
* Select “Contact-based”
* Set up your triggers. Search “Storylane” in Filter Categories to see what is available.
* Next, choose an Action. What happens when the trigger’s criteria are met? Email the contact owner. Send a Slack notification?
* Complete the rest of the workflow to your liking, and publish.

#### Forms&#x20;

* You can add a lead form within your demo by creating one in HubSpot and embedding it in a Lead Form element in Storylane. **Keep your embedded lead form short and sweet!**
* If you require more than a few fields for your form, we recommend linking the last step of your demo to an external lead form. Just add a CTA and direct it to the correct URL.

#### Reports&#x20;

* Create a new Single Object report
* Select "Contacts" as the object
* Add a Contact Property - search “demo” to see a list of Storylane properties (i.e “Storylane Demo Name”)
* Add a filter (i.e “Storylane Demo Complete (%))
* Select your chart type, and view the results!&#x20;

Get a clear view of your marketing and sales impact with Storylane demos in HubSpot. Dive into the demo below to begin. 👇

{% @storylane/embed subdomain="app" linkValue="p5hrjpexba4i" url="<https://app.storylane.io/share/p5hrjpexba4i>" %}

#### How to Install & Connect Storylane via HubSpot Marketplace?

Another way to connect Hubspot to Storylane is via Hubspot Marketplace, follow the steps below:

1. Go to the [**HubSpot Marketplace**.](https://app.hubspot.com/ecosystem/20574478/marketplace/apps)​
2. Search for "Storylane" and select it from the dropdown results.
3. Install the app.
4. ​[Log in to Storylane](https://app.storylane.io/login) and navigate to **Settings > Integrations**.
5. Click “**Connect**” on the HubSpot integration to complete the setup. Leads from published demos will sync to HubSpot Contacts, with analytics (custom fields and timeline activities) updating within 5 minutes.


---

# 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/integrations/integrations-and-data-flow/hubspot/hubspot-integration-features.md?ask=<question>&goal=<endgoal>
```

`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.