Skip to content

HubSpot required properties and quote saves

Why a quote save can stop with a message from HubSpot about a required property or a rule, and what to change so it goes through.

HubSpot lets your admins require properties on deals, quotes, line items, companies, and contacts, either always or only when another property has a certain value (a conditional required property). HubSpot now applies those rules to every change an integration makes, not only to edits made in the HubSpot record page. Quotivity writes quotes, line items, and deal fields through HubSpot, so a save that breaks one of your rules is rejected by HubSpot and Quotivity shows you HubSpot’s reason.

Nothing about your quotes changed. The difference is that a rule which used to apply only to people editing records in HubSpot now also applies to Quotivity.

Quotivity passes HubSpot’s own message through, so it names the property or rule involved. Depending on where the save happened:

  • In Quote Builder, the save fails and a red message appears, for example “Property ‘contract_term’ is required when ‘billing_frequency’ is set”. The edit is not saved until the rule is satisfied.
  • When a background update stops, the quote shows the same message and the update is not applied. This happens when a quote rule or a bundle change updates line items after you leave the builder.
  • When a quote is set to sync later (the HubSpot sync indicator shows pending changes), opening or publishing the quote reports “Failed to sync quote changes to HubSpot” followed by HubSpot’s message.
  1. Read the message. It tells you which property HubSpot wants and, for a conditional rule, which other property triggered it.
  2. Fill in that property on the record in HubSpot, or in Quote Builder if it is a quote or line item column your admin made editable.
  3. Save again. Quotivity retries the write with the same values, so once the property is set the save goes through.

If the rule should not apply to quotes at all, ask a HubSpot admin to review it under the object’s property settings in HubSpot. Quotivity does not fill in properties that a HubSpot rule requires, and it does not bypass the rule.

Rule in HubSpot Applies to Quotivity saves
Required property on a record type Yes, when Quotivity creates that record
Conditional required property Yes, when the condition is met by the values being saved
Required fields on the Create record form Yes, when Quotivity creates the record
User permission to edit associations Yes, for the user whose HubSpot account installed or connected Quotivity

Rules on objects Quotivity never writes, such as tickets, do not affect quotes.