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

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

Resolution: Contact iPaaS.com Support — the integration's application configuration needs to be corrected before authorization can be completed.

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 is able to grant the requested scopes. If the authorization continues to fail, Contact iPaaS.com Support.

Description: The integration attempted to update a HubSpot webhook subscription and could not establish the connection it needed to do so. Whatever step triggered the update stops. 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.

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 (for example a validation problem versus a permission problem), 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, confirm that property exists on the HubSpot object and that the connected app has permission to write it. Error Category names the class of problem HubSpot assigned to the failure. The table below describes the classes of rejection this integration surfaces, identified by the HTTP status HubSpot returns for each, and what to do about them:

Description: HubSpot rejected the call, but the response carried no explanation the integration could read — either the response body was empty, or it was not in the form HubSpot's error responses normally take. The message reports only the status HubSpot returned, written as a word rather than a number: for example Request failed with status code Unauthorized, Request failed with status code NotFound, or Request failed with status code TooManyRequests. A rejection with no readable body is most common on authorization and rate limit failures.

Resolution: Match the status word against the table above — BadRequest corresponds to 400, Unauthorized to 401, Forbidden to 403, NotFound to 404, and TooManyRequests to 429 — and take the action shown for that row. If the status word is not one of those, or the failure repeats after that action, Contact iPaaS.com Support with the message and the time it appeared in the Error Logs.

Description: The call to HubSpot failed before HubSpot could return a status — a network, DNS, or TLS failure. The message is the underlying communication error rather than anything HubSpot produced. A misconfigured API Url on the subscription is a common cause.

Resolution: Confirm the API Url setting on the HubSpot subscription is correct and reachable. Re-run the transfer; a single occurrence is usually transient. If it repeats, Contact iPaaS.com Support.

Description: The integration could not complete a call to the iPaaS.com platform. These calls look up an iPaaS.com record, or resolve the link between a HubSpot record and its iPaaS.com counterpart. When one fails, the transfer that depends on it stops.

Resolution: Re-run the transfer; an isolated occurrence is usually transient. If the error repeats, Contact iPaaS.com Support with the Http Code and the time the error appeared in the Error Logs.

Description: The integration matched a HubSpot record to an iPaaS.com record but could not save the link between the two. Because the link is what prevents the record from being created a second time, this condition carries a risk of duplicates on the next transfer.

Resolution: Check whether the record now exists in both systems and whether a duplicate was created. Merge or remove any duplicate, then re-sync so the link can be saved. If the error repeats, Contact iPaaS.com Support.

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. The message warns that this may result in duplicate customer records, because without the link the next transfer will create a new customer instead of updating the existing one.

Applies to: Add/Update HubSpot Contact TO iPaaS.com and Add/Update HubSpot Contact FROM iPaaS.com. Email matching is exact — a customer whose email differs by so much as a trailing space is treated as a different customer.

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, Contact iPaaS.com Support.

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.

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.

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. The wording of this message refers to a company; when it appears during a customer transfer, it is reporting the customer's related record.

Resolution: Resolve the related record's own error, reported separately in the Error Logs, then re-sync the customer. Note that 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.

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. The message warns that this may result in duplicate company records, because without the link the next transfer will create a new company rather than updating the existing one.

Applies to: Add/Update HubSpot Company TO iPaaS.com. Name matching is exact.

Resolution: Search both systems for companies with that name. If a duplicate was created, merge or remove it, then re-sync the company so the link can be established. If the link still cannot be saved, Contact iPaaS.com Support.

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.

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.

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.

Description: The HubSpot contact being transferred carries a category that does not exist in iPaaS.com yet, and no iPaaS.com category with that name was found to link to. The integration transfers the category first, and that transfer failed — so the contact cannot proceed.

Resolution: Resolve the category's own error, reported separately in the Error Logs, then re-sync the contact. Confirm the Contact Category Field Name setting on the subscription names an existing HubSpot contact property, matched on the property's Label.

Description: The HubSpot company being transferred carries a category that does not exist in iPaaS.com yet, and no iPaaS.com category with that name was found to link to. The integration transfers the category first, and that transfer failed — so the company cannot proceed.

Resolution: Resolve the category's own error, reported separately in the Error Logs, then re-sync the company. Confirm the Company Category Field Name setting on the subscription names an existing HubSpot company property, matched on the property's Label.

Description: The iPaaS.com customer being transferred to HubSpot carries a category that does not exist as an option on the HubSpot contact category property yet. The integration adds the category option first, and that failed — so the customer cannot proceed. The id shown in this message is the customer's, not the category's.

Resolution: Confirm the Contact Category Field Name setting names an existing HubSpot contact property and that the property accepts new options. Resolve the category's own error, reported separately in the Error Logs, then re-sync the customer. If this setting is left empty, contact category transfer is skipped entirely and this error will not occur.

Description: The iPaaS.com company being transferred to HubSpot carries a category that does not exist as an option on the HubSpot company category property yet. The integration adds the category option first, and that failed — so the company cannot proceed. The id shown in this message is the company's, not the category's.

Resolution: Confirm the Company Category Field Name setting names an existing HubSpot company property and that the property accepts new options. Resolve the category's own error, reported separately in the Error Logs, then re-sync the company. If this setting is left empty, company category transfer is skipped entirely and this error will not occur.

Description: A HubSpot category had no link to an iPaaS.com category yet, so the integration searched iPaaS.com for a category with the same name, found one, and attempted to link the two. The link did not save as expected, so a duplicate category may be created on the next transfer. This condition can arise while transferring either a contact or a company, since both flows resolve their categories the same way. The message wording refers to a company record; when it appears during a category link it is reporting the category.

Resolution: Check whether a duplicate category was created in iPaaS.com and remove it, then re-sync the record so the link can be established. If the link still cannot be saved, Contact iPaaS.com Support.

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 the customer is inactive, transfer it to HubSpot manually first, or activate it, then re-sync the transaction.

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.

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 at all, 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.

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.

Description: 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, HubSpot rejects it and the entire order fails to transfer, not only the affected line. The integration's standard line item mappings no longer send both values: 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 HubSpot Order Line Item FROM iPaaS.com or 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, so that only the discount amount transfers. If a percentage-based discount is required on the HubSpot line instead, map the percentage and remove the discount-amount mapping — never map both. After adjusting the mapping, re-sync the order.

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, Contact iPaaS.com Support.

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, Contact iPaaS.com Support.

Description: The integration groups certain HubSpot calls and runs them together to improve throughput. When one call in a group fails and the operation is one that 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. At the time this documentation was written, the number of calls run together is not subscriber-configurable.

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.

Description: These messages report that the integration received something it could not process. Recognizable examples include messages stating that a call was made "with unhandled parameters", that a parameter type or endpoint type is "unsupported", that a table name could not be determined, or that an operation is "not implemented". They are usually caused by a record that could not be assembled into a valid HubSpot request — an unexpected value, a value of an unexpected type, or a combination of fields the integration does not handle.

Important: A message reporting that an operation is not implemented during a Customer, Company, Product, or Transaction transfer does not mean the feature is unsupported. At the time this documentation was written, this wording is also used when a record fails to assemble into a request, which is a data problem rather than a missing feature. Treat it as a data fault and check the record that was being transferred.

Resolution: Note the record that was being transferred and the time the error appeared in the Error Logs, then Contact iPaaS.com Support. If the record 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.

Description: Deleting records is not supported by this integration in either direction, for any entity. A delete that reaches the integration reports that the operation is not implemented.

Resolution: Handle deletions manually in each system. See HubSpot Known Limitations for the full description of this constraint.