> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/integrations/calendar-integrations/hubspot-calendar.md).

# HubSpot (Calendar)

How to integrate with HubSpot calendars.

### Data flows

While HubSpot allows limited pre-population of meeting form fields (email, first name, and last name), it does not provide access to read or write calendar events outside of its own interface, and therefore offers more restricted integration support compared to specialized scheduling providers.

<table data-full-width="true"><thead><tr><th>Spara can prepopulate...</th><th>Spara can read from submitted calendar...</th><th>Integration Notes</th></tr></thead><tbody><tr><td><ul><li>Email</li><li>First name</li><li>Last name</li></ul></td><td><ul><li>Email</li><li>First name</li><li>Last name</li></ul></td><td>Spara will read email address and other fields after a meeting has been scheduled.</td></tr></tbody></table>

### Implementation

{% hint style="info" %}
How Spara's AI uses your HubSpot calendar must be configured by Spara internally. Please contact your customer service representative to get started.
{% endhint %}

HubSpot calendars are embedded as an iFrame within Spara's interface. All HubSpot UX can be used by your lead in this format.

Spara requires a HubSpot calendar URL , for example:

```yaml
https://meetings-na2.hubspot.com/<name>
```


---

# 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.spara.com/integrations/calendar-integrations/hubspot-calendar.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.
