Overview

This article catalogs the error messages subscribers or their MiSP may encounter with the iPaaS.com HubSpot integration, what causes each one, and how to resolve it. Each error carries a stable code — for example HUBS-EXTN-1001 — shown in bold next to its message. You can search this page (Ctrl+F / ⌘+F) for a code to jump straight to the entry that explains it.

Your Managed Integration Service Provider (MiSP) is the party that configures and maintains this integration for you — they own the field mappings, the connection credentials and settings, and the reconciliation of records between HubSpot and iPaaS.com. Several resolutions below are things the MiSP is best placed to check first.

Errors are recorded in the iPaaS.com portal under Dashboard → Integration Monitoring → Error Logs. Where a message shows a value in braces (for example {id} or {sku}), HubSpot or the integration fills in the specific record detail at runtime, so the message in the Error Logs will contain the actual value.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Supported Flows

The flows below each have at least one error source described in this article:

Connection and authorization
Add/Update HubSpot Contact TO iPaaS.com
Add/Update HubSpot Contact FROM iPaaS.com
Add/Update HubSpot Company TO iPaaS.com
Add HubSpot Company FROM iPaaS.com
Update HubSpot Company FROM iPaaS.com
Add HubSpot Order FROM iPaaS.com
Update HubSpot Order FROM iPaaS.com
Add/Update HubSpot Product FROM iPaaS.com
Add/Update HubSpot Customer Category TO iPaaS.com
Add/Update HubSpot Customer Category FROM iPaaS.com

In addition, the HubSpot API Communication, Record Identifiers, and Batch Processing errors described below can appear in any flow, including the Customer Address, Company Address, Customer Relationship, Company Relationship, and Transaction Line Item flows.

Error Collection

Connection & Authorization

A successful connection test does not confirm that the credentials work. Authorization problems surface on the first real transfer rather than at connect time, so subscribers or their MiSP should confirm a new connection by running an actual transfer and reviewing the Error Logs.

Authorization could not be completed — application credentials missing

HUBS-AUTH-1001 - Unable to complete OAuth process in ProcessAuthorization. ClientId is not specified in the CustomFields for this SystemTypeVersion (and the equivalent HUBS-AUTH-1002 ClientSecret message)

Description: The authorization was started, but the HubSpot application credentials the integration needs to complete it were not available. These credentials are configured on the iPaaS.com side of the integration, not in the subscription's own settings, so this is not something a subscriber or MiSP supplies.
Resolution: This one cannot be corrected from the subscription. Contact iPaaS.com Support at support@ipaas.com — the integration's application configuration needs to be corrected before authorization can be completed.

Authorization could not be completed — token exchange failed

HUBS-AUTH-1003 - Unable to complete OAuth process in ProcessAuthorization. Failed to convert temporary code into a permanent token

Description: HubSpot issued a temporary authorization code, but that code could not be exchanged for a usable access token. This is most often caused by an authorization that was left open too long, an authorization code that was already used, or the HubSpot account cancelling the app install partway through.
Resolution: Start the authorization again from the beginning so HubSpot issues a fresh code, and complete the HubSpot consent screen without pausing. Confirm the HubSpot user completing the authorization has access to the intended HubSpot account and can grant the requested scopes. If it continues to fail after a clean re-authorization, ask your MiSP to confirm the connection, and if it still fails, Contact iPaaS.com Support.

A webhook subscription update could not be completed

HUBS-INTL-1002 - Unable to locate HubSpot Call Wrapper while updating Webhook Subscription

Description: The integration attempted to update a HubSpot webhook subscription and could not establish the connection it needed to do so. At the time this documentation was written, HubSpot contacts, companies, and category values reach iPaaS.com through scheduled polling rather than through webhook notifications, so this condition is not part of the normal transfer path and is not expected on a standard subscription.
Resolution: This condition cannot be corrected from the subscription settings. Contact iPaaS.com Support, noting the date and time the error appeared in the Error Logs.

HubSpot API Communication

