Does Unify Create Accounts in HubSpot Automatically?
Yes—Unify can create company records in HubSpot when the sync permits creation and a company domain is available. It can write a company alongside its contact or through an explicit company sync action in a play. Connecting HubSpot alone does not mean every account you discover will be created there.
HubSpot calls these account records companies. Keep three questions separate: which event requests a write, whether a matching company already exists, and what the configured write is allowed to do. The HubSpot sync documentation describes those conditions; the connection establishes access, while your configuration determines the write path.
Does connecting HubSpot create every discovered account?
No. Finding a company in Unify, reading an existing HubSpot company, and creating a new HubSpot company are different operations. Seeing CRM information in an audience is not evidence that Unify created the underlying record.
The HubSpot integration guide separates connecting the account, reviewing field mappings, choosing sync rules, and enabling bidirectional syncs. Follow that order before relying on a production workflow. Initial CRM ingestion brings existing HubSpot data into Unify; do not interpret that incoming sync as a list of newly created HubSpot companies.
Which actions can create or update a company?
Automatic sync rules respond to configured activities, such as prospecting or enrollment. In Settings → HubSpot → Sync rules, review the behavior for the event you actually use. For prospecting, Sync if already exists supports matching-record updates; Sync also permits creation. An event set to Do nothing is disabled for that automatic rule.
An explicit Sync to HubSpot play action is a separate route. It uses the workspace connection and saved mappings, requires bidirectional syncs, and runs according to the play independently of automatic sync rules. Disabling an automatic event is therefore not proof that an explicit play action cannot write. Inspect the play configuration and execution logs when tracing that route.
| Condition on the company write | Documented result | What to verify |
|---|---|---|
| A company domain matches an existing HubSpot company | The matching record is selected for an update. | The destination ID and applicable field mappings. |
| No company matches; creation is permitted; a domain is supplied | Unify can create a company. | The sync result and resulting HubSpot record. |
| No company matches; creation is not permitted | This write is not permitted to create a new company. | The relevant rule or action, rather than the connection alone. |
| The required domain is missing | The documented new-company creation conditions are not satisfied. | The source domain, mapping, and reported result. |
| Several companies match the domain | One matching company is selected for the update. | Which record was selected; existing duplicates are not merged. |
This table describes documented conditions, not results from a test run. Do not treat a queued action, successful connection, or prospecting result as confirmation that a new company exists in HubSpot.
What happens to companies already in HubSpot?
Company matching uses the domain; contact matching uses email. Keep the company and contact IDs separate during review. A contact update does not, by itself, tell you whether the associated company was created, updated, or unchanged. Matching also does not clean up pre-existing duplicate companies.
Review field mappings before allowing writes to existing records. Read and write behavior are independent, and available fields depend on object, type, and access. The default-value settings supply missing values during mapped syncs; they are not an instruction to create every company. Review required properties and preserve the intended owner of each field.
The account-data maintenance workflow provides a useful review pattern: identify gaps, match records, and inspect proposed changes. Apply that discipline to company identity before changing mappings or repeating an action.
Can I explicitly ask Unify to save a company?
The CRM chat documentation describes asking Unify to save a company or person to the CRM. Chat writes must be allowed by an administrator, and the selected connection must support the request. Provide a domain or other identifying context when names are ambiguous.
Chat is an explicit request, not evidence that a background rule was enabled. If your process calls for review first, ask for the proposed change and approval before execution. Ordinary create and update requests can run directly when authorized. Review connection preferences to understand which account is used; personal HubSpot authorization does not necessarily limit app access to that user’s record-level permissions.
How do I verify which company was created?
Use Sync log in the HubSpot integration. Open the relevant attempt, inspect its result and connection, then open the record under Details for written values and the HubSpot record ID. Check that ID in HubSpot instead of searching only by a familiar company name.
Compare the destination with the source company. Record inspection helps you review the Unify record ID and attributes. Preserve the source domain, destination ID, action, check time, and observed result in your internal review. If the result is ambiguous or failed, keep it unresolved rather than reporting a new account as created.
For a controlled verification, define one permitted existing-match case and one permitted no-match case before running a write. Specify the expected create-versus-update behavior and inspect the outcome afterward. These are suggested acceptance checks, not claims that a live HubSpot test was performed for this article.
The broader CRM integration implementation guide covers ownership and mapping tests. For this question, the next step is narrower: review the exact rule or action, confirm its creation permission and domain input, then verify the destination record.
Frequently asked questions
Does every company found in Unify become a HubSpot company?
No. Discovery and CRM creation are separate operations. A configured write must run, and its creation conditions must be satisfied.
What does Unify use to match HubSpot companies?
The company domain. Contacts are matched by email, so verify company and contact records separately.
Does Unify merge duplicate HubSpot companies?
No. The documentation says existing duplicates are not merged; one matching company is selected for an update.
Can a play write when an automatic sync rule is disabled?
An explicit HubSpot sync action runs according to the play independently of automatic rules. It requires the workspace connection and enabled bidirectional syncs.
Where can I confirm the HubSpot company ID?
Open the write in Sync log, then inspect the record under Details for the written values and HubSpot record ID. Verify the resulting record in HubSpot.
