Opens in a new tab
A kneeling worker measures a laundry doorway with a tape measure while a colleague holds a clipboard and pencil, with a large stainless-steel washing machine visible inside.
Marketing

HubSpot required deal fields still blank? What to check

Required fields are set, but important deal details are still missing. Check the rule, trace how the deal changed and test each route into your pipeline.

You have made a field required in HubSpot, yet deals still reach the next stage without the information your team needs. A quotation is ready, but nobody knows the installation requirements. A sale is marked won, but the delivery team has to chase basic details.

Start by identifying exactly where the requirement was configured and how the affected deal was created or updated. A field displayed on a record, a requirement during manual creation and a condition triggered by a stage change are different things. Integration behaviour also needs checking against the API version in use.

The aim is a dependable handover: collect information when it becomes necessary, keep genuine enquiries moving and make incomplete records visible to someone who can resolve them.

Start with one incomplete deal

Choose a recent example where the missing information caused extra work. Write down the deal, pipeline, stage, missing property and the point at which that information should have been available.

For example, a commercial laundry supplier might accept an initial enquiry without knowing the width of a customer’s access doorway. Before confirming delivery of a large machine, it needs the relevant access constraints. That is a sensible later-stage requirement. Making every early enquiry provide installation details would solve a different problem and could create unnecessary friction.

Check whether the value is genuinely absent. Is the information stored on the associated contact or company instead? Are two similarly named properties being confused? Agree which record should hold the answer before changing any rules.

Check which kind of requirement you actually set

A field on the create-deal form

HubSpot lets you choose fields for its manual record-creation panel and separately mark them as required. Adding a field to the panel does not itself require an answer. Its create-form guidance explains the required-field control and the subscription requirements: making properties required needs Starter, Professional or Enterprise.

Ask your administrator to inspect the Deals creation form and confirm that the intended property is marked required, the configuration is saved and any conditions match the example being investigated. Test creating a new deal through that panel. Do not use an existing deal as the only test of a creation requirement.

A requirement when entering a deal stage

HubSpot’s conditional stage-property guidance describes showing properties when users manually create a record in, or move one to, a selected stage. The dependent property must also have its Required checkbox selected to demand a value.

Check the exact pipeline and stage. A rule for your installation pipeline should not be assumed to cover a separate maintenance pipeline. Confirm which stages the condition includes and whether the missing property is the one selected in the rule.

Use a test deal with that field empty and attempt the relevant manual move. Record whether the prompt appears and whether leaving the answer blank prevents the save. A visible prompt alone is not sufficient evidence.

A condition based on another property

A requirement may depend on a selection such as service type or installation needed. Review the controlling value and every condition, rather than only the dependent field.

HubSpot’s current conditional-property documentation covers manual creation and editing across supported interfaces, including desktop and mobile. It explicitly says that this logic does not apply to edits made through other HubSpot tools such as workflows. The feature is listed for Professional and Enterprise subscriptions.

If your test involves a person changing a field but the affected deals are moved by a workflow, you have tested different routes. Keep both in the investigation.

Check the integration version before accepting old advice

Do not assume that every integration ignores required fields. HubSpot’s updated CRM API validation guidance specifies enforcement of configured conditional required properties from API version 2026-09, and enforcement of record-creation required properties on API creation requests. A missing required value can produce a 400 validation error.

The same guidance carries an important correction dated 27 October 2026: required associations remain enforced in the application interface, rather than public API write paths. Requiring a property and requiring an associated record are separate checks.

Ask whoever maintains the integration to identify its actual API version, the operation it performs, the applicable rule and the response received. Treat an import, a native workflow and an external integration as separate routes to verify.

Where validation rejects a request, correct the input before retrying, as HubSpot recommends. Keep the failed enquiry visible for recovery. Do not remove a useful requirement simply to make a connection report success.

Trace when the information disappeared

A blank field today does not establish that it was blank when the deal entered the stage. Investigate whether it was never supplied, supplied to a different property or cleared afterwards.

Open the deal and inspect the missing property’s history alongside the stage history. HubSpot’s property-history guide explains how to review changed values, dates and sources. You can inspect an individual property or use Actions, then View property history, for the record.

Build a short sequence from the evidence: the deal was created, its stage changed, the required detail was entered, then another update occurred. Where history identifies a workflow or integration, inspect that specific action and its input. Avoid changing every connected automation at once.

If different people’s details are being combined on the contact itself, investigate that separately using our guide to HubSpot forms overwriting contacts. A deal-field requirement will not resolve a wrong-person record.

Repair the route that needs the information

Choose the smallest change that addresses the confirmed cause. For manual entry, that might mean marking an already displayed field required or correcting the stage condition. For a workflow, review the decision immediately before the stage change and explicitly check that the necessary details are available.

For an integration, agree how it should handle an incomplete submission. Depending on your process, it could keep the deal at an earlier stage or place it in a visible review queue. Specify who follows up and what counts as resolved. A silent failure is not an acceptable handover.

Do not fill missing fields with invented answers, zero values or “N/A” merely to satisfy a rule. Those entries can hide the original problem from the next person. If an unknown value is legitimate at that stage, revise the business requirement openly.

Keep qualification and fulfilment requirements proportionate. The first conversation may need only enough information to respond usefully; a confirmed installation needs more. Decide that sequence with the people doing the work.

Test both incomplete and complete deals

Use clearly identified test records and prevent customer-facing messages or fulfilment actions from running during the checks. Test every route your business actually uses, including mobile entry, imports or integrations where relevant.

  • Incomplete manual entry: the intended requirement appears and prevents the relevant save.
  • Complete manual entry: a valid answer saves on the correct deal and allows the intended move.
  • Incomplete automated entry: the route rejects, holds or flags the record as designed, with someone responsible for recovery.
  • Complete automated entry: the expected deal is created or updated with its details intact.
  • Later updates: a subsequent synchronisation or workflow leaves the necessary information intact.

For each test, retain the record reference, route, result and relevant error or history entry. After the controlled checks, review a fresh genuine enquiry through to the team’s handover. A successful field save is only part of the outcome.

Clean up affected deals without changing their commercial history

Identify existing deals in the relevant stages with missing information and give their owners a focused correction list. Start with those awaiting an imminent quote, delivery or installation.

Recover answers from reliable correspondence or ask the responsible person. Do not move genuine won deals backwards solely to trigger a prompt, and do not replay a whole sales workflow to populate one field. Before making bulk corrections, check the downstream actions those updates could trigger.

When you use deal stages in marketing reports, document what each stage means and what evidence supports it. Our guide to connecting enquiries with sales reporting explains why those definitions matter when judging lead quality.

If required fields are failing to protect your sales handover, talk to BuzzBoost. We can help review how your website, CRM and automations pass enquiry details between them, then define the checks that demonstrate a reliable result.

Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.

Bolt AI — BuzzBoost Digital author avatar
Written by Bolt AI