C# Hubspot Connector In this article you will learn how to integrate Hubspot data to C# (live / bi-directional connection to Hubspot). Hubpost Connector can be used to integrate Hubspot and your data source, e.g. Microsoft SQL Server, Oracle, Excel, Power BI, etc. Get, write, delete Hubspot data in a few clicks!. Using Hubspot Connector you will be able to connect, read, and write data from within C#. Follow the steps below to see how we would accomplish that. Download  Help File  Buy  Driver mentioned in this article is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc. If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started. ODBC PowerPack - System Requirements and Installation Getting Started - Using ODBC PowerPack ODBC API Driver Help File

See also Connect Hubspot in SSIS Connect Hubspot in SQL Server Connect Hubspot in Power BI Connect Hubspot in SSRS Connect Hubspot in Informatica Connect Hubspot in MS Access Connect Hubspot in MS Excel Connect Hubspot in SSAS Connect Hubspot in Python Connect Hubspot in JAVA Connect Hubspot in Tableau Connect Hubspot in SAP Crystal Reports Connect Hubspot in Azure Data Factory (ADF) Connect Hubspot in ODBC

Create ODBC Data Source (DSN) based on ZappySys API Driver

To get data from Hubspot using C# we first need to create a DSN (Data Source) which will access data from Hubspot. We will later be able to read data using C#. Perform these steps:

1. Install ZappySys ODBC PowerPack.

2. Open ODBC Data Sources (x64):
   

3. Create a User Data Source (User DSN) based on ZappySys API Driver

   ZappySys API Driver

   
   You should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version.

4. 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

   

