How to integrate Hubspot with Power BI

Learn how to quickly and efficiently connect Hubspot with Power BI for smooth data access.

Read and write HubSpot data effortlessly. Integrate, manage, and automate contacts, companies, deals, and tickets — almost no coding required. You can do it all using the high-performance Hubspot ODBC Driver for Power BI (often referred to as the Hubspot Connector). We'll walk you through the entire setup.

Ready to dive in? Download the product to jump right in, or follow the step-by-step guide below to see how it works.

Hubspot ODBC Driver Powering this integration

High performance
Bidirectional
Low-code / No-code
Easy to use

Built on the ZappySys API Driver, the Hubspot ODBC Driver is a high-performance, low-code / no-code solution. It enables you to connect to Hubspot data without any coding right in your SQL Server, or any ODBC/JDBC application. Part of the ODBC PowerPack.

Documentation

Video Tutorial

This video covers the following topics and more, so please watch carefully. After watching the video, follow the steps outlined in this article:

How to download and install the required PowerPack for Hubspot integration in Power BI
How to configure the connection for Hubspot
Features of the ZappySys API Driver (Authentication / Query Language / Examples / Driver UI)
How to use the Hubspot in Power BI

Create data source using Hubspot ODBC Driver

Step-by-step instructions

To get data from Hubspot using Power BI, we first need to create an ODBC data source. We will later read this data in Power BI. Perform these steps:

Download and install ODBC PowerPack (if you haven't already).
Search for odbc and open the ODBC Data Sources (64-bit):
Create a User data source (User DSN) based on the ZappySys API Driver driver:

ZappySys API Driver
- Create and use a User DSN if the client application runs under a User Account. This is the ideal option at design time (e.g., when developing in Visual Studio). Use it for both types of applications (64-bit and 32-bit).
- Create and use a System DSN if the client application runs under a System Account (e.g., as a Windows Service). This is usually the required option in a production environment. If your Windows Service is a 32-bit application, you must use the 32-bit ODBC Data Source Administrator to configure this
When deployed to production, Power BI runs under a Service Account. Therefore, for the production environment, you must create and use a System DSN.
When the Configuration window appears give your data source a name if you haven't done that already, then select "Hubspot" from the list of Popular Connectors. If "Hubspot" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

HubspotDSN

Hubspot

Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

Private app (Static Access Token)

Hubspot authentication

Private apps allow you to use HubSpot's APIs to access specific data from your HubSpot account. You can authorize what each private app can request or change in your account, which will generate an access token that's unique to your app. [API reference]

Follow these instructions to create a Private app in HubSpot and configure HubSpot authentication in SSIS package or ODBC data source:

First of all, go to HubSpot portal.
Then click Data Management option on the left and then hit Integrations menu item:
Move on by clicking Private Apps menu item and then click Create a private app button to create one:
Then continue by following the instructions on HubSpot Docs.
Once you create an app, go to SSIS package or ODBC data source and in Private App authentication set these parameters:
- For AccessToken field use Access token value from the Private app configuration in HubSpot.
Done! Now you are ready to use HubSpot Connector!

API Connection Manager configuration

Just perform these simple steps to finish authentication configuration:

Set Authentication Type to Private app (Static Access Token) [Http]
Optional step. Modify API Base URL if needed (in most cases default will work).
Fill in all the required parameters and set optional parameters if needed.
Finally, hit OK button:

HubspotDSN

Hubspot

Private app (Static Access Token) [Http]

https://api.hubapi.com

Required Parameters
AccessToken	Fill-in the parameter...
Optional Parameters
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

Public app

Hubspot authentication

In HubSpot, a public app is a type of integration that can be installed on customer accounts or listed on the App Marketplace. It requires authentication via OAuth. Once a user installs your app on their HubSpot account, you’ll be able to make API calls to that account using an OAuth access token. [API reference]

Follow these instructions to create a Public app in HubSpot and configure HubSpot authentication in SSIS package or ODBC data source:

First of all, if you don't have HubSpot Developer's account, register one.
Go to HubSpot and select your Developer account.
Click Apps on the left hand side and then click Create app button to create a Public app:
Then continue by following the instructions in HubSpot Docs.
NOTE: If you don't have a working Redirect URL, you can use https://zappysys.com/oauth (it's safe).

