HubSpot error messages

Find the message you see in HubSpot below, then follow the checks in order. The first two checks fix most of these errors.

The checks, in order

1. Check status.portant.co. If everyone on your team sees the same error at the same time, it is likely a platform problem. See Is Portant down?
2. Reconnect HubSpot. Go to Settings → Permissions and reconnect HubSpot. Your HubSpot workflows keep working after a reconnect. See Reconnect HubSpot.
3. Reconnect Google. A HubSpot error can come from the Google side, because Portant reads the template and saves the output in Google Drive. See Reconnect your Google account.
4. Check your active team. If you belong to more than one Portant team, make sure that the team you are working in is the one connected to this HubSpot portal.
5. Check the object. For a HubSpot workflow action, the object that HubSpot enrolls (for example Deal) must be the same as the source object of the Portant workflow.

Something went wrong

You may also see An unknown error has occurred. This general error does not name the cause. Work through all five checks above, then try the workflow again from the record. If it still fails, run the same workflow from the Portant app: in the workflow's Source tab, search for the record, then run it. If the run fails in Portant too, the Outputs page has a support code you can send us.

There was a problem reaching the app's API

You may also see couldn't get a response from the connected app. HubSpot could not get an answer from Portant. Check the status page first. If there is no incident, reconnect HubSpot and then reconnect Google (checks 2 and 3).

Refused to connect

The Portant card or window inside HubSpot could not load. This often comes from a browser extension or a privacy setting that blocks content from other sites.

1. Reload the HubSpot page.
2. Allow app.portant.co in any ad blocker or privacy extension, or try a private window.
3. If the error continues for everyone on your team, check the status page.

Authorization failed

The HubSpot connection belongs to your Portant team. The team owner or an Admin manages it, and teammates use the same connection. So when the connection expires, every teammate sees this error.

Ask the team owner or an Admin to reconnect HubSpot at Settings → Permissions. If the person who connected HubSpot has left your company, see Reconnect HubSpot: the connecting admin has left.

The Portant card is empty or keeps loading

1. Reload the HubSpot record.
2. Reconnect HubSpot (check 2). This also refreshes the list of workflows that HubSpot can see.
3. If the card loads but your workflow is not in it, see My workflow isn't showing in HubSpot.

The Run a Portant workflow action does nothing

• Object mismatch. The action runs only a Portant workflow whose source object is the same as the object the HubSpot workflow enrolls. A Deal-based HubSpot workflow cannot run a Portant workflow with a Contact source.
• Two Portant accounts on one portal. A HubSpot portal connects to one Portant workspace. If two Portant accounts are connected to the same portal, the action can fail with no error. Keep one connection.
• Expired connection. An action that stays on waiting with no delay step is a sign of an expired connection. Reconnect HubSpot.

For how to set up the action, see Add a Portant action to a HubSpot workflow.

Still not working?

Copy a support code from the Outputs page if the item appears there, take a screenshot of the error in HubSpot, and contact us.