No duplicate companies, just because one lookup had a bad moment.
fieldbrain cleanly distinguishes between 'no company found' and 'the search just failed' and only creates something new in the first case.
The technical precision
A company search that technically fails is not the same, to fieldbrain, as a search that confirms no match. Only a confirmed non-match leads to creating a new company. A transient API error never produces a duplicate. Since HubSpot's access tokens are workspace-scoped, not tied to one person, a configured owner is resolved once against the real Owners API and reused for every deal.
What actually syncs
What stays unchanged: fieldbrain only ever writes the fields from the table above. Other objects, your own automations, layouts, or reports in your CRM stay untouched. Nothing gets deleted, renamed, or restructured, only added to.
A day with HubSpot
A rep calls fieldbrain right after a call and describes what was discussed. fieldbrain looks up the company in HubSpot, finds it or creates it, updates the deal, and assigns it to the right owner. A sales manager opening the pipeline in the morning already sees last night's update, not a gap filled in mid-week.
Does fieldbrain create duplicate companies if a lookup briefly fails?
No. A brief API error is treated as unknown, never as confirmed absent, so it never results in a second company.
What happens if HubSpot hits a rate limit?
fieldbrain automatically retries the write with increasing wait time. A brief limit on HubSpot's side doesn't cause an update to be lost.
Security & Permissions
Your connection belongs exclusively to your account. No other user, not even on the same team, can access it.
Sync is part of the Professional plan and above. Without an active plan it stays inactive, nothing runs in the background.
Disconnect it and sync stops immediately. Data already transferred stays where it is, nothing is retroactively deleted.