> ## Documentation Index
> Fetch the complete documentation index at: https://help.gowindmill.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HubSpot

> Connect HubSpot to Windmill to sync deals, contacts, and pipeline activity so revenue context appears in recaps, 1:1 prep, and performance review summaries.

## Benefits of connecting HubSpot to Windmill

Connecting HubSpot to Windmill ensures customer-facing work — from pipeline progress to relationship-building — is reflected automatically in performance conversations.

* Captures deal movement and account work without requiring reps to “self-report”
* Gives managers coaching context grounded in real customer activity
* Ensures employees get credit for behind-the-scenes relationship work
* Reduces time spent preparing for reviews, calibrations, and promotions
* Makes performance evaluations more objective and tied to measurable outcomes

Windmill turns ongoing sales and success activity from HubSpot into structured context for growth, recognition, and fair evaluation.

## Connected data

When connected, Windmill securely reads *high-signal* activity from HubSpot:

| Data Type                                | How Windmill Uses It                                  |
| ---------------------------------------- | ----------------------------------------------------- |
| Deals, stages, and pipeline progression  | Displays momentum and conversion patterns over time   |
| Account and contact ownership            | Attributes customer work to the correct employee      |
| Meeting + call activity metadata         | Shows engagement, responsiveness, and consistency     |
| Notes and logged interactions            | Adds qualitative coaching context to 1:1s and reviews |
| Emails (metadata only, not full content) | Surfaces follow-through and communication patterns    |

> Windmill only syncs the fields required to provide accurate performance context — *not your full CRM export.*

<Info>
  Learn more about [how Windmill syncs deals from HubSpot](/data/deals).
</Info>

## Permissions

Windmill requests **read-only**, scoped access via HubSpot OAuth.

| Permission                                             | Purpose                                                                    |
| ------------------------------------------------------ | -------------------------------------------------------------------------- |
| Read deal + pipeline metadata                          | To reflect progress, contribution, and momentum in performance discussions |
| Read account/contact ownership info                    | To map customer work to the correct employee profiles                      |
| Read activity/event metadata (meetings, calls, emails) | To show effort, engagement, and follow-through patterns                    |
| **No write access**                                    | Windmill never modifies deals, notes, contacts, or records in HubSpot      |
| **Scoped to selected pipelines / objects**             | You maintain full control over what is shared and synced                   |

> Windmill follows a **least-privilege access model** — it requests only what’s necessary for coaching & performance insight.

## FAQs

<AccordionGroup>
  <Accordion title="Does Windmill sync full email content?">
    No. Windmill only syncs metadata (e.g., that a follow-up occurred), not message bodies.
  </Accordion>

  <Accordion title="Does Windmill write anything back into HubSpot?">
    No. The integration is strictly read-only.
  </Accordion>

  <Accordion title="How often does Windmill sync data?">
    Continuously. Updates appear in Windmill shortly after they occur in HubSpot.
  </Accordion>

  <Accordion title="Is this integration secure?">
    Yes. All data is encrypted in transit and at rest. Windmill meets SOC 2 security standards and tracks only necessary activity-level context.
  </Accordion>

  <Accordion title="What if a rep changes roles or leaves?">
    Their historical contributions remain for context, but Windmill stops attributing new activity once they're deactivated.
  </Accordion>
</AccordionGroup>

***