The Aircall and HubSpot integration allows you to dynamically set the HubSpot call engagement type based on Aircall tags. This configuration is managed in the Event type section of the integration settings and lets you override default HubSpot call type rules when specific tags are applied to a call.
This article explains how tag-based mapping works, how to configure it, and important behaviors to be aware of.
How tag-based call type mapping works
In the Event type section, found under Call type settings in the Aircall and HubSpot integration, you can map:
Aircall tags
To HubSpot call types, including both default and custom call types
The mapping is dynamic. This means:
If call types are added, modified, or removed in HubSpot, the available options in the Aircall Dashboard update automatically.
The mapping applies only when a configured tag is present on the call.
Note: Only one HubSpot call engagement type can be applied per call activity.
Configuring tag to call type mapping
Only Admins can configure this setting.
Steps
Select HubSpot.
Navigate to the Call type settings section.
In the Event type section, click Add call type.
-
Select:
One Aircall tag from the predefined list.
One HubSpot call type to map it to.
Save your changes.
Once configured, this mapping overrules the default rules defined in the Call type section.
Example
The default HubSpot call type for an answered outbound call is set to First outreach.
A call is tagged with QA_TAG_1.
QA_TAG_1 is mapped to the HubSpot call type Demo.
Result: The call will be logged in HubSpot with the Demo call type instead of First outreach.
Fallback behavior and edge cases
The following rules apply when tags are not mapped or conditions are not met:
If a call does not include a mapped tag, the standard Call type settings apply.
If a mapped tag is removed from a call, the standard Call type settings apply.
If multiple tags are present on a call and more than one tag is mapped to different HubSpot call types, the standard Call type settings apply.
Important: Tag-based mapping is applied only when exactly one mapped tag is present on the call.
Timing and update behavior
Be aware of the following timing-related behaviors:
Note: When a mapped tag is added during a call, the mapped HubSpot call type is applied only after the call has ended.
Deleting a mapping does not update call types for calls that were already logged in HubSpot.
If a mapped Aircall tag is deleted, it appears as Deleted tag in the mapping settings, and existing HubSpot call activities remain unchanged.
Important: There is a one-hour delay for deletions, updates, and creations of mapped call types.
Details:
If a mapped custom call type is deleted in HubSpot, it may still be used in call logs for up to one hour if a call is tagged during that period.
The deleted call type is immediately removed from the Dashboard settings and cannot be selected again.
If a custom call type is created or updated in HubSpot, it appears immediately in the Dashboard, but new mapping rules created in the Dashboard may take up to one hour to take effect.
Learn more
For more details on the HubSpot integration, please see the following Help Center articles:
- How the HubSpot integration works
- Installing your HubSpot Integration
- How to configure the HubSpot Integration
- HubSpot workflows and custom properties
Using Aircall tags to drive HubSpot call engagement types gives you more flexibility and control over how calls are categorized, while still preserving your default call type logic as a fallback.