HubSpot Account Requirements
What has to be true in HubSpot and in Steve before the integration can be connected and start syncing
Overview
Most failed HubSpot setups are permissions, not configuration. Work through this checklist before you click Connect to HubSpot — it takes two minutes and saves a support ticket.
Who it's for: 📣 PMM / admin.
On the Steve side
| Requirement | Details |
|---|---|
| A Steve account | Sign up and sign in at app.hiresteve.ai. |
| An organization | CRM integrations are configured per organization, not per user. The authorization carries your organization ID with it. |
| Organization manager role | Only an org manager can connect, configure, or delete an integration. |
| A role that isn't Individual Sales | The HubSpot pages are gated. If your Steve role category is Individual Sales, you're redirected to Projects and see "Integration Not Available — HubSpot integration is only available for sales management and PMM teams." |
| At least one project | Deal suggestions and competitor annotation are project-scoped. With no projects, Steve imports deals but skips suggestion generation entirely. |
A single-project shortcut. If your organization has exactly one project, every imported deal is auto-assigned to it. With two or more projects, deals arrive unassigned and you assign them yourself — or let Deal Suggestions propose one.
On the HubSpot side
| Requirement | Details |
|---|---|
| A HubSpot account with a CRM | Any HubSpot tier that has Deals. Free CRM works for the basic deal sync. |
| Permission to install apps | Your HubSpot user needs app-install rights. If your HubSpot super admin has locked down the Marketplace, ask them to run the authorization or pre-approve the Steve app. |
| Access to the deals you expect to see | The authorization is scoped to the HubSpot account you sign in with. Deals in a portal you don't have access to won't import. |
| Deal property edit rights | Steve creates custom deal properties on your behalf. A user without property-management rights can authorize, but the auto-created fields will silently fail and you'll have to create them by hand. |
| The right portal selected | If you belong to several HubSpot accounts, HubSpot asks you to choose one during authorization. Pick the portal that holds the deals you want in Steve. |
The scopes you'll be asked to approve
The consent screen lists these. Read Connecting HubSpot for what each one is used for.
oauth
crm.objects.deals.read crm.objects.deals.write
crm.schemas.deals.read crm.schemas.deals.write
crm.objects.companies.read crm.objects.companies.write
crm.schemas.companies.read crm.schemas.companies.write
crm.objects.contacts.read crm.objects.contacts.write
crm.objects.contacts.writeis what writes notes. It's the scope HubSpot requires for the Notes and Call engagement objects Steve creates on the deal timeline. If your connection predates that scope, Steve shows a "Re-integrate to enable deal activity notes" banner in settings — one click fixes it and no data is lost.
The custom deal properties Steve needs
Two are created automatically when you authorize:
| Internal name | Label | Type | Group |
|---|---|---|---|
steve_connected_calls | Steve Connected Calls | Multi-line text | Deal information |
steve_connected_battle_cards | Steve Connected Battle Cards | Multi-line text | Deal information |
Six more are yours to create — automatically from Steve, or by hand in HubSpot. Defaults:
| Internal name | Label | Purpose |
|---|---|---|
steve_channels | Steve Channels | Which channels Steve is being used in |
steve_usage | Steve Usage | How Steve is being used on this deal |
loss_reason | Loss Reason | Why the deal was lost |
win_reason | Win Reason | Why the deal was won |
project_competitor | Project Competitor | The competitors annotated on this deal |
steve_project | Steve Project | The Steve project this deal belongs to |
You can point Steve at existing HubSpot properties instead of creating new ones — see Field Mapping. The names above are just the defaults Steve offers.
One HubSpot account, one Steve organization
A HubSpot portal is stored against a single Steve organization. Connecting the same portal from a second organization overwrites the first organization's tokens. If two teams need the same portal, talk to us at tech@hiresteve.ai first.
Quick pre-flight check
- I'm signed in to Steve as an organization manager
- My Steve organization has at least one project with competitors
- I can install apps in the HubSpot portal I want to connect
- I can create and edit deal properties in that portal
- I know which HubSpot portal holds the deals I want in Steve
Next Steps
- Connecting HubSpot — the OAuth flow and what gets stored.
- Field Setup Instructions — create the six Steve properties.
- Troubleshooting — if the checklist passed and it still fails.