User Mapping and Campaign Mapping control how owners and activity data are written in HubSpot. They do not change the OAuth token scopes.

Identities Mapping connects identities used by Enginy with HubSpot owners. When Enginy logs certain activity, it can write the corresponding owner in the properties sent.

This mapping does not make Enginy run the request as that person. It also does not limit the API to Contacts visible to that owner.

Users Mapping connects Enginy users with HubSpot owners to assign ownership of the record or corresponding activity.

The individual permissions of the mapped user do not apply to the integration. Access still depends on the OAuth token and its scopes.

Default CRM owner is used as a fallback when Enginy cannot resolve an owner through the previous mappings.

Choose someone who can receive records without a clear owner. Review this option when someone leaves the team or changes their HubSpot user.

Campaign Mapping lets you connect data generated by Enginy campaigns with HubSpot properties.

The screen organizes mappings into sections such as:

Configure only the properties you are going to use. Review their type and avoid reusing a HubSpot property for data with different meanings.

The Tasks panel appears only when the corresponding feature is enabled in your workspace. In HubSpot, you can connect call outcomes with Enginy call statuses.

Check the mapping when you change or add outcomes in HubSpot. A new outcome is not automatically associated with an Enginy status.

Enginy has flows to log calls and resync them with the CRM. The result depends on the linked Contact, the resolved owner, and the active mappings.

If a call does not appear in HubSpot:

The integration includes native Enginy surfaces inside HubSpot to work with lists, campaigns, and workflows. The available actions depend on the record context and the features enabled for your workspace.

Two things changed here recently, and they are worth stating plainly because the old behaviour caught people out.

Conversations CRM Export controls whether messages are logged as activities. It does not control whether Campaign Mapping fields are written.

The two used to be coupled: turning conversation export off also stopped Sequence Status from updating, silently. They are now independent — campaign fields mirror every send and reply whatever the message-logging setting says.

Sequence Status also syncs on enrollment, so it appears when the contact enters the campaign rather than only after the first message is logged.

Status used to reach HubSpot only on message events. It now also syncs when you:

A blocked lead is reported with a blocked status rather than dropping out of the sync.

These syncs never fail the action that triggered them. Pausing a contact still works if HubSpot is unreachable — the failure surfaces in the sync status instead.