Symptom

When a HubSpot workflow with a Send SMS action runs, it fails immediately with the following error:

Invalid integration error in hubspot

This error typically appears in the action logs after the Aircall-HubSpot integration has been reinstalled, even when:

  • The user who installed the integration has full admin/super admin permissions in HubSpot and Aircall.
  • The Aircall-HubSpot integration shows as Active in Aircall Dashboard > Integrations > Apps.
  • Calls and SMS are logging normally from Aircall to HubSpot.

Cause

When you initially set up Aircall’s Send SMS action in your HubSpot Workflow, you are prompted to select an Aircall number from which messages will be sent to the enrolled Contacts/Companies. The selected Aircall Number is stored in HubSpot with a reference to a specific HubSpot integration instance ID.

When the Aircall-HubSpot integration is reinstalled, a new integration instance is created with a new ID. Any existing Send SMS actions in workflows still reference the old, now-deleted integration instance ID. However, that instance no longer exists, so HubSpot returns an "Invalid integration" error when the action is triggered, even though the current Aircall-HubSpot connection is valid and active.

On reviewing the Send SMS action that is producing the "Invalid integration" error, you may see a set of ID numbers listed in the Aircall number field instead of the Aircall number name.

Invalid integration error - cause message

For example, the above ID 17016-36022 represents:

  • 17016 = the ID of that specific integration connection
  • 36022 = the ID of the Aircall number

Solution

To resolve the error, you’ll need to remove and re-add the Send SMS action in your HubSpot Workflow to map it to the current integration instance:

  1. Open the impacted workflow in HubSpot.
  2. Delete the Send SMS action from the workflow entirely.
  3. Re-add the Send SMS action to the workflow.
  4. In the Aircall Number field, reselect the number from which you would like to send messages.
  5. Save and test the workflow.

If the error persists after these steps, please contact Aircall Support with the processId for the error appearing in the workflow Action Log, along with the timestamp for the outbound message attempt.