The Jitterbit Harmony HubSpot Connector establishes access to HubSpot.
The HubSpot connector provides an interface for creating a HubSpot connection, the foundation used for generating instances of HubSpot activities. These activities, once configured, interact with HubSpot through the connection.
The HubSpot connector is accessed from the design component palette's Connections tab (see Design Component Palette).
This connector is used to first configure a HubSpot connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).
Together, a specific HubSpot connection and its activities are referred to as a HubSpot endpoint:
Search: Retrieves object data from HubSpot and is intended to be used as a source in an operation.
Create: Creates object data in HubSpot and is intended to be used as a target in an operation.
Update: Updates object data in HubSpot and is intended to be used as a target in an operation.
Delete: Deletes object data from HubSpot and is intended to be used as a target in an operation.
This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.
Prerequisites and Supported API Versions¶
The HubSpot connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.
The HubSpot connector uses the HubSpot API. Refer to the API documentation for information on the schema nodes and fields.
To use the HubSpot connector, you must have a HubSpot private app, the appropriate scope permissions set, and an access token as described in HubSpot Prerequisites.
If you experience issues with the HubSpot connector, these troubleshooting steps are recommended:
Ensure the HubSpot connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
Check the operation logs for any information written during execution of the operation.
Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.
If using Private Agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:
<logger name="org.jitterbit.connector.verbose.logging.hubspot" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.