5. 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) [Http]

   Authenticate using static AccessToken (Private App) to access specific account. Follow 3 simple steps. 1) Create an App, 2) select permissions and 3) get Token and use on this UI. For more information on how to obtain AccessToken visit https://developers.hubspot.com/docs/api/private-apps [Read more..]

   Steps to get Hubspot Credentials
   

   Just follow this link on how to get an PrivateApp Access Token. Once you obtain it, paste it into AccessToken parameter: https://developers.hubspot.com/docs/api/private-apps

   Fill in all required parameters and set optional parameters if needed:

   HubspotDSN

   Hubspot

   Private App (Static Access Token) [Http]

   https://api.hubapi.com

   Required Parameters
   AccessToken	Fill in the parameter...
   Optional Parameters
   RetryMode	Fill in the parameter...
   RetryStatusCodeList	Fill in the parameter...
   RetryCountMax	Fill in the parameter...
   RetryMultiplyWaitTime	Fill in the parameter...

   

    User Credentials (3-Legged) [OAuth]

   OAuth App must be created in HubSpot website. These settings typically found here https://developers.hubspot.com/docs/api/working-with-oauth. [Read more..]

   Steps to get Hubspot Credentials
   

   Just follow this link on how to create an API app: https://developers.hubspot.com/docs/api/creating-an-app On the App Scopes section make sure to select following scopes in order to access all features of this driver. You can choose more or less but keep in mind to select same or less number of scopes on Driver UI (Scopes Property) else it will not authorize the request. If you need File Upload feature then choose files scope.

   Your selected scopes when registering your app must match the scopes you enter here on the connector screen. You cannot request less or more scopes for now (it may change in future). If they don't match, the connector will not be able to work with your HubSpot account!

   		
   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
   
   you can add more... but must select same number of scopes in the connection screen too (Scopes Parameter)
   

   Fill in all required parameters and set optional parameters if needed:

   HubspotDSN

   Hubspot

   User Credentials (3-Legged) [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	Fill in the parameter...
   Client Secret	Fill in the parameter...
   ReturnUrl	Fill in the parameter...
   RetryMode	Fill in the parameter...
   RetryStatusCodeList	Fill in the parameter...
   RetryCountMax	Fill in the parameter...
   RetryMultiplyWaitTime	Fill in the parameter...

   

    API Key in URL (Deprecated) [Http]

   Authenticate using Static API Key instead of userid / password. It can be found at https://app.hubspot.com/api-key/<YOUR_ACCOUNT_ID>>/call-log [Read more..]

   Steps to get Hubspot Credentials
   

   Just follow this link on how to get an API key. Once you obtain it, paste it into ApiKey parameter: https://knowledge.hubspot.com/integrations/how-do-i-get-my-hubspot-api-key

   Fill in all required parameters and set optional parameters if needed:

   HubspotDSN

   Hubspot

   API Key in URL (Deprecated) [Http]

   https://api.hubapi.com

   Required Parameters
   ApiKey	Fill in the parameter...
   Optional Parameters
   RetryMode	Fill in the parameter...
   RetryStatusCodeList	Fill in the parameter...
   RetryCountMax	Fill in the parameter...
   RetryMultiplyWaitTime	Fill in the parameter...

   

6. Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
   

7. Click OK to finish creating the data source.

Read data in C# from the DSN

1. Create a new Console project and use this code to read the data:
   

   "HubspotDSN";

   

2. Press F5 to run the code and read the data:
   

3. Here is the code in text format:

   
   using System;
   using System.Data.Odbc;
   
   namespace ConsoleApp {
       class Program {
           static void Main() {
               var dsn = "HubspotDSN";
               using (var conn = new OdbcConnection(String.Format("DSN={0}", dsn)))
               {
                   conn.Open();
                   var cmd = new OdbcCommand("SELECT * FROM Products", conn);
                   var rdr = cmd.ExecuteReader();
                   while (rdr.Read())
                   {
                       for (int i = 0; i < rdr.FieldCount; i++)
                       {
                               Console.Write("{0}\t", rdr[i]);
                       }
                       Console.WriteLine();
                   }
               }
               Console.ReadKey();
           }
       }
   }
   

4. If you want to avoid being dependent on a DSN and creating multiple DSNs for each platform (x86, x64), then you can use a fully qualified connection string. Simply go to your DSN and copy the Connection String . Then in your C# code, pass the connection string as an argument when calling the OdbcConnection object's constructor, for example:

       
   var connectionString = "DRIVER={ZappySys API Driver};ServiceUrl=https://services.odata.org/V3/Northwind/Northwind.svc;Provider=OData;AuthName=Http;";
   
   using (var conn = new OdbcConnection(connectionString))
   {
       // ...
   }
   

   How to Overcome the Long Connection String Issue

   This issue is typically caused when the connection string includes a long RefreshToken attribute (i.e. RefreshToken=xxxxxxxxxxxx...xxx, especially if it's more than 1,000 characters).

   A good solution is to supply the RefreshToken by a file. Simply copy and paste the RefreshToken into a text file and save it, and then pass that file path in the connection string instead of directly supplying the RefreshToken.

   Here is an example of a connection string that can cause the issue:

   
   var connectionString = "Driver={ZappySys API Driver};RefreshToken=xxxxxxxxxxxx...xxxxxxx;ServiceUrl=...;";
   
   using (var conn = new OdbcConnection(connectionString))
   {
       // ...
   }
   

   Here is an example of a connection string that has resolved the issue by moving the RefreshToken attribute to the file c:\my_refresh_token.txt:

   
   var connectionString = "Driver={ZappySys API Driver};RefreshTokenFile=c:\my_refresh_token.txt;ServiceUrl=...;";
   
   using (connectionString)
   {
       // ...
   }
   

Create Custom Store Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Store Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

1. Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
   

2. Enter the desired Procedure name and click on OK:
   

3. Select the created Store Procedure and write the your desired store procedure and Save it and it will create the custom store procedure in the ZappySys Driver:
   Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
   

   CREATE PROCEDURE [usp_get_orders]
       @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
    AS
       SELECT * FROM Orders where OrderDate >= '<@fromdate>';
   

   
   

4. That's it now go to Preview Tab and Execute your Store Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
   

   Exec usp_get_orders '1996-01-01';

   
   

5. Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
   As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
   

   SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')

   
   

6. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
   

Create Custom Virtual Table in ZappySys Driver

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

1. Go to Custom Objects Tab and Click on Add button and Select Add Table:
   

2. Enter the desired Table name and click on OK:
   

3. And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.

4. Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
   Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
   

   SELECT
     "ShipCountry",
     "OrderID",
     "CustomerID",
     "EmployeeID",
     "OrderDate",
     "RequiredDate",
     "ShippedDate",
     "ShipVia",
     "Freight",
     "ShipName",
     "ShipAddress",
     "ShipCity",
     "ShipRegion",
     "ShipPostalCode"
   FROM "Orders"
   Where "ShipCountry"='USA'

   
   

5. That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
   

   SELECT * FROM "vt__usa_orders_only"

   
   

6. Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
   As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
   

   SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')

   
   

7. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
   

Conclusion

Download Hubspot Connector for C# Documentation 

Actions supported by Hubspot Connector

Other App Integration scenarios for Hubspot

SSIS

SQL Server

Power BI

SSRS

Informatica

MS Access

MS Excel

SSAS

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (ADF)

ODBC

Other Connectors for C#

Zendesk

Azure DevOps

ManagedEngine ServiceDesk Plus (Zoho)

Zoho CRM

Hubspot

Google Sheets

Stripe

YouTube

Google BigQuery

OneDrive

OData

Amazon Ads

Mailchimp

Jira

Outlook Mail (Office 365)

Zoom

Cosmos DB

Shopify

Nativo

Google Drive

SharePoint Online

Amazon MWS

ServiceNow

ElasticSearch

Google Calendar

DropBox

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Download Hubspot Connector for C# Documentation 

Common Searches: