HubSpot: Send products to HubSpot

This setting has no effect in the default data mapping to HubSpot. APIcenter writes attributes to the property group that you set in Property category name to use for attributes, and not to an attribute set. The value is only used if you link the attribute set yourself to a HubSpot property in the Data mapping.

This setting has no effect in the default data mapping to HubSpot. APIcenter writes features to the property group that you set in Property category name to use for features, and not to a feature set. The value is only used if you link the feature set yourself to a HubSpot property in the Data mapping.

This setting has no effect in the default data mapping to HubSpot, because the default data mapping does not send an attribute set, so there is nothing to force. It only matters if you link the attribute set yourself to a HubSpot property in the Data mapping. Leave it off (default).

This setting has no effect in the default data mapping to HubSpot, because the default data mapping does not send a feature set, so there is nothing to force. It only matters if you link the feature set yourself to a HubSpot property in the Data mapping. Leave it off (default).

This setting has no effect in the default data mapping to HubSpot. The default data mapping to HubSpot does not send a feature set. You only need it if you link the feature set yourself to a HubSpot property in the Data mapping of the flow. Leave it off (default): if it is on without a value, the flow stops with an error message.

Use a mapping table to link the names and values of attributes from the other application to the names and options of HubSpot properties. APIcenter searches for the property in the group that you set in Property category name to use for attributes, by name or label. Values that are not in the table are handled according to What to do with a value that cannot be mapped using the mapping table. Default: off.

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send an attribute set, so there is nothing to map. You only need the mapping table if you link the attribute set yourself to a HubSpot property in the Data mapping. Leave it off (default).

Use a mapping table to link the names and values of features from the other application to the names and options of HubSpot properties. APIcenter searches for the property in the group that you set in Property category name to use for features, by name or label. Values that are not in the table are handled according to What to do with a value that cannot be mapped using the mapping table. Default: off.

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a feature set, so there is nothing to map. You only need the mapping table if you link the feature set yourself to a HubSpot property in the Data mapping. Leave it off (default).

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send an attribute set. It only decides what happens if you use the mapping table for attribute sets yourself: Use default (default) uses the default value, Use value passes on the original value and Ignore value leaves the field empty.

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a feature set. It only decides what happens if you use the mapping table for feature sets yourself: Use default (default) uses the default value, Use value passes on the original value and Ignore value leaves the field empty.

This 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.

This 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.

This 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).

This 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).

This 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).

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a category, so there is nothing to map. You only need the mapping table if you link the category yourself to a HubSpot property in the Data mapping. Leave it off (default).

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a category. It only decides what happens if you use the mapping table for categories yourself: Use default (default) uses the default value, Use value passes on the original value and Ignore value leaves the field empty.

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a price list group. The value is only used if Enable use of a default customer price list group is on and you link the price list group yourself to a HubSpot property in the Data mapping. Leave the field empty.

This setting has no effect in the default data mapping to HubSpot. The default data mapping to HubSpot does not send a price list group. You only need it if you link the price list group yourself to a HubSpot property in the Data mapping of the flow. Leave it off (default): if it is on without a value, the flow stops with an error message.

This setting has no effect in the default data mapping to HubSpot, because the default data mapping does not send a price list group, so there is nothing to force. It only matters if you link the price list group yourself to a HubSpot property in the Data mapping. Leave it off (default).

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a price list group, so there is nothing to map. You only need the mapping table if you link the price list group yourself to a HubSpot property in the Data mapping. Leave it off (default).

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a price list group. It only decides what happens if you use the mapping table for price list groups yourself: Use default (default) uses the default value, Use value passes on the original value and Ignore value leaves the field empty.

Turns 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.

This 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).

This setting has no effect for HubSpot, because the data that APIcenter exchanges with HubSpot has no administration field. Leave it as it is.

This setting has no effect for HubSpot. APIcenter does not use it in the HubSpot flows, so you can leave it as it is.

Decides 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.

This setting has no effect. APIcenter does not use it in the HubSpot flows: a variant that does not exist yet is always created. You can leave it as it is. Default: off.

The 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.

The 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.

The 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.

Decides what happens if a product with the same SKU (hs_sku) already exists in HubSpot. If this is off (default), APIcenter does not update the product and the flow reports that the product may not be updated. If this is on, APIcenter updates the existing product. With Update product name, Update product description and Update product images, you decide which fields are overwritten.

This setting has no effect for HubSpot. For Send Product, APIcenter does not send images to HubSpot, even if the data mapping contains images. You can leave it as it is.

In 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.

In 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.

This setting has no effect in the default data mapping to HubSpot. The HubSpot flows do not use a warehouse and the default data mapping does not send one. You only need it if you link the warehouse yourself to a HubSpot property in the Data mapping of the flow. Leave it off (default): if it is on without a value, the flow stops with an error message.

This setting has no effect in the default data mapping to HubSpot, because the default data mapping does not send a warehouse, so there is nothing to force. It only matters if you link the warehouse yourself to a HubSpot property in the Data mapping. Leave it off (default).

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a warehouse, so there is nothing to map. You only need the mapping table if you link the warehouse yourself to a HubSpot property in the Data mapping. Leave it off (default).

This setting has no effect in the default data mapping to HubSpot. The default data mapping does not send a warehouse. The value is only used if Enable the use of a default warehouse is on and you link the warehouse yourself to a HubSpot property in the Data mapping. Leave the field empty.

This setting has no effect in the default data mapping to HubSpot. The HubSpot flows do not use a warehouse. It only decides what happens if you use the mapping table for warehouses yourself: Use default (default) uses the default value, Use value passes on the original value and Ignore value leaves the field empty.

This setting has no effect in the default data mapping to HubSpot. The default data mapping to HubSpot sends the VAT amount (tax) and no VAT code or tax class. The VAT amount is calculated from the amounts in the data or, if the rate is not in them, from Default tax rate prices. Leave this setting off (default): if it is on without a value for Value for the default tax id (exclude '%'), the flow stops with an error message.

This setting has no effect in the default data mapping to HubSpot. The default data mapping to HubSpot sends the VAT amount (tax) and no VAT code or tax class. Leave this setting off (default).

This setting has no effect in the default data mapping to HubSpot, so there is nothing to map. The default data mapping to HubSpot sends the VAT amount (tax) and no VAT code or tax class. You only need the mapping table if you link a tax class yourself to a HubSpot property in the Data mapping. Leave it off (default).

This setting has no effect in the default data mapping to HubSpot. The default data mapping to HubSpot sends the VAT amount (tax) and no VAT code or tax class. You only need this field if you link a tax class yourself to a HubSpot property in the Data mapping. Leave the field empty.

This setting has no effect in the default data mapping to HubSpot. The default data mapping to HubSpot sends the VAT amount (tax) and no VAT code or tax class. It only decides what happens if you use the mapping table for tax classes yourself: Use default (default) uses the default value, Use value passes on the original value and Ignore value leaves the field empty.