#HubSpot

#Permissions

The connection needs contacts read/write, deals read, owners read and contact schema read/write (to create the X3 fields). Without schema write X3 asks you to map existing fields or keeps the values in the note.

#Contacts and notes

X3 creates contacts. HubSpot itself refuses a second contact with the same email – X3 then links the existing one. Notes are HubSpot notes associated with the contact. The record link opens the contact in your portal (EU portals on app-eu1).

#Standard fields

X3 writes these HubSpot standard contact properties instead of own fields (new connections; existing connections get them where the field was not mapped yet). Like every X3 field they are filled on create and afterwards only while empty – HubSpot's own value (for example „Offline sources“ of an imported contact) is never overwritten.

Not written: the drill-downs hs_analytics_source_data_1/2 (set by HubSpot, read-only), hs_latest_source (HubSpot recalculates it with every tracked visit), lead status and lifecycle stage (X3 has no status write-back). Raw UTMs, the X3 link, fit and lead id have no HubSpot equivalent and stay x3_* fields.

#Deals and meetings

Won = hs_is_closed_won. The value is the sum of every associated won deal of the contact, converted into the project currency at the close date. Meetings come from the meetings object (hs_meeting_outcome: canceled and no-show do not count).

#Limits

HubSpot portals have a limit for custom properties. X3 creates at most five own fields by default (x3_lead_url, x3_source, x3_campaign, x3_fit, x3_lead_id); everything else goes into the note. If the limit is reached the task „CRM-Felder“ appears.