HubSpot: Sales and CMS

Discover more about the HubSpot Sales and HubSpot CMS connectors and how to use them on the Digibee Integration Platform.

The HubSpot Sales and HubSpot CMS connectors integrate the Digibee Integration Platform with HubSpot, enabling the automation of sales and content management processes.

  • The HubSpot Sales connector streamlines lead management, deals, and sales activities, optimizing the sales workflow.

  • The HubSpot CMS connector allows for the management of content, such as pages and blogs, ensuring an efficient and integrated digital experience.

Together, these connectors provide greater control and automation for sales and marketing teams.

Parameters

Take a look at the configuration parameters for the connectors. Parameters supported by Double Braces expressions are marked with (DB).

Both connectors share the same parameters, but they differ in the available Paths.

General tab

Parameter
Description
Default value
Data type

Account

The account used by the connector. Supported types: OAuth Bearer and OAuth 2. Learn more about working with OAuth Bearer and OAuth 2 in the HubSpot documentation.

N/A

Account

Fail On Error

If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the "success" property.

False

Boolean

API tab

Parameter
Description
Default value
Data type

Host (DB)

The base URL of the HubSpot API.

N/A

String

Path

The specific HubSpot endpoint to be accessed. The selected path determines the available operations and required configurations. Refer to the HubSpot API documentation for details on each endpoint.

N/A

String

Method

The HTTP method used for the request.

N/A

String

Settings tab

Parameter
Description
Default value
Data type

Connect Timeout (ms)

Maximum time allowed for establishing a connection, in milliseconds.

30000

Integer

Read Timeout (ms)

Maximum time allowed for reading data, in milliseconds.

30000

Integer

Stop on Client Error

When enabled, stops the pipeline execution if a 4xx HTTP error occurs.

False

Boolean

Stop on Server Error

When enabled, stops the pipeline execution if a 5xx HTTP error occurs.

False

Boolean

Override Response Charset

When enabled, replaces the charset returned by the endpoint with the one specified in the Response Charset property. Otherwise, the charset from the Content-Type header is used.

True

Boolean

Response Charset

Defines the charset to be used when Override Response Charset is enabled. Default: UTF-8.

UTF-8

String

Documentation tab

Parameter
Description
Default value
Data type

Documentation

Section for documenting any necessary information about the connector configuration and business rules.

N/A

String

Last updated

Was this helpful?