Once you create an app, go to SSIS package or ODBC data source and in Public app authentication set these parameters (use values from your Public app configuration in HubSpot):

For ClientId field use Client ID value.
For ClientSecret field use Client secret value.

For Scope field use Scopes values, e.g.:

accounting
tickets
files

crm.lists.read
crm.lists.write

crm.objects.contacts.read
crm.objects.contacts.write
crm.schemas.contacts.read

crm.objects.custom.read
crm.objects.custom.write
crm.schemas.custom.read

crm.objects.companies.read
crm.objects.companies.write
crm.schemas.companies.read

crm.objects.deals.read
crm.objects.deals.write
crm.schemas.deals.read

crm.objects.quotes.read
crm.objects.quotes.write
crm.schemas.quotes.read

crm.objects.line_items.read
crm.objects.line_items.write
crm.schemas.line_items.read

NOTE: You can use other scopes too, but they must match the scopes defined in your Public app.

For ReturnUrl field use one of Redirect URLs.

When you are done with that, click Generate Token button to generate Access and Refresh Tokens.
Done! Now you are ready to use HubSpot Connector!

API Connection Manager configuration

Just perform these simple steps to finish authentication configuration:

Set Authentication Type to Public app [OAuth]
Optional step. Modify API Base URL if needed (in most cases default will work).
Fill in all the required parameters and set optional parameters if needed.
Press Generate Token button to generate the tokens.
Finally, hit OK button:

HubspotDSN

Hubspot

Public app [OAuth]

https://api.hubapi.com

Required Parameters
UseCustomApp	Fill-in the parameter...
Scope (Must Match with App Scopes)	Fill-in the parameter...
Optional Parameters
Client ID
Client Secret
ReturnUrl
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

Developer API key (Deprecated)

Hubspot authentication

Deprecated authentication method. Use [Private app] instead. [API reference]

Using HubSpot API key is deprecated method for authentication. Use Private app authentication instead. If you still need one, then follow these instructions to get HubSpot API key:

First of all, if you don't have HubSpot Developer's account, register one.
Go to HubSpot and select your Developer account.
Click Apps on the left hand side and then click Get HubSpot API key button to get one:
When a popup appears, click Show Key button and then hit Copy button to copy API key:
Once copy the API key, go to SSIS package or ODBC data source and use it in API Key authentication configuration:
- Paste it in ApiKey parameter field.
Done! Now you are ready to use HubSpot Connector!

API Connection Manager configuration

Just perform these simple steps to finish authentication configuration:

Set Authentication Type to Developer API key (Deprecated) [Http]
Optional step. Modify API Base URL if needed (in most cases default will work).
Fill in all the required parameters and set optional parameters if needed.
Finally, hit OK button:

HubspotDSN

Hubspot

Developer API key (Deprecated) [Http]

https://api.hubapi.com

Required Parameters
ApiKey	Fill-in the parameter...
Optional Parameters
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

Once the data source connection has been configured, it's time to configure the SQL query. Select the Preview tab and then click Query Builder button to configure the SQL query:

ZappySys API Driver - Hubspot

Read and write HubSpot data effortlessly. Integrate, manage, and automate contacts, companies, deals, and tickets — almost no coding required.

HubspotDSN
Start by selecting the Table or Endpoint you are interested in and then configure the parameters. This will generate a query that we will use in Power BI to retrieve data from Hubspot. Hit OK button to use this query in the next step.
```
SELECT * FROM Companies
-- WHERE Id=123
```
Some parameters configured in this window will be passed to the Hubspot API, e.g. filtering parameters. It means that filtering will be done on the server side (instead of the client side), enabling you to get only the meaningful data much faster.
Now hit Preview Data button to preview the data using the generated SQL query. If you are satisfied with the result, use this query in Power BI:
ZappySys API Driver - Hubspot

Read and write HubSpot data effortlessly. Integrate, manage, and automate contacts, companies, deals, and tickets — almost no coding required.

HubspotDSN
```
SELECT * FROM Companies
-- WHERE Id=123
```
You can also access data quickly from the tables dropdown by selecting <Select table>.