Errors in this section can appear in any flow, because every entity transfer ultimately calls the HubSpot API.

HubSpot returned a structured error

HUBS-EXTN-1001 - Error Status: {status} / Error Message: {message} / Error CorrelationId: {id} / Error Category: {category} / Error AdditionalErrors JSON: {details}

Description: HubSpot rejected the call and returned a description of why. This is the message subscribers or their MiSP see for most HubSpot rejections. The Error Message is HubSpot's own explanation — for example an invalid property value, a property that does not exist on the HubSpot object, or a missing permission. Error Category groups the failure, and Error CorrelationId is HubSpot's unique reference for that specific request. Error AdditionalErrors JSON carries any further detail HubSpot returned and is not formatted for reading.
Resolution: Read the Error Message and correct the indicated value on the source record, then re-sync. If the message points at a HubSpot property, have your MiSP confirm that property exists on the HubSpot object and that the connected app has permission to write it. The table below describes the classes of rejection this integration surfaces, identified by the HTTP status HubSpot returns for each:

HTTP status	What it usually means	What to do
400 / 409 / 422	HubSpot rejected the data in the request — an invalid value, a required property with no value, or a value that conflicts with an existing HubSpot record.	Correct the indicated value on the source record and re-sync.
401 / 403	The connection's authorization is invalid, expired, or the connected app is missing a scope the call requires.	Re-authorize the HubSpot connection. If the failure repeats immediately after re-authorizing, Contact iPaaS.com Support.
404	The HubSpot record the integration tried to read or update no longer exists — commonly because it was deleted or merged in HubSpot after it was linked.	Confirm the record still exists in HubSpot. If it was deleted, the link to it is stale and the record must be transferred again as a new record.
429	Too many requests were sent to HubSpot in a short window. At the time this documentation was written, the integration does not automatically wait and retry when HubSpot throttles it, so the transfer fails rather than slowing down.	Re-run the affected transfers. Avoid running several large manual syncs at the same time, and stagger bulk jobs.
500 / 502 / 503	HubSpot had a server-side problem. Usually transient.	Re-run the transfer. If it persists, check HubSpot's status page.

If the cause is still unclear after reading HubSpot's response, Contact iPaaS.com Support and include the Error CorrelationId — HubSpot Support can trace the exact request from that value.

