Skip to Content
IntegrationsAPNDisconnecting

Disconnecting APN

This page shows how to disconnect APN, what that changes, how to reconnect, and how to remove the connector from your AWS account.

Disconnect

You need the tenant owner or admin role.

  1. Go to Settings → Integrations → APN.
  2. Click Disconnect.
  3. Click Confirm disconnect.

Result: the page shows Not connected and the Set up APN connector button.

Over MCP, use disable_apn_integration.

What disconnecting changes

  • FlowState sends nothing more to Partner Central. Changes to your HubSpot deals are not sent, and Submit and Save & submit on the deal card show “APN is disconnected”.
  • FlowState no longer receives changes from Partner Central for your tenant.
  • The scheduled APN sync stops.
  • Your AWS account is released, so another FlowState tenant can connect it.

What stays:

  • The ExternalId. It does not change, so the trust policy of your connector role stays valid. To issue a new one, use rotate_apn_external_id over MCP, and then update the trust policy with the new value.
  • Opportunities in Partner Central. FlowState never deletes them.
  • The APN properties on your HubSpot deals. They keep their last values.
  • The link between each deal and its opportunity. When you reconnect, FlowState does not create the opportunities again.
  • The audit log.
Note

Disconnecting does not remove your connector role from AWS. If you stop using APN sync, remove the connector from AWS.

Pause when HubSpot is disconnected

If you disconnect HubSpot, APN sync pauses. FlowState keeps the APN connection, but sends nothing to AWS and ignores changes from AWS. Settings → Integrations → APN shows Paused — HubSpot disconnected.

When you connect HubSpot again, APN sync starts again, with a catch-up sync that reads the opportunities that changed in the meantime.

Reconnect

The ExternalId has not changed, so you do not need to change anything in AWS.

  1. Go to Settings → Integrations → APN and click Set up APN connector.
  2. Click Start setup.
  3. On the Deploy module step, choose the same catalog as before. Do not deploy the connector again. Click I’ve deployed the module.
  4. Paste the role ARN of your existing connector role, click Test connection, then Continue.

Result: the wizard shows You’re connected. FlowState runs a catch-up sync: it sends the current values of your linked deals to AWS and reads the opportunities that changed in AWS while you were disconnected. A deal that you did not submit before you disconnected stays unsubmitted until you click Submit on its card.

Remove the connector from AWS

If you stop using APN sync, remove the connector from the AWS account that is linked to Partner Central:

  • CloudFormation: delete the APN connector stack.
  • OpenTofu: run tofu destroy in the connector directory.
  • Manual connector: delete what the Manual tab of the wizard had you create: the EventBridge rule FlowStateAPNEvents<Catalog> and the catalog lock parameter (both in us-east-1), and the roles FlowStateAPNConnector<Catalog> and FlowStateAPNEventForward<Catalog> in IAM.

Deleting the stack removes the connector role, the event-forwarding role, the EventBridge rule and the catalog lock. The catalog is then free for another FlowState tenant. The AWS managed policies need no clean-up.

Removing the connector does not change FlowState’s data: the HubSpot property values and the audit log stay.

Updating the connectorTroubleshooting