A WHERE clause, LIMIT keyword will be performed on the client side, meaning that the whole result set will be retrieved from the Hubspot API first, and only then the filtering will be applied to the data. If possible, it is recommended to use parameters in Query Builder to filter the data on the server side (in Hubspot servers).
Click OK to finish creating the data source.

Video Tutorial

Connect to Hubspot data in Power BI

Import data from a table or view

Once you open Power BI Desktop click Get Data to get data from ODBC:
A window opens, and then search for "odbc" to get data from ODBC data source:
Another window opens and asks to select a Data Source we already created. Choose HubspotDSN and continue:

HubspotDSN
Most likely, you will be asked to authenticate to a newly created DSN. Just select Windows authentication option together with Use my current credentials option:

HubspotDSN
Finally, you will be asked to select a table or view to get data from. Select one and load the data!
Finally, finally, read extracted data from Hubspot in a Power BI report:

Import data using a SQL query

If you wish to import Hubspot data from SQL query rather than a table then you can use advanced options during import steps (as below). After selecting DSN you can click on advanced options to see SQL Query editor.

HubspotDSN

SELECT * FROM Companies
-- WHERE Id=123

Get REST API data in Power BI Desktop using SQL query and ODBC

Consider using Custom Objects feature in ODBC data source to encapsulate SQL query in a Virtual Table. This way, you can see a virtual table in Power BI table list where you can import multiple objects using the same connection rather than creating a new connection for each custom SQL query.

Publish Power BI report to Power BI service

Here are the instructions on how to publish a Power BI report to Power BI service from Power BI Desktop application:

First of all, go to Power BI Desktop, open a Power BI report, and click Publish button:
Then select the Workspace you want to publish report to and hit Select button:
Finally, if everything went right, you will see a window indicating success:

What's next? If you need to periodically refresh Power BI semantic model (dataset) to ensure data accuracy and up-to-dateness, you can accomplish that by using Microsoft On-premises data gateway. Proceed to the next section - Refresh the Power BI semantic model via the gateway - and learn how to do that.

Refresh the Power BI semantic model (dataset) via the gateway

Power BI allows you to refresh semantic models (previously known as "datasets") that are based on data sources residing on-premises. This is achieved using the Microsoft On-premises data gateway. It acts as a secure bridge between Power BI cloud services and your local Hubspot ODBC data source:

Power BI and On-premises data gateway diagram

There are two types of On-premises data gateways:

Standard mode

Supports Power BI and other Microsoft Cloud services
Installs as a Windows service
Starts automatically
Supports centralized user access control
Supports the Direct Query feature
Ideal for enterprise solutions

Personal mode

Supports Power BI services only
Cannot run as a Windows service
Stops when you sign out of Windows
Does not support access control
Does not support the Direct Query feature
Best for individual use and POC solutions

You can download the On-premises data gateway directly from the Microsoft Fabric or Power BI portals:

Download Power BI On-premises data gateway

We recommend using Personal mode for quick POCs or personal use, and Standard mode for production scenarios.

Below are instructions on how to refresh the semantic model using both gateway types.

Use the Standard mode gateway (recommended)

Best for enterprise production environments where multiple users need to share the same gateway connection.

Follow these steps to refresh a Power BI semantic model using the On-premises data gateway (Standard mode):

Go to Power BI My workspace, hover your mouse cursor over your semantic model, and click Settings:
If you see this view, it means you must install the On-premises data gateway (Standard mode):
Download On-premises data gateway (standard mode) and run the installer.
Once the configuration window opens, sign in:

Sign in with the same email address you use for Microsoft Fabric.
Select Register a new gateway on this computer (or migrate an existing one):
Name your gateway, enter a Recovery key, and click the Configure button:

Save your Recovery Key in a safe place (like a password manager). If you lose it, you cannot restore or migrate this gateway later.
Once Microsoft gateway is installed, check if it registered correctly:
- Go back to Power BI portal
- Click Gear icon on top-right
- And then hit Manage connections and gateways menu item
Continue by clicking the On-premises data gateway tab and selecting Standard mode gateways from the dropdown menu:
If your gateway is not listed, the registration may have failed. To resolve this:
- Wait a couple of minutes and refresh Power BI portal page
- Restart the machine where On-premises data gateway is installed
- Check firewall settings
Success! The gateway is now Online and ready to handle requests.
Now, return to your semantic model settings in the Power BI portal. Refresh the page, and you should see your newly created gateway. Click the arrow icon to expand the options, and then click the Add to gateway link:

ODBC{"connectionstring":"dsn=HubspotDSN"}
Once you do that, you will create a new gateway connection. Give it a name, set the Authentication method, Privacy level, and click the Create button:

dsn=HubspotDSN

In this example, we use the least restrictive Privacy level.

If your connection uses a full connection string, you may hit a length limitation when entering it into the field. To create the connection, you will need to shorten it manually. Check the section about the limitation of a full connection string on how to accomplish this.

On-premises data gateway (Personal mode) does not have this limitation.
Select the newly created connection to map it to your dataset:

ODBC{"connectionstring":"dsn=HubspotDSN"}
Finally, you can refresh the semantic model:

Use the Personal mode gateway (POC)

Best for single-user scenarios, quick tests (POC), or when you don't have administrative rights to install the Standard gateway.

Follow these steps to refresh a Power BI semantic model using the On-premises data gateway (Personal mode):

Go to Power BI My workspace, hover your mouse cursor over your semantic model, and click Settings:
If you see this view, it means you must install the On-premises data gateway (Personal mode):
Install On-premises data gateway (personal mode) and sign-in:

Use the same email address you use when logging in into your account.
Once Microsoft gateway is installed, check if it registered correctly:
- Go back to Power BI portal
- Click Gear icon on top-right
- And then hit Manage connections and gateways menu item
Continue by clicking On-premises data gateway tab and select Personal mode option from the dropdown:
If your gateway is not listed, the registration may have failed. To resolve this:
- Wait a couple of minutes and refresh Power BI portal page
- Restart the machine where On-premises data gateway is installed
- Check firewall settings
The On-premises data gateway is now Online and ready to receive requests.
Return to your semantic model Settings, expand Data source credentials, click Edit credentials, select the Authentication method and the Privacy level, and then click the Sign in button:

dsn=HubspotDSN
Finally, you are ready to refresh your semantic model:

Advanced topics

Editing query in Power BI

There will be a time you need to change the initial query after importing data into Power BI. Don't worry, just right-click on your table and click Edit query menu item:

Edit query in Power BI to get REST API data

Refer to Power Query M reference for more information on how to use its advanced features in your queries.

Using parameters for dynamic queries

In the real world, many values of your REST / SOAP API call may be coming from parameters. If that's the case for you can try to edit script manually as below. In below example its calling SQL Query with POST method and passing some parameters. Notice below where paraAPIKey is Power BI Parameter (string type). You can use parameters anywhere in your script just like the normal variable.

To use a parameter in Power BI report, follow these simple steps:

Firstly, you need to Edit query of your table (see previous section)

