Skip to Content
IntegrationsHubSpotTroubleshooting

HubSpot troubleshooting

Token expired (HubSpot 401)

Symptom: the pipeline pages stop showing new data, or Test connection on Settings → Integrations → HubSpot shows an error. The status still reads connected: FlowState does not change the status when HubSpot rejects its authorisation, and it sends no email.

Cause: HubSpot ended the authorisation. This happens after about six months without use, or when a HubSpot Super Admin uninstalls the app.

Fix:

  1. Open Settings → Integrations → HubSpot.
  2. Click Disconnect, then Connect HubSpot, and approve the app in HubSpot.
  3. Check that the status reads connected and that Test connection shows a deal.

The APN link of each deal and the APN property values are kept.

HubSpot needs new permissions

Symptom: Settings → Integrations → HubSpot shows the banner HubSpot needs new permissions, or the deal analysis fails with a missing-permission error.

Cause: FlowState now asks for a permission that your connection does not have yet.

Fix: click Reconnect HubSpot in the banner and approve the new permission in HubSpot. You do not have to disconnect first. See Missing permissions.

Permission errors (HubSpot 403)

Symptom: HubSpot is connected, but reading deals or writing properties fails with a permission error.

Cause: the HubSpot user who connected FlowState could not grant every permission, or a HubSpot admin restricted the app later.

Fix:

  1. Click Disconnect on Settings → Integrations → HubSpot.
  2. Ask a HubSpot Super Admin to click Connect HubSpot.
  3. On HubSpot’s consent page, check that all 12 permissions are listed before clicking Connect app. See Permissions & scopes.

Property provisioning failed

Symptom: after Provision properties, FlowState shows Property provisioning failed. and some APN properties are missing in HubSpot.

Cause: a property with the same internal name already exists in HubSpot with a different type, for example apn_mrr as text instead of a number.

Fix:

  1. In HubSpot, open Settings → Properties and search for the property name.
  2. Delete the conflicting property if nobody uses it, or rename it.
  3. In FlowState, click Provision properties again.

Do not use Deprovision to fix this. It deletes all APN properties and their values.

A deal change does not reach AWS

Symptom: you changed a deal in HubSpot, but AWS Partner Central does not show the change.

Check, in this order:

  1. The deal was submitted. FlowState sends changes to AWS only after the deal has been submitted from the card (Submit to AWS or Save & submit), or auto-submitted by a template. See The HubSpot card.
  2. Wait a minute. FlowState waits a few seconds after the last edit, so that several edits become one update to AWS.
  3. The property triggers a sync. Changes to the deal name, stage, close date, amount and the APN properties your team edits are sent. Properties FlowState writes itself, such as APN Sync Status, never trigger a sync.
  4. APN sync with AWS is on. The deal’s APN Sync with AWS enabled property is Yes. An empty value counts as No.
  5. APN is connected and not paused. Settings → Integrations shows the APN integration as connected, not paused — HubSpot disconnected.
  6. The card shows no error. Open the deal’s FlowState tab. If the card shows APN sync failed, the details say what AWS rejected. See APN troubleshooting.

If all of this is in order, contact support at support@copebit.ch.

DisconnectingAPN