All about HubSpot
HubSpot: Get products from HubSpot
Get products from HubSpot, with SKU, name, description and price, and send them to your webshop or another application.
Updated November 9, 2026
This flow gets products from HubSpot and sends them to another application, for example a webshop. Use it when HubSpot is the leading system for your products.
How it works
- APIcenter only gets products that changed after the date you set, the oldest change first. In each run, APIcenter gets at most the amount you set, by default 10. After each run, APIcenter sets the date to the modification date of the last product. If you set the date back, APIcenter gets products again.
- By default, APIcenter sends the SKU (
hs_sku) as product code, the name, the description, the price and the VAT amount. You add more fields under Data mapping. - Does a product have an image URL in the field
hs_images? Then APIcenter uses it as the image of the product. - APIcenter only processes variants if you set the product property for the main product. A product where this property contains the SKU of another product is a variant of that product. If you leave the property empty, APIcenter processes all products as separate products.
- Features and attributes come from two property groups in HubSpot: the group for features and the group for attributes. Each property in such a group is a feature or an attribute, with the label of the chosen option as value. This only works if you also set the property for the main product.
What you need first
- HubSpot is connected to APIcenter. See Connect HubSpot to APIcenter.
- For variants: a product property in HubSpot that holds the SKU of the main product.
- For features and attributes: property groups in HubSpot with the properties that you want to pass on.
- The other application in the integration can receive products.
Tips
- Is a product missing in the target system? Check if it changed after the date you set. If not, set the date back.
- The default data mapping does not contain stock and does not contain categories. If you need them, add them under Data mapping.
- If the product property for the main product does not exist in HubSpot, the flow stops with an error message. Check the name.
Below you find all settings of this flow, each with its own explanation.
Settings
The settings you see in the dashboard, with what each one does.
Default category name
CategoriesThis setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a category. The value is only used if Enable use of default category is on and you link the category yourself to a HubSpot property in the Data mapping. Leave the field empty.
Enable use of default category
CategoriesThis setting has no effect in the default data mapping to HubSpot. The HubSpot flows do not process product categories and the default data mapping does not send a category. You only need it if you link the category yourself to a HubSpot property in the Data mapping. Leave it off (default): if it is on without a value, the flow stops with an error message.
Force category on variant as parent
CategoriesThis setting has no effect for HubSpot. The HubSpot flows do not process product categories, so there is nothing to take over from the main product. Leave it off (default).
Force use of default category
CategoriesThis setting has no effect in the default data mapping to HubSpot, because the default data mapping does not send a category, so there is nothing to force. It only matters if you link the category yourself to a HubSpot property in the Data mapping. Leave it off (default).
Set category on variant as parent
CategoriesThis setting has no effect for HubSpot. The HubSpot flows do not process product categories, so there is nothing to take over from the main product. Leave it off (default).
Custom Product properties for the source application
Custom PropertiesThis setting has no effect. APIcenter does not use it in the HubSpot flows. If you want to get extra product fields from HubSpot, link them under Data mapping. Leave the field empty.
Use custom Product properties
Custom PropertiesThis setting has no effect. APIcenter does not use it in the HubSpot flows. If you want to get extra product fields from HubSpot, link them under Data mapping. Leave this setting off.
Enable URL Encoding of data in the endpoints of the source application
General flow settingEnable URL Encoding of data in the endpoints of the target application
General flow settingEnable URL encoding of data in endpoints
General flow settingTurns on URL encoding for values that APIcenter puts in the URL of a request to HubSpot. This prevents errors with special characters such as spaces, slashes or ampersands. In HubSpot, search values such as an e-mail address, SKU or deal name are in the content of the request and not in the URL; the URL only contains IDs and object types. So you rarely need this. This is the main switch: values are only encoded if you also turn on Enable URL Encoding of data in the endpoints of the source application (when getting) or Enable URL Encoding of data in the endpoints of the target application (when sending). Default: off.
Use administration mapping table
General flow settingThis setting has no effect for HubSpot. The data that APIcenter exchanges with HubSpot has no administration field, so there is nothing to map. Leave this setting off (default).
What to do with a value that cannot be mapped using the mapping table
General flow settingThis setting has no effect for HubSpot, because the data that APIcenter exchanges with HubSpot has no administration field. Leave it as it is.
Notifications Email address
NotificationsNotifications Slack webhook
NotificationsNotifications frequency
NotificationsReceive Notifications
NotificationsCreate missing properties in the target system
Product SettingsDecides if APIcenter creates a property or an option that does not exist in HubSpot. If this is off (default), the flow stops with an error message when a property or option is missing. If this is on, APIcenter creates the property or option in the group that you set. You can only add an option to a property that HubSpot has not locked; otherwise an error message follows.
Property category name to use for attributes
Product SettingsThe name of the property group in HubSpot that holds the properties for attributes, such as color or size, in which variants differ. For Get Product, APIcenter reads each property in this group as an attribute, with the label of the chosen option as value; this only works if you also set the property for the main product. For Send Product, APIcenter writes the attributes to properties in this group. If you leave this field empty, APIcenter does not process attributes.
Property category name to use for features
Product SettingsThe name of the property group in HubSpot that holds the properties for features of a product. For Get Product, APIcenter reads each property in this group as a feature, with the label of the chosen option as value; this only works if you also set the property for the main product. For Send Product, APIcenter writes the features to properties in this group. If you leave this field empty, APIcenter does not process features.
Property name or id of the property that holds the parent reference.
Product SettingsThe name or label of the product property in HubSpot that holds the SKU of the main product. For Get Product, APIcenter treats a product with a value in this property as a variant of the product with that SKU. For Send Product, a variant gets the SKU of the main product in this property. If the property does not exist, the flow stops with an error message, unless Create missing properties in the target system is on. If you leave this field empty, APIcenter processes all products as separate products, without variants.
Amount to process
Run behaviourThe maximum number of contacts, products or deals that APIcenter gets from HubSpot in each run. The default value is 10; you can choose a number from 1 up to and including 15. APIcenter gets the oldest changed records first. With a higher number, you clear a backlog faster, but each run takes longer.
From what date do you want to retrieve products?
Run behaviourThe date and time from which APIcenter gets contacts (Get Customer) or products (Get Product) from HubSpot. APIcenter only gets records that changed after this moment, the oldest change first. After each run, APIcenter sets the date to the modification date of the last record it got, so normally you do not need to change it. If you set the date back in time, APIcenter gets those records again and passes them on again. Default: 2025-01-01T00:00:00.
Last execution time
Run behaviourMaximum number of pages to retrieve
Run behaviourIn practice, this setting has no effect for HubSpot. The HubSpot flows ask for one list per run with their own limit (when getting data, this is Amount to process) and do not read extra pages. The default value is 20; you do not need to change it.
Offset
Run behaviourThis setting has no effect for HubSpot. Get Customer keeps track of where the flow stopped with the date from which contacts are retrieved, not with an offset. The default value is 0; you do not need to change it.
Run at specific times
Run behaviourUse page size
Run behaviourIn practice, this setting has no effect for HubSpot. The HubSpot flows decide themselves how many records they ask for per request: when getting data, this is Amount to process. The default value is 50; you do not need to change it.