Then just create a new parameter by clicking Manage Parameters dropdown, click New Parameter option, and use it in the query:

                
                            = Odbc.Query("dsn=HubspotDSN",
                                         "SELECT ProductID, ProductName, UnitPrice, UnitsInStock
                                          FROM Products
                                          WHERE UnitPrice > " & Text.From(MyParameter) & "
                                          ORDER BY UnitPrice")

Use parameter in Power BI to get REST API data

Refer to Power Query M reference for more information on how to use its advanced features in your queries.

Using DirectQuery (live connection)

By default, Power BI imports Hubspot data into its internal cache. However, if you require real-time data, you can use the DirectQuery mode.

Since the native Power BI ODBC connector limits you to Import mode, we must bridge the connection via Microsoft SQL Server. To do this, we configure the ZappySys Data Gateway and create a Linked Server pointing to it:

Architecture diagram: Power BI (DirectQuery) connected to SQL Server, bridging to ZappySys Data Gateway via Linked Server, and finally fetching data from Hubspot Service

This method requires an existing Microsoft SQL Server instance to act as the bridge.

Follow these steps to use DirectQuery:

Configure ZappySys Data Gateway and create a Linked Server in SQL Server.
Once the Linked Server is ready, open Power BI Desktop.
Click Get Data and select SQL Server.
Enter your SQL Server instance name and a valid database name (e.g., master).
Under Data Connectivity mode, select DirectQuery.
Expand Advanced options and enter your SQL query using the OPENQUERY syntax below (replace [LINKED_SERVER_NAME] with your actual Linked Server name):

SELECT * FROM OPENQUERY([LS_TO_HUBSPOT_IN_GATEWAY], 'SELECT * FROM Companies -- WHERE Id=123')
```
SELECT * FROM OPENQUERY([LS_TO_HUBSPOT_IN_GATEWAY], 'SELECT * FROM Companies
-- WHERE Id=123')
```
Click OK and load the data. Your Hubspot data is now linked live rather than imported.

Avoid using DirectQuery unless it is required for very large datasets or real-time data needs. Data is fetched on demand, which can impact performance compared to the cached Import mode.

Using full ODBC connection string

In the previous steps we used a very short format of ODBC connection string - a DSN. Yet sometimes you don't want a dependency on an ODBC data source (and an extra step). In those times, you can define a full connection string and skip creating an ODBC data source entirely. Let's see below how to accomplish that in the below steps:

Open ODBC data source configuration and click Copy settings:

ZappySys API Driver - Configuration [Version: 2.0.1.10418]

ZappySys API Driver - Hubspot

Read and write HubSpot data effortlessly. Integrate, manage, and automate contacts, companies, deals, and tickets — almost no coding required.

HubspotDSN
The window opens, telling us the connection string was successfully copied to the clipboard:
Then just paste the connection string into your script:

HubspotDSN

DRIVER={ZappySys API Driver};ServiceUrl=https://api.hubapi.com;CredentialType=Token;
You are good to go! The script will execute the same way as using a DSN.

The DSN defined in the Data source name (DSN) field will be ignored.

Have in mind that a full connection string has length limitations.

Proceed to the next step to find out the details.

Handling limitations of using a full connection string

Despite using a full ODBC connection string may be very convenient it comes with a limitation: it's length is limited to 1024 symbols (or sometimes more). It usually happens when API provider generates a very long Refresh Token when OAuth is at play. If you are using such a long ODBC connection string, you may get this error:

"Connection string exceeds maximum allowed length of 1024"

But there is a solution to this by storing the full connection string in a file. Follow the steps below to achieve this:

Open your ODBC data source.
Click Copy settings button to copy a full connection string (see the previous section on how to accomplish that).
Then create a new file, let's say, in C:\temp\odbc-connection-string.txt.
Continue by pasting the copied connection string into a newly created file and save it.
Finally, the last step! Just construct a shorter ODBC connection string using this format:
```
DRIVER={ZappySys API Driver};SettingsFile=C:\temp\odbc-connection-string.txt
```
Our troubles are over! Now you should be able to use this connection string in Power BI with no problems.

This feature requires ODBC PowerPack v1.9.0 or later.

Optional: Centralized data access via ZappySys Data Gateway

In some situations, you may need to provide Hubspot data access to multiple users or services. Configuring the data source on a Data Gateway creates a single, centralized connection point for this purpose.

This configuration provides two primary advantages:

Centralized data access
The data source is configured once on the gateway, eliminating the need to set it up individually on each user's machine or application. This significantly simplifies the management process.
Centralized access control
Since all connections route through the gateway, access can be governed or revoked from a single location for all users.

	Data Gateway	Local ODBC data source
Simple configuration
Installation	Single machine	Per machine
Connectivity	Local and remote	Local only
Connections limit	Limited by License	Unlimited
Central data access
Central access control
More flexible cost

To achieve this, you must first create a data source in the Data Gateway (server-side) and then create an ODBC data source in Power BI (client-side) to connect to it.

Let's not wait and get going!

Create Hubspot data source in the gateway

In this section we will create a data source for Hubspot in the Data Gateway. Let's follow these steps to accomplish that:

Search for gateway in the Windows Start Menu and open ZappySys Data Gateway Configuration:
Go to the Users tab and follow these steps to add a Data Gateway user:
- Click the Add button
- In the Login field enter a username, e.g., john
- Then enter a Password
- Check the Is Administrator checkbox
- Click OK to save
Now we are ready to add a data source:
- Click the Add button
- Give the Data source a name (have it handy for later)
- Then select Native - ZappySys API Driver
- Finally, click OK
HubspotDSN

ZappySys API Driver
When the ZappySys API Driver configuration window opens, go back to ODBC Data Source Administrator where you already have the Hubspot ODBC data source created and configured, and follow these steps on how to Import data source configuration into the Gateway:
- Open ODBC data source configuration and click Copy settings:
  
  ZappySys API Driver - Configuration [Version: 2.0.1.10418]
  
  ZappySys API Driver - Hubspot
  
  Read and write HubSpot data effortlessly. Integrate, manage, and automate contacts, companies, deals, and tickets — almost no coding required.
  
  HubspotDSN
- The window opens, telling us the connection string was successfully copied to the clipboard:
- Then go to Data Gateway configuration and in data source configuration window click Load settings:
  
  HubspotDSN
  
  ZappySys API Driver - Configuration [Version: 2.0.1.10418]
  
  ZappySys API Driver - Hubspot
  
  Read and write HubSpot data effortlessly. Integrate, manage, and automate contacts, companies, deals, and tickets — almost no coding required.
  
  HubspotDSN
- Once a window opens, just paste the settings by pressing CTRL+V or by clicking right mouse button and then Paste option.
Once done, go to the Network Settings tab and Add a firewall rule for inbound traffic:
- This will initially allow all inbound traffic.
- Click Edit IP filters to restrict access to specific IP addresses or ranges.
Crucial Step: After creating or modifying the data source, you must:
- Click the Save button to persist your changes.
- Hit Yes when prompted to restart the Data Gateway service.
This ensures all changes are properly applied:

Skipping this step may cause the new settings to fail, preventing you from connecting to the data source.

Create ODBC data source to connect to the gateway

In this part we will create an ODBC data source to connect to the ZappySys Data Gateway from Power BI. To achieve that, let's perform these steps:

Search for odbc and open the ODBC Data Sources (64-bit):
Create a User data source (User DSN) based on the ODBC Driver 17 for SQL Server driver:

ODBC Driver 17 for SQL Server

If you don't see the ODBC Driver 17 for SQL Server driver in the list, choose a similar version.
Then set a Name for the data source (e.g. Gateway) and the address of the Data Gateway:

ZappySysGatewayDSN

localhost,5000

Make sure you separate the hostname and port with a comma, e.g. localhost,5000.
Proceed with the authentication part:
- Select SQL Server authentication
- In the Login ID field enter the user name you created in the Data Gateway, e.g., john
- Set Password to the one you configured in the Data Gateway
Then set the default database property to HubspotDSN (the one we used in the Data Gateway):

HubspotDSN

HubspotDSN

Make sure to type the data source name manually or copy/paste it directly into the field. Using the dropdown might fail because the Trust server certificate option is not enabled yet (next step).
Continue by checking the Trust server certificate option:
Once you do that, test the connection:
If the connection is successful, everything is good:
Done!

We are ready to move to the final step. Let's do it!

Access data in Power BI via the gateway

Finally, we are ready to read data from Hubspot in Power BI via the Data Gateway. Follow these final steps:

Go back to Power BI.
Once you open Power BI Desktop click Get Data to get data from ODBC:
A window opens, and then search for "odbc" to get data from ODBC data source:
Another window opens and asks to select a Data Source we already created. Choose ZappySysGatewayDSN and continue:

ZappySysGatewayDSN
When the ODBC driver authentication window opens, configure the following:
- Enter the User name (e.g., john)
- Enter the Password that you configured in ZappySys Data Gateway
- Hit the Connect button
dsn=ZappySysGatewayDSN

Make sure the Database tab is selected; otherwise, Power BI won't be able to connect to the ZappySys Data Gateway.
Read the data the same way we discussed at the beginning of this article.
That's it!

Now you can connect to Hubspot data in Power BI via the Data Gateway.

Supported Hubspot Connector actions

Got a specific use case in mind? We've mapped out exactly how to perform a variety of essential Hubspot operations directly in Power BI, so you don't have to figure out the setup from scratch. Check out the step-by-step guides below:

Conclusion

In this article we showed you how to connect to Hubspot in Power BI and integrate data without writing complex code — all of this was powered by Hubspot ODBC Driver.

Download ODBC PowerPack now or ping us via chat if you have any questions or are looking for a specific feature (you can also reach out to us by submitting a ticket):

Download Chat