HubSpot Troubleshooting
Symptom-by-symptom fixes for HubSpot connection errors, missing deals, failed writes, and configuration problems
Overview
Work down to your symptom. If nothing here fixes it, contact us — include the exact error text and the time it happened.
Connection problems
"Authorization code not found"
HubSpot sent you back without completing the authorization — usually because the consent screen was closed or cancelled.
Fix: Go to Settings → HubSpot, click Connect to HubSpot, and complete the flow without navigating away or opening it in a second tab.
"Invalid state parameter"
Steve couldn't match HubSpot's response to your organization. The authorization carries your Steve organization ID with it, so it has to start from Steve.
Fix: Reload app.hiresteve.ai/settings?tab=hubspot, confirm the correct organization is selected in Steve, and start again from the Connect to HubSpot button. Never start from the HubSpot App Marketplace.
"Failed to fetch access token"
HubSpot rejected the exchange of the authorization code for a token. Codes are single-use and short-lived.
Fix: Retry immediately without leaving the consent screen open. If it repeats, the app may not be approved for your portal — ask your HubSpot super admin.
"Failed to verify HubSpot connection"
A token was issued but Steve couldn't confirm it against HubSpot.
Fix: Retry once. If it persists, check whether your HubSpot portal restricts app installs, and have a super admin run the authorization.
"Internal server error occurred" / "Unknown error occurred"
Something failed that Steve doesn't have a specific message for.
Fix: Check HubSpot's notification bar for a declined-permission notice, retry once, then contact tech@hiresteve.ai with the timestamp.
The HubSpot page redirects me to Projects
Your Steve role category is Individual Sales. The CRM pages are limited to sales management and PMM roles, and you'll see "Integration Not Available."
Fix: Ask an organization manager to change your role, or have them do the CRM work.
Setup and configuration problems
The amber "New Steve fields need to be created" banner
steve_connected_calls or steve_connected_battle_cards is missing from your portal — usually because the connecting HubSpot user couldn't create deal properties.
Fix: Click Create missing fields in the banner. If that fails too, create them by hand as multi-line text properties in the Deal information group, using those exact internal names.
The amber "Re-integrate to enable deal activity notes" banner
Your connection was authorized before Steve requested crm.objects.contacts.write, which HubSpot requires for creating Notes.
Fix: Click Re-integrate on the settings card and complete the authorization. Nothing is deleted; only the stored scopes are updated.
Field creation reports failures
The connected HubSpot user lacks property-management rights, or a property with that internal name already exists with a different type.
Fix: Check Settings → Properties → Deal Properties in HubSpot. If the property exists, skip creation and just map to it. Otherwise reconnect as a user who can manage properties.
A property I just created in HubSpot isn't in the dropdown
The property list is cached from HubSpot.
Fix: Click Refresh Properties on the Field Mapping page. HubSpot can also take a moment to expose a brand-new property over its API — wait thirty seconds and refresh again.
Save Configuration is greyed out
All six Steve fields must be mapped to real properties, and at least one property must be selected.
Fix: Look at the Configuration Status card — fields still missing a green check are the ones to fix. A field mapped to a property that no longer exists in HubSpot counts as unmapped.
Sync problems
No deals imported at all
| Check | How |
|---|---|
| The right portal is connected | The settings card shows the connection; re-integrate against the correct portal if not. |
| The portal actually has deals | Open HubSpot and confirm. |
| The connected user can see those deals | Deals in a portal or team the user has no access to won't import. |
| The sync has had time to run | It's asynchronous. Click Sync HubSpot Data, wait, then Refetch. |
Some deals are missing
The sync is incremental after the first run — it only fetches deals modified since the last import.
Fix: Touch the missing deals in HubSpot to bump their last-modified date, then click Sync HubSpot Data.
A property is blank in Steve but has a value in HubSpot
It isn't in your selected properties, so it was never fetched.
Fix: Add it on the Field Mapping page and save — saving triggers a sync with the new selection.
Companies never appeared
Sync HubSpot Data in the deals table is deals-only. Companies sync on connect, on saving field mapping, and on the daily run.
Fix: Save your field mapping again, or wait for the next daily run.
The deals table shows "Failed to load HubSpot deals"
Steve couldn't read its own copy of the deals — usually a transient error.
Fix: Refresh the page. If it persists, contact support with the message.
Write-back problems
Competitors won't select — the cell is disabled
The deal has no project. Competitor annotation is project-scoped.
Fix: Assign a project in the Project column first. The tooltip on the disabled cell says the same thing.
The competitor list is empty for a deal
The deal's project has no competitors, or the competitors you expect belong to a different project.
Fix: Add competitors to that project, or reassign the deal to the right one.
Battle card links appear in the property but not on the timeline
Missing the crm.objects.contacts.write scope.
Fix: Click Re-integrate in settings.
Steve Channels / Win Reason / Loss Reason cells are read-only
Those fields are editable only when mapped.
Fix: Map them on the Field Mapping page.
Edits save in Steve but don't appear in HubSpot
The field is mapped to a property that no longer exists, or the connected user lost write access to it.
Fix: Re-check the mapping, and confirm in HubSpot that the property is editable and not read-only or calculated.
A deal shows the wrong project after sync
Your mapped Steve Project property holds a project ID that doesn't exist in your organization. Steve logs a warning and leaves the deal unassigned rather than breaking the import.
Fix: Correct the value in HubSpot, or unmap Steve Project and assign projects in Steve instead.
AI feature problems
No deal suggestions are generated
| Cause | Fix |
|---|---|
| Your organization has no projects | Create a project with competitors, then sync so new deals are analyzed. |
| The deals already existed | Only newly inserted deals are analyzed, once each. |
| The deals were updated, not created | Same — updates don't trigger analysis. |
Extracted playbook fields never reach HubSpot
The call isn't annotated to a deal, or — for company fields — Steve couldn't match a company from the call's participants.
Fix: Annotate the call to a deal in Sales Calls, and confirm participants exist as HubSpot contacts linked to a company. See CRM Field Extraction.
HubSpot rejects an extracted dropdown value
The field mapping was created before Steve stored the property's allowed values, so the model was guessing.
Fix: Delete and re-add the extraction field so its allowed values are captured from the property.
Still stuck?
Head to Support with:
- Your Steve organization name and HubSpot portal ID
- The exact error message, word for word
- What you were doing when it happened, and roughly when
- A screenshot of the relevant screen