See what the HubSpot integration can do →
The HubSpot integration connects a HubSpot account to iPaaS.com and keeps the two systems in step. Depending on the mapping collections enabled for the subscription, the integration synchronizes customers, customer addresses, customer categories, companies, company addresses, customer and company relationships, products, transactions, and transaction line items.
How to Connect
Prerequisites
Since HubSpot does not have native contact or company category support, the following allows subscribers or their MiSP to create a field to leverage syncing customer and company categories in HubSpot. Both properties are optional: if a category property is not created and named in the subscription settings, category synchronization for that object is simply not performed.
Before setting up the HubSpot integration in iPaaS.com, prepare the following in HubSpot:
Contact Category Field Name: This should contain the property label of a contact property in HubSpot that will represent the contact category, which will be synchronized with iPaaS.com customer categories. This property must be created in HubSpot beforehand as a dropdown type. To set up this field:
Company Category Field Name: This should contain the property label of a company property in HubSpot that will represent the company category, which will be synchronized with iPaaS.com customer categories. This property must be created in HubSpot beforehand as a dropdown type. To set up this field:
Navigate to Settings > Data Management > Properties in HubSpot.
Click Create Property.
Provide the desired property name as a Company Object type property, and select the desired group.
On the Field Type tab, select Dropdown Select as the field type, and enter at least one category name before clicking Create.
The integration matches these settings against the property label shown in HubSpot, not the internal property name. Subscribers or their MiSP should enter the label exactly as it appears on the property.
Configure Subscription Settings
Navigate to the HubSpot subscription settings in iPaaS.com and provide the following information:
Field | Description | Required | Example |
Name | A unique name for identifying the HubSpot subscription in iPaaS.com. | Yes | HubSpot |
Versions | The iPaaS.com HubSpot integration version to use. The latest version is recommended. | Yes | v1.0 |
Create Default Mappings | When selected, the template mapping collections are created with the subscription. Leave it cleared only if all mappings will be built manually. | No | Selected |
API Url | The base API URL for HubSpot. | Yes | |
API Key | Enter | Yes | null |
Transfer Products as a Prerequisite for Transactions | Enter | No | true |
Contact Category Field Name | The label of the HubSpot contact property that represents the customer category. Leave it empty to skip contact category synchronization. | No | Contact Category |
Company Category Field Name | The label of the HubSpot company property that represents the company category. Leave it empty to skip company category synchronization. | No | Company Category |
Two settings behave in ways worth noting before saving:
Transfer Products as a Prerequisite for Transactions: Only the exact value
trueenables the behavior, and the comparison ignores capitalization, soTruealso works. Any other entry — including1,yes, andon— leaves the behavior disabled without reporting an error. This setting applies only to transactions transferring from iPaaS.com to HubSpot; it has no effect on transfers to iPaaS.com. The customer and company associated with a transaction are always transferred as prerequisites regardless of this setting.Contact Category Field Name and Company Category Field Name: Both are optional. An empty value silently disables category synchronization for that object rather than raising an error, so a missing category in HubSpot is usually a sign that the property label was left blank or does not match.
Authentication Methods
Method: OAuth Authentication
OAuth is the intended authentication method for HubSpot. Once OAuth is completed, the stored access token is used for every HubSpot call.
Save the subscription settings in iPaaS.com.
Open the HubSpot subscription settings and click the lock icon in the top toolbar.
You will be redirected to the HubSpot login page.
Sign in with your HubSpot credentials. If you are already signed in, you will advance to the next step.
Select the preferred account if prompted, and choose the account.
Once authenticated, you will be redirected back to iPaaS.com, where an Authorization card confirms that authorization is complete. Click Close Page to close it.
Wait a moment, then refresh the HubSpot subscription. If authentication succeeded, access tokens are saved to the OAuth details within the subscription settings.
To restart authentication, delete the access tokens and OAuth status using the trash icons next to them, refresh the iPaaS.com subscription, and click the lock icon again.
The integration refreshes the OAuth token when the connection is established, so a subscription that has been idle does not require manual reauthentication.
Method: API Key Authentication
The API Key setting is a fallback and is only used when no OAuth access token is stored on the subscription. When a value other than null is supplied and OAuth has not been completed, the integration presents that value to HubSpot as a private app token. Subscribers or their MiSP who complete OAuth authentication never use this value, which is why null is the recommended entry.
Verifying the Connection
Testing the connection in iPaaS.com reports success without confirming that HubSpot has accepted the stored credentials, so a successful test alone does not prove the connection works. Confirm the connection by running an actual transfer of a small record set and reviewing the outcome under Dashboard > Integration Monitoring > Error Logs. Credential and permission problems surface there on the first real transfer.
Initialization Support
Initialization is not supported for HubSpot in iPaaS.com. No data type can be transferred in bulk through initialization, and all data synchronization and mappings must be configured through the mapping collections during the integration process.
Throttling
Throttling ensures that HubSpot's API isn't overwhelmed by excessive API calls, preserving system performance during heavy data transfers. The throttling fields are required and arrive pre-populated with default values. Subscribers or their MiSP can adjust them, and should reduce them if HubSpot rate limit errors are encountered. For more details, refer to Subscription Configuration – Edit.












