Summary
An iPaaS.com Customer Category can be transferred to HubSpot, but it does not arrive as a record of its own. HubSpot has no customer category object, so the category becomes a value on a HubSpot dropdown property — the property named in the Contact Category Field Name or Company Category Field Name subscription setting. Each iPaaS.com category becomes one selectable value on that property, and the iPaaS.com category Name decides which of the two properties receives it.
ID Format
Manual Sync ID Format
Enter the iPaaS.com Customer Category id on the iPaaS.com Manual Sync page to transfer that category to HubSpot.
External ID Format
The external id linking an iPaaS.com Customer Category to HubSpot is the property value followed by _customer for a value on the contact property, or _company for a value on the company property. A category named Gold Customer|contact is therefore linked as Gold Customer_customer, and a category named Gold Customer|company is linked as Gold Customer_company. Because the link is built from the value rather than from a HubSpot record id, the same category name transferred to both objects produces two separate links.
Deleted Record Support
Outbound delete is not supported. Deleting a category in iPaaS.com does not remove the corresponding value from the HubSpot dropdown property, delete mappings are not included in the default templates, and deletions do not propagate in any form. This collection only ever adds a value. Removing an option from the HubSpot property is a manual action performed under a supervised process.
Custom Field Support
Custom fields are not supported for this collection. A custom field mapping added here does not reach HubSpot, because the destination is a property definition rather than a record that can carry custom properties.
Mapping Collection Status
Status: Enabled. Sync type is Add/Update, in the FROM iPaaS.com direction.
Trigger Events: This is a FROM iPaaS.com collection, so it is driven by iPaaS.com outbound triggers, which subscribers or their MiSP enable under Outbound Data Flows in the subscription configuration. Subscribe to the iPaaS.com Customer Category events that should dispatch a transfer. No automatic transfers occur until those subscriptions are enabled, and no HubSpot-side event triggers this collection. A category also transfers as a prerequisite ahead of a contact or company that carries a category assignment, so the property value exists before the record that references it — but only when the relevant category field name setting is populated. Manual Sync is available regardless.
Duplicate or Conflicting Mappings
No subscriber-selectable duplicate-handling option is presented for this collection. Before adding a value, the integration reads the property's existing values and checks whether the incoming value is already among them. If it is, the property is left untouched and no duplicate option is added. If it is not, the value is appended to the existing list.
The other collection that operates on the same entity is Add/Update HubSpot Customer Category TO iPaaS.com, the opposite-direction collection, which turns the HubSpot property's values into iPaaS.com customer categories. Because categories can transfer in both directions, subscribers or their MiSP should decide which system is authoritative for the category list before enabling both.
System Caveats
HubSpot Caveats
The property must exist and have at least one value: the property named in the setting must already exist in HubSpot as a Dropdown Select property with at least one value defined. A property with no values gives the integration nothing to build on.
The settings hold the property label: the integration matches on the property's label, not its internal name.
Values are added, never removed: this collection only ever adds a value to the property. A category removed in iPaaS.com leaves its HubSpot option in place.
A single property holds the designation: HubSpot holds one property per record type for the category designation, so a record carrying several iPaaS.com category assignments shows only one of them.
Rate limiting: at the time this documentation was written, the integration does not wait and retry when HubSpot throttles it. A throttled transfer fails and must be re-run. The failure is reported under Dashboard, Integration Monitoring, Error Logs.
iPaaS.com Caveats
The category name suffix determines the destination: the iPaaS.com category Name must be suffixed with a vertical bar and either contact or company — for example Gold Customer|contact or Gold Customer|company. The part before the bar becomes the value and label of the HubSpot option; the part after the bar routes the category to the contact property or the company property. A name with no suffix still yields an option label and value — the full name is used — but the object type cannot be determined, so the category has no property to be written to. Subscribers or their MiSP should name iPaaS.com categories with the suffix when those categories are intended to reach HubSpot.
Category hierarchies do not transfer: a HubSpot dropdown property is a flat list of values, so no parent or child relationship between iPaaS.com categories is represented.
Processing is opt-in per record type: an empty Contact Category Field Name or Company Category Field Name setting fully disables category processing for that record type, including the pre-processing that transfers a record's dependent categories. No error is raised.
Setup Requirements
HubSpot Configuration
Create the category property in HubSpot before any transfer is attempted. It must be a Dropdown Select type property with at least one value already defined.
Create a separate property for each record type that should carry a category designation — one on the Contact object, one on the Company object, or both.
Confirm the connected HubSpot account can edit property definitions.
iPaaS.com Configuration
Enable the iPaaS.com Customer Category outbound triggers under Outbound Data Flows on the subscription. No automatic transfers occur until they are enabled.
Populate Contact Category Field Name for the contact property and Company Category Field Name for the company property. Each setting must contain the property's label, not its internal name.
Name the iPaaS.com categories with the routing suffix described under iPaaS.com Caveats.
Authentication and connection setup are covered in HubSpot Installation Instructions and HubSpot Connections and Settings.
Integration Flow
An iPaaS.com Customer Category change, a manual sync, or a contact or company transfer that carries a category assignment dispatches the category transfer.
The part of the category name after the vertical bar decides which property is the destination: contact routes to the property named in Contact Category Field Name, and company routes to the property named in Company Category Field Name. When the relevant setting is empty, no property is resolved and processing for that record type stops without an error.
The integration retrieves the current definition of that dropdown property, including its existing list of values.
The incoming value — the part of the category name before the vertical bar — is checked against that list. If the value is already present, the property is left untouched and no further write occurs.
If the value is not present, it is appended to the list read in step 3 and the complete list is written back to the property, replacing the previous list in a single operation.
The external-id link is recorded on the iPaaS.com Customer Category so the value is recognised on later transfers.
Because step 5 replaces the whole value list rather than adding one value in isolation, the list written back is only as current as the list read in step 3. See Additional Notes for the consequences.
Mappings
Add/Update HubSpot Customer Category FROM iPaaS.com (Parent)
iPaaS.com data type: Customer Category
The mappings in this collection do not describe a customer. Because the destination is a HubSpot dropdown property rather than a record, they describe the property itself — its type, its field type, the group it appears in, and which HubSpot object it belongs to — together with the label, value, and description of the option being added to it.
Mapping Type | Source Field (iPaaS.com) | Destination Field (HubSpot) | Description |
Dynamic Formula |
| Model | Required. Determines which HubSpot object the category's property belongs to, so the value is added to the contact property or the company property. The formula reads the iPaaS.com category Name and splits it on the vertical bar. When the name carries a suffix — for example Gold Customer|contact — it returns the part after the bar, which must be contact or company. When the name has no bar, nothing is returned and the transfer has no object type to work with, so the category cannot be routed to a property. Name iPaaS.com categories with the |contact or |company suffix when they are intended to reach HubSpot. |
Dynamic Formula |
| FormField | Optional. Always returns true, marking the HubSpot category property as one that can be used on HubSpot forms. HubSpot does not require this value when a property is created; sending true simply makes the category available for form use. Change this mapping to return false if the category property should not be offered on forms. |
Dynamic Formula |
| GroupName | Required. Sets the HubSpot property group that the category property is displayed in. HubSpot requires a group whenever a property is created. The formula reads the iPaaS.com category Name, splits it on the vertical bar, and looks at the part after it. A suffix of company places the property in the company information group; a suffix of contact places it in the contact information group. A category name with no suffix produces no group, which is another reason to follow the naming convention described in the Model note. |
Dynamic Formula |
| Option_Label | Required. The text shown in the HubSpot dropdown for this category. The formula reads the iPaaS.com category Name, splits it on the vertical bar, and returns the part before it — so Gold Customer|contact is displayed as Gold Customer. When the name has no bar, the whole name is used as the label. |
Field | Description | Option_Description | Optional. Copies the iPaaS.com category description onto the HubSpot dropdown option as its description, which appears as helper text where HubSpot shows option details. If the iPaaS.com category has no description, no description is set on the option. |
Dynamic Formula |
| Option_Value | Required. The value HubSpot stores on the record when this option is selected. The formula is the same as the one used for Option_Label: it splits the iPaaS.com category Name on the vertical bar and returns the part before it, falling back to the whole name when there is no bar. Keeping the value identical to the label means the value stored on the HubSpot record reads the same as the text shown in the dropdown, and it is also the value the integration matches on when checking whether the option already exists. |
Static |
| FieldType | Required. Sets how the HubSpot category property is presented — select produces a dropdown from which one option can be chosen. Together with the Type mapping's enumeration value, this is HubSpot's Dropdown Select property, which is the property type the category property must be created as. This value should be left as it is; changing it produces a property HubSpot will not accept category options for. |
Static |
| Type | Required. Sets the HubSpot category property's data type to a fixed set of options, which is what allows the property to carry the category values. Together with the FieldType mapping's select value, this is HubSpot's Dropdown Select property. This value should be left as it is. |
Error Handling
The errors this collection can raise are catalogued, with their causes and resolutions, in HubSpot Error Messages. Rather than repeat them here, the entries most relevant to category transfers are:
HubSpot API Communication: covers the messages raised when HubSpot rejects or cannot receive a property write, including the rate limit case. At the time this documentation was written, the integration does not wait and retry when HubSpot throttles it, so a throttled transfer fails and must be re-run.
Category property errors: raised when the property named in Contact Category Field Name or Company Category Field Name does not exist in HubSpot, or is not a Dropdown Select property with at least one value defined. Correct the property in HubSpot, or clear the setting to disable category processing for that record type, then re-sync the category.
Errors are reported under Dashboard, Integration Monitoring, Error Logs.
Testing & Validation
Test Scenarios
Create an iPaaS.com Customer Category named with the contact suffix — for example Gold Customer|contact — and manually sync it by its iPaaS.com Customer Category id. Confirm the value appears as a new option on the HubSpot property named in Contact Category Field Name, and that the option's label and value are the part of the name before the bar.
Repeat with a category named with the company suffix and confirm the value reaches the property named in Company Category Field Name instead.
Re-sync a category that has already transferred. Confirm no duplicate option is added and the existing options are unchanged.
Sync a category whose name carries no suffix. Confirm no property value is written and no error is raised.
Clear the Contact Category Field Name setting and sync a contact-suffixed category. Confirm category processing stops with no error raised, then restore the setting and confirm the value transfers.
Assign a transferred category to an iPaaS.com Customer and transfer that customer. Confirm the category value existed on the HubSpot property before the contact referenced it, and that the contact carries the designation.
Add an option directly in HubSpot, then sync a new iPaaS.com category. Confirm which options are present on the property afterward, and re-run the transfer if a value is missing.
Validation Checklist
A first transfer adds the category value as an option on the correct HubSpot property.
A second transfer of the same category adds no duplicate option.
The suffix after the vertical bar routes the value to the contact property or the company property as expected.
A category name with no suffix produces no property value and no error.
An empty category field name setting disables processing for that record type without raising an error.
Existing options on the property are still present after a transfer.
Errors appear under Dashboard, Integration Monitoring, Error Logs.
Additional Notes
At the time this documentation was written, only one HubSpot property holds the category designation for each record type, so only one of the iPaaS.com category assignments on a customer or company is reflected in HubSpot. When several assignments are provided, the last one processed becomes the final value of the HubSpot property and the others are not represented. This feature is best suited to a single category assignment per customer or company. Subscribers or their MiSP who need several categories per record should plan to hold the additional designations in separate HubSpot properties populated through custom field mappings on the Customer or Company collections.
At the time this documentation was written, adding a value to the HubSpot property is a read-then-write operation: the integration reads the property's full list of values, appends the new one, and writes the whole list back. It does not check whether the list changed in between. Two category transfers running at the same time can therefore result in one of the new values being lost, and a value added directly in HubSpot between the read and the write can be dropped. Subscribers or their MiSP should avoid running category transfers concurrently, and avoid editing the property in HubSpot while a category transfer is in progress. Where values appear to be missing, re-running the transfer restores them.
At the time this documentation was written, values are added, never removed. Deleting a category in iPaaS.com, or removing a category assignment from a record, does not remove the option from the HubSpot property.
Creating the HubSpot property itself is out of scope. The property must be created manually in HubSpot beforehand as a Dropdown Select property with at least one value defined.
Category hierarchies are out of scope. A HubSpot dropdown property is a flat list of values, so no parent or child relationship between categories is transferred.
Transferring HubSpot property values to iPaaS.com is handled by Add/Update HubSpot Customer Category TO iPaaS.com.