Connect HubSpot to Kanopee

When you connect HubSpot

Each Kanopee company is connected to one HubSpot portal. During initial setup, Kanopee sends you to HubSpot to approve the connection and then returns you to Kanopee to continue setup.

If the connection later needs to be refreshed—for example, because access was revoked or Kanopee needs permissions that were not present on an older installation—you can reconnect from Settings.

What Kanopee needs access to

The current HubSpot connection is designed to let Kanopee read and update the CRM information required by supported workflows.

At a customer level, that includes access needed to:

• work with Contacts, Companies, Deals and Tickets
• read HubSpot owners
• read and manage supported list membership
• read forms used by form-submission workflows; and
• perform the CRM updates selected in your workflow actions.

The exact authorization screen is controlled by the HubSpot app configuration. If an older connection is missing a permission that Kanopee now uses, reconnecting can refresh the authorization.

What happens after you authorize HubSpot

After you approve the connection in HubSpot, Kanopee processes the authorization and associates the portal with the relevant Kanopee account.

During initial onboarding you will then choose a plan and continue through setup. Kanopee syncs the HubSpot metadata it uses in the workflow editor, including properties, owners, teams, forms, lists, pipelines and stages.

If the connection succeeds but something is missing in a dropdown later, use Sync Kanopee with HubSpot before reconnecting.

If HubSpot does not connect

If the HubSpot connection fails:

1. Return to Kanopee and start the connection again.
2. Make sure you are authorizing the intended HubSpot portal.
3. If Kanopee reports that HubSpot is not connected, use the Connect HubSpot or Reconnect HubSpot control shown in Setup or Settings.
4. If the portal is connected but forms, properties, owners or stages are missing, run a metadata sync.
5. If forms or another newly supported capability still cannot be read after syncing, reconnecting may be required to refresh permissions.

If repeated connection attempts fail, the issue may need support investigation rather than another workflow edit.

---