Quick answer
The Contact Owner feed setting was removed in Gravity Forms HubSpot Add-On 3.0.4 because the HubSpot Forms API no longer supports that assignment. Verify that the contact still arrives, then use an assignment method supported by your current HubSpot account. Do not recreate the removed option with an unsupported request.
Determine whether this is a delivery or assignment failure
Find one recent test entry in Gravity Forms and match it to the intended HubSpot account using its email and timestamp. Use an address you control or a sanctioned test identity, not a real prospect whose ownership could change during testing.
If no contact or submission arrived, inspect the feed result before working on routing. A missing required field, wrong portal, or failed connection is a delivery issue. If the contact arrived but has no owner, you have a later-stage assignment issue. Write down which boundary actually failed.
Document the old business rule
Ask sales operations what the old owner setting was meant to accomplish. Was every inquiry assigned to one person, or did custom code choose someone based on region, service, campaign, or an existing relationship? A missing dropdown is often the first time anyone has written that rule down.
Also identify the fallback. A lead without a country, an unknown service value, or an inactive salesperson should land somewhere that is monitored. The correct fallback is not necessarily a random owner. It may be a shared review process with an explicit response-time expectation.
Choose a supported assignment mechanism
Review the workflows and assignment features available in the current HubSpot account. Availability and permissions vary, so do not assume every account has the same automation tools. Where automation is unavailable, define an accountable manual triage step instead of silently dropping assignment.
Keep the form responsible for collecting and delivering the agreed routing inputs. Keep the CRM assignment rule responsible for deciding ownership. This separation makes it possible to change the sales roster without redeploying form code. It also makes a routing failure visible independently of a delivery failure.
Test existing contacts as well as new ones
A new contact assigned correctly does not prove the rule is safe. Test a contact that already has an owner and decide whether another inquiry should preserve or replace that relationship. Use a sandbox or a clearly isolated test segment before activating broad enrollment.
Next, test an unowned contact, an incomplete routing value, and a repeat submission from the same test address. Record the expected owner before running each case. Inspect the contact history after processing so a later rule cannot quietly overwrite the result you saw initially.
- New contact with complete routing fields.
- Existing contact with a protected owner relationship.
- Incomplete or unrecognized routing information.
- Repeated submission that should not create ownership churn.
Review custom integrations deliberately
The vendor also deprecated owner-related helper methods and other API arguments associated with the old behavior. Search maintained custom plugins and snippets for the named deprecated interfaces in the release notes. Do not edit the add-on package directly or delete code only because a name looks similar.
For each match, identify its callers and intended outcome. Replace unsupported behavior with a documented mechanism and add a regression test. If the code is no longer used, remove it through the normal deployment process with a rollback revision, not by experimenting in the production editor.
Make the handoff observable
A useful lead handoff record contains the form entry ID, CRM contact ID, routing fields, selected rule, resulting owner, and processing timestamp. Store only what your organization needs and apply its retention policy. Do not create a second uncontrolled customer database for debugging.
After activation, review a small sample of legitimate submissions with sales operations. Measure whether the lead reached the correct queue and received attention, not merely whether the automation ran. A technically successful sync that leaves nobody responsible for the lead is still an operational failure.
Explain the change to the team
Tell the form administrator that the removed option is an intentional integration change, not evidence of a lost license. Tell sales staff where the replacement assignment rule lives and who can change it. Record the review date and the account features used so future support can understand the implementation.
Do not promise that older lead ownership will be automatically repaired. Historical cleanup needs its own scope, review, and safeguards against overwriting valid relationships. Keep that work separate from restoring correct handling of new inquiries.
Illustrative diagnostic worksheet. Use your own test results.When to bring in help
Use WordPress CRM integration support when the form feed works but sales ownership is unpredictable. Bring the form ID, mapped routing fields, and an example contact timeline. Keep account credentials and real lead details out of the support brief.
Related troubleshooting
Verify the form inputs used by routing rules.
Helpful references
Gravity Forms HubSpot 3.0.4 release notes.