> 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/how-to-build-workflows-with-demo-engagement-data.md).

# How to Build Workflows with Demo Engagement Data

Turn demo engagement into automated follow-up — re-engage, nurture, and qualify leads based on how prospects actually interact with your demos.

Once Storylane is connected to HubSpot, every demo and Hub session syncs engagement data onto your contact records. Use these signals to trigger workflows that reach each prospect with the right message at the right moment.

***

**💡 The signals you can build on**

A few synced fields do most of the work as workflow triggers:

* **Storylane Buying Intent** — engagement-based level: **Low / Medium / High**. The fastest way to segment, no setup required.
* **Storylane Demo Complete (%)** — for finer thresholds than intent alone.
* **Storylane CTA Clicked** — a clicked CTA (e.g. "Book a call") is a strong hand-raise signal.

Time spent, session count, and lead source sync too — see the full list of synced fields.

***

**👥 Group contacts by engagement tier**

Map every contact to a tier, then build one workflow per tier. 

**Buying Intent** does this out of the box — layer in **Demo Complete (%)** for tighter control.

| Tier          | Signal                                     | Play                                  |
| ------------- | ------------------------------------------ | ------------------------------------- |
| 🔴 **Low**    | Intent = Low *(or < 40%)*                  | Short nurture — lead with value props |
| 🟡 **Medium** | Intent = Medium *(or 40–89%)*              | Send use cases + customer stories     |
| 🟢 **High**   | Intent = High *(or > 90%, or a CTA click)* | Immediate follow-up + notify sales    |
|               |                                            |                                       |

**⚡ Three workflows to start with**

Each workflow **enrolls** the right contacts, **suppresses** anyone who's moved to a higher tier, and runs one clear action.

* **Re-engagement (Low):** wait 2–3 days, then send a value-prop email. *Suppress if intent is High or a CTA was clicked.*
* **Nurture (Medium):** send use cases or case studies over a short cadence. *Suppress if intent is High.*
* **High intent / Completion:** send a next-steps email within minutes **and** alert the contact owner. *Suppress if follow-up was already sent or an opportunity is open.*

***

**🧹 Keep your messaging clean**

{% hint style="info" %}
**The golden rule:** when a contact's engagement increases, advance them to the highest tier they qualify for — and never send lower-tier messaging to a more engaged contact. Someone who viewed 20% last week and completed 100% today is a hot prospect, not a re-engagement target.
{% endhint %}

Suppression is what makes this work — it stops a contact from qualifying for two workflows at once and receiving conflicting emails. To avoid repeats, set a custom property (e.g. *Completion email sent = Yes*) as a workflow action and suppress on it.

***

**🛠️ Make it your own**

These are starting points — mix and match signals to fit your funnel. Alert sales the moment a target account hits High intent, branch by lead source, or trigger a step when a viewer returns for a second session.

{% hint style="info" %}
Buying Intent thresholds can be tuned to your use case — [reach out to our team](mailto:support@storylane.io) to customize what counts as Low, Medium, or High.
{% endhint %}


---

# 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:

```
GET https://docs.storylane.io/integrations/integrations-and-data-flow/hubspot/how-to-build-workflows-with-demo-engagement-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.