Hubspot Connectors

ZappySys Hubspot Connector provide read / write capability inside your app (see list below), using these drag and drop , high performance connectors you can perform many Hubspot operations without any coding. You can use this connector to integrate Hubspot data inside apps like SSIS, SQL Server or popular ETL Platforms / BI Tools/ Reporting Apps / Programming languages (i.e. Informatica, Power BI, SSRS, Excel, C#, JAVA, Python)

Download for SSIS Download for Other Apps Documentation

Video Tutorial - Hubspot - Connectors REST API Integration

Click on your App below to get started with Hubspot Integration

Choose your App / Scenario for which you like to integrate Hubspot

Actions supported by Hubspot Connector

Hubspot Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.
 Search Companies
Search companies using one or more filter conditions. Choose properties to include in the output.
Parameter Description
Properties
 Search Contacts
Search contacts using one or more filter conditions. Choose properties to include in the output.
Parameter Description
Properties
 Search Tickets
Search tickets using one or more filter conditions. Choose properties to include in the output.
Parameter Description
Properties
 Search Deals
Search deals using one or more filter conditions. Choose properties to include in the output.
Parameter Description
Properties
 Search Products
Search products using one or more filter conditions. Choose properties to include in the output.
Parameter Description
Properties
 Search LineItems
Search LineItems using one or more filter conditions. Choose properties to include in the output.
Parameter Description
Properties
 Search Quotes
Search Quotes using one or more filter conditions. Choose properties to include in the output.
Parameter Description
Properties
 Get Contacts
Parameter Description
Properties
 Get Contact By ID
Parameter Description
Properties
 Get Contact Properties
 Create Contacts
 Update Contacts
 Archive Contacts
 Get Deals
Parameter Description
Properties
 Get Deal Properties
 Get Deal By ID
Parameter Description
Properties
 Create Deals
 Archive Deals
 Update Deals
 Get Products
Parameter Description
Properties
 Get Product By ID
Parameter Description
Properties
 Get Product Properties
 Create Products
 Archive Products
 Update Products
 Get Companies
Parameter Description
Properties
 Get Company By ID
Parameter Description
Properties
 Get Company Properties
 Create Companies
 Archive Companies
 Update Companies
 Get Line Items
Parameter Description
Properties
 Get Line Item By ID
Parameter Description
Properties
 Get Line Item Properties
Parameter Description
 Create Line Items
Parameter Description
 Archive Line Items
 Update Line items
 Get Tickets
Parameter Description
Properties
 Get Ticket By ID
Parameter Description
Properties
 Get Tickets Properties
Parameter Description
 Create Tickets
 Archive Tickets
 Update Tickets
 Get Quotes
Parameter Description
Properties
 Get Ticket By ID
Parameter Description
Properties
 Get Quotes Properties
Parameter Description
 Create Quotes
 Archive Quotes
 Update Quotes
 Get Owners
Parameter Description
OwnerId
 Upload File from Local Disk
Uploads local file to Hubspot CRM. This API requires files permission for the App (see scopes)
Parameter Description
Source File Path Specify a disk file path
Target Folder Path Specify Target folder path. Partially optional field. One of folderPath or folderId must be specified. Path of the folder the file should be uploaded into. Uploading files into the root path “/” is highly discouraged.
Target File Name (e.g. MyFile.xlsx) Specify file name you like to give
AccessType Specify file access type
Option Value
PRIVATE PRIVATE
PUBLIC_NOT_INDEXABLE PUBLIC_NOT_INDEXABLE
PUBLIC_INDEXABLE PUBLIC_INDEXABLE
Overwrite Specify wheather you like to overwrite target file if exists. If true this file with replace any existing files with the name, folder, and type. Note: If this is set to false, and the uploaded file matches the filename of an existing file in the same folder, the file will be uploaded with a number incremented filename (e.g. example_file.txt will become example_file-1.txt)
Option Value
false false
true true
DuplicateValidationStrategy Specify how to handle duplicate target file.
Option Value
NONE NONE
REJECT REJECT
RETURN_EXISTING RETURN_EXISTING
DuplicateValidationScope Specify scope of duplicate validation.
Option Value
EXACT_FOLDER EXACT_FOLDER
ENTIRE_PORTAL ENTIRE_PORTAL
 Generic Request
This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL.
Parameter Description
Url API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
Body Request Body content goes here
IsMultiPart Check this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract
Headers Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair