Go to Subscriptions Management > Subscriptions and click Search Certified Integration Marketplace and Subscribe.
Click the HubSpot Integration title.
On the Subscription Detail page, click the Subscribe button.
Enter the Name of the subscription and select a Version. It can be set to any relevant and unique subscription name within the company where this subscription is created.
Format: [Product Name] - [Environment/Purpose]
Example: HubSpot – Release
Select Create Default Mappings (recommended). If you don’t want to create default mappings and want to create all mappings from scratch by yourself, then uncheck this box.
Enter null in API Key. This value will not be used for authentication, but a value is required. You will authenticate later in the procedures.
Provide the API endpoint for your HubSpot instance. The HubSpot API URL is same for all instances and is not instance-based.
Environment URLs:
Test/Sandbox:
https://api.hubapi.comProduction:
https://api.hubapi.com
Enter the Company Category Field Name. This should contain the property label of a HubSpot company property representing the company category, which will be synchronized with iPaaS.com customer categories. This property must be created in HubSpot beforehand by the client/user as a dropdown type.
Enter the Contact Category Field Name. This should contain the label of a HubSpot contact property that will be synchronized with iPaaS.com customer categories. This property must be created in HubSpot beforehand by the client/user as a dropdown type.
Enter Transfer Products as a Prerequisite for Transactions. When set to true, the system will use the transaction line-item SKU to get the iPaaS product/variant and create the product/parent-product as a prerequisite from iPaaS into HubSpot. Then, when the transaction is created in HubSpot, it can be created along with its line items. If empty or false, no preprocessing will be performed for the transaction line item, and transfers may fail. This gives clients a flexible way to enable or disable preprocessing based on their specific business requirements.
Enter the API Throttle Limit. This setting prevents any single integration or user from overwhelming the system with too many requests. It protects system performance by controlling the number of API requests that can run simultaneously, ensuring fair usage.
Recommended Values
Initial Setup: 5
Ongoing Operations: 500
High Volume: 500
Enter the API Throttle Seconds. This defines the time window during which the API Throttle Limit is measured. If an integration makes too many requests within this time window, additional requests are rejected until the window resets.
Default Value: 60 seconds
Range: 60 seconds
Enter the number of Concurrent Connections. This specifies the maximum number of simultaneous API connections that Copper CRM can process for a user or integration. If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.
Default Value: 5
Range: 10
Enter the number of Concurrent Batch Executions. This specifies the maximum number of simultaneous batch executions that can process for an integration at one time. If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.
Default Value: 5
Range: 10
Click Apply to save the settings.
After configuring your iPaaS.com subscription settings and saving them for HubSpot, open your subscription settings to initiate the OAuth 2.0 Flow.
To initiate the OAuth 2.0 Flow and generate an access token:
Go to your HubSpot Subscription Settings.
Click the Authentication icon:
A new browser window opens to the HubSpot login page
Sign in to proceed.
Select the account to authorize and then click Choose Account.
You will be redirected back to iPaaS.com.
Close the page and refresh your HubSpot subscription. If authentication was successful, you will now find access tokens saved to the OAuth details within the subscription settings:
NOTE: The HubSpot OAuth 2.0 access token is a permanent access token and does not expire. |
Post-Installation Verification
After completing the installation, perform these tests to verify the installation.
Data Sync Test
Initiate a sample data pull. (To iPaaS.com)
Initiate a sample data push. (From iPaaS.com)
Functionality Test
Run an end-to-end business process.
Validate key features like field mappings, workflow triggers, and logging.
Review integration logs in iPaaS.com.
Support and Troubleshooting
Click the Help button on any iPaaS.com page to contact Support or to search our documentation.
Documentation: Search our documentation at the top of this article
Support Portal: Click the Help and Support button at the lower-right of this window.
Contact Information: Contact iPaaS.com.





