Platform · CRM sync

HubSpot

Leads become HubSpot contacts, meetings become meeting engagements, email activity can be logged, and lifecycle stage, lead status, deals and history are read back. This page follows the HubSpot card under CRM Sync from top to bottom, with the HubSpot setup guide the app shows.

Step 1 · Connect

Open Integrations
Settings → Workspace → Integrations, HubSpot tile, Connect HubSpot. A dialog explains that Meeton will sync contacts, deals and lead activity. Also import email history asks HubSpot for one extra permission, to read sales emails, which only a HubSpot super admin can approve; you can leave it off and add it later.
Approve in HubSpot
Sign in as a user with rights to the contacts, companies, deals, owners, forms and lists of the portal you want. Meeton requests read and write on contacts, write on companies, read on deals and owners, plus forms and lists.
Back in Meeton
The tile reads Connected · set-up needed. Nothing is pushed yet: go to Settings → Apps → Meeton ai → Data & tracking → CRM Sync.

Step 2 · Initial setup: the unique ID property

Meeton stores its contact ID in a custom contact property so the same person can be found again. Set Up Custom Properties creates it (and the attribution properties, if you use them) in one click and reports Created, Already exists or Failed per field. If your HubSpot user cannot create properties, ask a super admin for that permission or follow the manual guide, which is the one the app shows:

HubSpot setup guide (manual)

In HubSpot, click the Settings icon (⚙️) in the main navigation bar.
In the left sidebar, navigate to Properties.
Click the Create Property button.
Set the Object Type to Contact.
For the Label, enter a name like DynaMeet Contact ID.
Click Next.
For the Field Type, select Single-line text.
HubSpot will show the Internal Name (e.g., dynameet_contact_id).
Important: on the Rules screen, do not check the Require unique value box.
Click Create.
Copy the Internal Name you just created and paste it into the Unique ID Field box in Meeton.

Contact Sync and Activity Sync stay greyed out until the field is set. If you turn Push on with the box empty, Meeton uses dynameet_contact_id.

Step 3 · Contact sync

Push contacts

Sync new contacts to HubSpot when a visitor submits a form. Matched by email; a new contact is created only when none exists. A note with the form submission details is added either way.

Fields written

First name, last name, company, phone, job title, plus any lead-form custom field you linked to a HubSpot property (Lead form → Import from HubSpot, up to 20 custom fields).

Merge strategy

Fill empty only by default; see the overview.

Language

Japanese or English for the activity subjects and notes Meeton writes.

First-touch attribution

UTM parameters and ad click IDs written into contact properties you name, only while they are empty. The table lists each parameter with its HubSpot property, checks whether it exists, and can create it.

Step 4 · Activity sync

Setting	Direction	What it does	Default
Meeting sync	To HubSpot	Creates a HubSpot meeting engagement, Meeting booked via Meeton AI, when a meeting is booked. The owner is the HubSpot user whose email matches the host.	On
Meeton Email activity	To HubSpot	Logs AI email events, Sent, Opened and Clicked (with the link URL), as email engagements on the contact. Shown as Not available on your plan where it is not included.	Off
Import notes & meetings	From HubSpot	Pulls the contact's HubSpot notes and meetings into Meeton as read-only history, so the chat agent and Meeton Email know what your team already did.	Off
Import emails	From HubSpot	Pulls the contact's HubSpot email history into Meeton, read-only. Reads your sales emails, so HubSpot asks for explicit permission: Grant email permission sends you to a HubSpot consent screen that mentions sensitive data. Only emails on contacts you already sync are imported, nothing is edited or sent back, and you can switch it off without disconnecting. If the permission lapses the row reads Paused until you reconnect.	Off
Import deal amounts	From HubSpot	Reads the amounts of deals associated to synced contacts to calculate Pipeline influenced on the ROI dashboard. Pick a default currency for deals that carry none.	On

What is read back

Lifecycle stage and lead status. A contact whose lead status is unqualified, or whose lifecycle stage is unqualified or other, is treated as disqualified in Meeton: follow-up email stops and lead notifications no longer fire for them.
Deals. The first associated deal's amount and stage, for the ROI dashboard. Meeton never creates or edits deals.
Owner. Used to attribute meetings to the right HubSpot user.

HubSpot forms on your site

The tag understands HubSpot forms without any mapping. Both the legacy inline embed and the v4 forms embed are detected; a successful submission identifies the visitor and, if the page has a Form submitted here rule, opens the booking calendar the moment HubSpot confirms the submission. When the HubSpot tracking script is on the page, the identity is pushed to its queue (_hsq) too, so the HubSpot contact and the Meeton visitor line up before the first sync run.

Test it

Send test contact at the foot of the card fires a simulated visitor event with your current settings to the email address you type. Only syncs that are on run, so it is the quickest way to see the contact, its note and the attribution properties appear in HubSpot. A test that fails on a missing property names it, with the fix: Set Up Custom Properties.

Troubleshooting

Symptom	Likely cause	What to do
Tile reads Connected · set-up needed	Push contacts is off or the unique ID property is not set	Finish steps 2 and 3 on the CRM Sync page.
Some fields failed to create	Your HubSpot user lacks permission to create custom properties	Ask a HubSpot super admin for the permission, or create the property manually and paste its internal name.
Test fails: Custom property … does not exist	The property was renamed or deleted in HubSpot	Create it again, or update the name in Meeton.
Meetings sync with no owner	The host's Meeton email does not match a HubSpot user's email	Use the same address in both, or accept unowned meetings.
Import emails reads Paused	The email-read permission was revoked or expired	Reconnect to grant permission; notes and meetings keep importing meanwhile.
HubSpot contact and Meeton visitor are separate people	The visitor identified in chat with a different email than on the HubSpot form	Expected; they merge once an email matches.
A HubSpot form stopped submitting	The legacy form path sends the data to Meeton first; if that request is blocked the submission is held back	Check that `api.dynameet.ai` is reachable from the page; the debug log says HubSpot submission prevented.

Frequently asked questions

Which HubSpot tiers does it work with?

Any tier with custom contact properties and OAuth apps, which includes the free CRM. Some activity imports depend on your Meeton plan rather than on HubSpot.

Why does HubSpot warn about sensitive data when we grant email permission?

Because the permission reads the content of sales emails. Meeton imports only emails on contacts it already syncs and never edits or sends them. Leave Import emails off if you do not want that.

Can we choose which HubSpot properties receive the form fields?

Standard fields map by name. For your own fields, import the HubSpot property as a lead-form custom field; it then stays linked and writes to that property.

Does it create companies?

Meeton fills the contact's company field. It does not create or associate company records.