A common specific case — an order line item cannot carry both a discount amount and a discount percentage. When this appears it arrives as HUBS-EXTN-1001 with Error Category: VALIDATION_ERROR and the message Cannot set both discount '{value}' and discountPercentage '{value}' (HubSpot's detail is CANT_SET_BOTH_VALUE_AND_PERCENT). HubSpot does not allow a single order line item to carry both a discount amount and a discount percentage; when a transferred line supplies both, the entire order fails to transfer, not only the affected line. The integration's standard line item mappings no longer send both — the discount amount is transferred and the percentage is intentionally left empty — so the configuration the integration ships with does not produce this error. It can still occur where the Add/Update HubSpot Order Line Item FROM iPaaS.com mappings have been changed to send the discount percentage alongside the amount. Resolution: send only one of the two. Leave the line item DiscountPercentage mapping returning no value, as the integration ships it. If a percentage-based discount is required on the HubSpot line instead, map the percentage and remove the discount-amount mapping — never both — then re-sync the order. Your MiSP owns this mapping change.

HubSpot rejected the request without a readable explanation, or could not be reached

HUBS-EXTN-1002 - Request failed with status code {status}

Description: The call to HubSpot failed and the integration could not read a structured reason. Either HubSpot returned a rejection with no readable body — the message then reports only the status as a word, for example Request failed with status code Unauthorized, NotFound, or TooManyRequests — or the call never reached HubSpot at all (a network, DNS, or TLS failure), in which case the message is the underlying communication error. A misconfigured API Url on the subscription is a common cause of the second kind.
Resolution: If the message shows a status word, match it against the table above — BadRequest is 400, Unauthorized 401, Forbidden 403, NotFound 404, TooManyRequests 429 — and take the action for that row. If it is a communication error, have your MiSP confirm the API Url setting on the HubSpot subscription is correct and reachable, then re-run the transfer; a single occurrence is usually transient. If it repeats after that, Contact iPaaS.com Support with the message and the time it appeared in the Error Logs.

Customer

Customer could not be linked to an existing iPaaS.com customer by email

HUBS-BIZL-1001 - Unable to dynamically link to existing customer using email address. This may result in duplicate customer records.

Description: A HubSpot contact had no link to an iPaaS.com customer yet, so the integration searched iPaaS.com for a customer with the same email address, found one, and attempted to link the two records. The link did not save as expected. Without the link, the next transfer will create a new customer instead of updating the existing one, which is why the message warns about duplicates. Email matching is exact — a customer whose email differs by so much as a trailing space is treated as a different customer. Applies to Add/Update HubSpot Contact TO iPaaS.com and FROM iPaaS.com.
Resolution: Search iPaaS.com and HubSpot for customers with that email address. If a duplicate was created, merge or remove it, then re-sync the customer so the link can be established. If the link still cannot be saved, ask your MiSP to check the record's linkage; if it remains unresolved, Contact iPaaS.com Support.

A related contact could not be transferred before the customer (TO iPaaS.com)

HUBS-BIZL-1003 - Unable to create Customer Relationship Contact Id: {id}. This will prevent the transfer of the contact id: {id}.

Description: The HubSpot contact being transferred has a relationship to another contact that does not exist in iPaaS.com yet. The integration transfers that related contact first, and that prerequisite transfer failed — so the original contact cannot proceed.
Resolution: Find the error for the related contact, which is reported separately in the Error Logs, and resolve it. Then re-sync the original contact. The related contact's own error is the actual cause; this message only reports the consequence.

A related company could not be transferred before the customer (TO iPaaS.com)

HUBS-BIZL-1004 - Unable to create Customer Relationship Company Id: {id}. This will prevent the transfer of the contact id: {id}.

Description: The HubSpot contact being transferred is associated with a company that does not exist in iPaaS.com yet. The integration transfers that company first, and that prerequisite transfer failed — so the contact cannot proceed.
Resolution: Resolve the company's own error, reported separately in the Error Logs, then re-sync the contact.

A related record could not be transferred before the customer (FROM iPaaS.com)

HUBS-BIZL-1007 - Unable to create company to customer association id: {id}. This will prevent the transfer of the customer.

Description: The iPaaS.com customer being transferred to HubSpot has a relationship to another customer or company that has not been transferred to HubSpot yet. The integration attempts that related record first, and it failed — so the customer cannot proceed.
Resolution: Resolve the related record's own error, reported separately in the Error Logs, then re-sync the customer. Related records are only transferred automatically when they are active in iPaaS.com — an inactive related record is skipped rather than transferred, and will not produce this error.

Company

Company could not be linked to an existing iPaaS.com company by name

HUBS-BIZL-1002 - Unable to dynamically link to existing company using name. This may result in duplicate company records.

Description: A HubSpot company had no link to an iPaaS.com company yet, so the integration searched iPaaS.com for a company with the same name, found one, and attempted to link the two records. The link did not save as expected, so the next transfer may create a duplicate company rather than updating the existing one. Name matching is exact. This same message can also appear while a contact or company category is being linked by name, since those flows resolve their match the same way. Applies to Add/Update HubSpot Company TO iPaaS.com.
Resolution: Search both systems for companies (or categories) with that name. If a duplicate was created, merge or remove it, then re-sync so the link can be established. If the link still cannot be saved, ask your MiSP to check the linkage; if it remains unresolved, Contact iPaaS.com Support.

A related contact could not be transferred before the company (TO iPaaS.com)

HUBS-BIZL-1005 - Unable to create Company Relationship Contact Id: {id}. This will prevent the transfer of the company id: {id}.

Description: The HubSpot company being transferred is associated with a contact that does not exist in iPaaS.com yet. The integration transfers that contact first, and that prerequisite transfer failed — so the company cannot proceed.
Resolution: Resolve the contact's own error, reported separately in the Error Logs, then re-sync the company.

A related company could not be transferred before the company (TO iPaaS.com)

HUBS-BIZL-1006 - Unable to create Company Relationship Company Id: {id}. This will prevent the transfer of the company id: {id}.

Description: The HubSpot company being transferred is associated with another company that does not exist in iPaaS.com yet. The integration transfers that related company first, and that prerequisite transfer failed — so the original company cannot proceed.
Resolution: Resolve the related company's own error, reported separately in the Error Logs, then re-sync the original company.

A related record could not be transferred before the company (FROM iPaaS.com)

HUBS-BIZL-1008 - Unable to create company to customer association id: {id}. This will prevent the transfer of the company.

Description: The iPaaS.com company being transferred to HubSpot has a relationship to a customer or another company that has not been transferred to HubSpot yet. The integration attempts that related record first, and it failed — so the company cannot proceed.
Resolution: Resolve the related record's own error, reported separately in the Error Logs, then re-sync the company. Related records are only transferred automatically when they are active in iPaaS.com; an inactive related record is skipped and will not produce this error.

Relationships

Relationship transfers do not raise their own errors when the record they point at is missing. The Add/Update HubSpot Contact Association TO iPaaS.com, Add/Update HubSpot Company Association TO iPaaS.com, Add/Update HubSpot Contact Association FROM iPaaS.com, Add HubSpot Company Association FROM iPaaS.com, and Update HubSpot Company Association FROM iPaaS.com collections each carry a filter that checks whether the record the relationship depends on has already been transferred. When that record has not been transferred, the relationship is skipped for that run — nothing is written and no error is logged.

If an expected relationship is not appearing in the destination system and there is no corresponding entry in the Error Logs, this skip is the most likely explanation. Transfer the customer or company the relationship depends on first, then re-sync the relationship.

Relationship flows can still produce the HubSpot API Communication, Record Identifiers, and Batch Processing errors described elsewhere in this article.

Transaction

These errors occur in the Add HubSpot Order FROM iPaaS.com and Update HubSpot Order FROM iPaaS.com flows, where the integration transfers a transaction's dependencies to HubSpot before the transaction itself.

Customer could not be transferred before the transaction

HUBS-BIZL-1013 - Unable to create customer id: {id}. This will prevent the transfer of the order.

Description: The iPaaS.com transaction references a customer that does not exist in HubSpot yet. The integration transfers that customer first, and that transfer failed — so the transaction cannot proceed. This prerequisite always runs; it is not controlled by any subscription setting.
Resolution: Resolve the customer's own error, reported separately in the Error Logs, then re-sync the transaction. The customer is only transferred automatically when it is active in iPaaS.com — if it is inactive, transfer it to HubSpot manually first, or activate it, then re-sync the transaction.

Company could not be transferred before the transaction

HUBS-BIZL-1014 - Unable to create company id: {id}. This will prevent the transfer of the order.

Description: The iPaaS.com transaction references a company that does not exist in HubSpot yet. The integration transfers that company first, and that transfer failed — so the transaction cannot proceed. This prerequisite always runs; it is not controlled by any subscription setting.
Resolution: Resolve the company's own error, reported separately in the Error Logs, then re-sync the transaction. As with the customer, an inactive iPaaS.com company is not transferred automatically.

Product could not be transferred before the transaction

HUBS-BIZL-1015 - Unable to create product sku: {sku}. This will prevent the transfer of the order.

Description: A line on the iPaaS.com transaction references a product SKU that does not exist in HubSpot yet. The integration transfers that product first, and that transfer failed — so the transaction cannot proceed. This prerequisite only runs when the Transfer Products as a Prerequisite for Transactions setting is enabled.
Resolution: Resolve the product's own error, reported separately in the Error Logs, then re-sync the transaction. If products should not be transferred automatically, set Transfer Products as a Prerequisite for Transactions to false and create the products in HubSpot ahead of the transaction instead. Note that this setting only recognizes the exact value true — values such as 1, yes, or on silently turn the behavior off.

Product could not be transferred before the transaction after resolving a variant SKU

HUBS-BIZL-1016 - Unable to create product sku : {sku} having variant sku: {sku} in line item. This will prevent the transfer of the order.

Description: A transaction line's SKU did not match any iPaaS.com product, so the integration looked it up as a product variant instead, found it, and attempted to transfer the variant's parent product to HubSpot. That parent product transfer failed — so the transaction cannot proceed. The message shows both SKUs: the parent product's SKU first, then the variant SKU that appeared on the line.
Resolution: Resolve the parent product's own error, reported separately in the Error Logs, then re-sync the transaction. HubSpot receives the parent product, not the variant, so confirm the parent product's data is complete and valid in iPaaS.com.

Record Identifiers

These errors appear when a record identifier supplied to the integration is not in the form the entity expects. They most often occur on the Manual Sync page, where the identifier is typed by hand.

Invalid key value

HUBS-VALD-1001 - Invalid key value at {location}. MappingCollectionType = {type}, ExpectedDataType = {expected}, PKValue = {value}

Description: The identifier supplied for the record is not in the format that entity requires. The message reports the expected format and the value that was supplied. Three formats are used across the HubSpot entities: a plain numeric id; an id containing exactly one separator character; and an id containing exactly two separator characters. Address, category, and relationship records use the separated forms because a single value is not enough to identify them.
Resolution: Compare the value shown in PKValue against the expected format shown in ExpectedDataType and re-enter the identifier in the correct form. The mapping documentation for the entity being synced shows its identifier format. If the value looks correct and the error persists, ask your MiSP to confirm the identifier format for that entity.

Invalid data passed to a record identifier

HUBS-VALD-1002 - Invalid data passed to {location}: {value}

Description: The identifier supplied for the record could not be interpreted at all — for example, text where a numeric id is required, or an identifier missing the separator segments the entity needs.
Resolution: Re-enter the identifier using the format shown in that entity's mapping documentation, then re-sync. If the error persists with a value that appears correct, ask your MiSP to confirm the identifier format for that entity.

Batch Processing

Batch processing stopped after an error

HUBS-EXTN-1003 - Received an exception during batch run of {action}. {message}

Description: The integration groups certain HubSpot calls and runs them together to improve throughput. When one call in a group fails and the operation cannot safely continue with a partial result, the whole group stops and the error from the first failed call is reported alongside the name of the operation that was running.
Resolution: Read the underlying error included in the message and resolve it — it is one of the HubSpot API Communication errors described above, and the same error is usually reported separately in the Error Logs with more detail. Correct the indicated data and re-sync. Because the group stopped early, records after the failure were not attempted and will be picked up on the re-sync.

Internal Errors

The integration raises a further set of messages that report an internal condition rather than something in the subscriber's data or configuration.

Unexpected data or an unhandled condition

HUBS-INTL-1001 - {App} {Operation}.Body {Entity}{Operation}Request encountered an error: {message}

Description: The integration received something it could not process while assembling a record into a HubSpot request — usually an unexpected value, a value of an unexpected type, or a combination of fields the integration does not handle. It is reported during a Customer, Company, Product, or Transaction transfer.
Resolution: This is a data fault rather than a missing feature — check the record that was being transferred. If it contains unusual values — very long text, unexpected characters, or a field left in an unusual state — correcting those and re-syncing is worth attempting first. If the record looks correct, have your MiSP review the mappings for that entity; if it remains unresolved, note the record and the time the error appeared in the Error Logs and Contact iPaaS.com Support.

Deleted records

Description: Deleting records is not supported by this integration in either direction, for any entity. A delete that reaches the integration stops with an internal error rather than removing anything.
Resolution: Handle deletions manually in each system. See HubSpot Known Limitations for the full description of this constraint.

HubSpot Error Messages