> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/integrations/hubspot.md).

# HubSpot

This article will give guide you through the setup and integration of HubSpot with Let's Get Digital.

## What data can be imported from HubSpot? <a href="#what-data-can-be-imported-from-eventbrite" id="what-data-can-be-imported-from-eventbrite"></a>

It is possible to import the following fields from HubSpot to Let's Get Digital:

* **First name**
* **Last name**
* **Email**
* **Company name**
* **Company role**
* **Title**
* **Privacy**
* **Password**
* **Phone number**
* **Description**
* **LinkedIn Profile URL**
* **User tags**

### Activate the HubSpot Integration <a href="#activate-the-eventbrite-integration" id="activate-the-eventbrite-integration"></a>

1. Open the Admin panel
2. Navigation to Settings -> Integrations
3. Click on New integration -> Choose HubSpot
4. Give integration a name
5. Click on Authenticate HubSpot -> Login to your HubSpot account
6. Select the form you want to connect
7. Save changes
8. Map your data fields (email is the minimum requirement)
9. Select at is active -> Active
10. Click on Import -> Start import

{% hint style="danger" %}
The integration will automatically update upto 10 weeks before the event start date and until 1 week post event. Outside of this timeframe you will need to manually click on the Import button from the integration.&#x20;
{% endhint %}

<br>


---

# 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://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/integrations/hubspot.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.