How HubSpot enrichment works in Default
A HubSpot enrichment workflow in Default runs these steps:- Something starts the workflow. A visitor submits a form on your site, which fires the Form Submission trigger, or a new contact or company appears in HubSpot, which fires CRM Record Created.
- Default enriches the lead. An Enrich Data node runs your waterfall for the person’s email, the company’s domain, or both.
- Default checks HubSpot. For a form submission, a Match Record node looks for an existing HubSpot contact, so the workflow does not create a second contact for an email HubSpot already has.
- Default writes the fields to HubSpot. A Create Record node creates the contact with the enriched properties, or an Update Record node adds them to the existing record.
- The run is logged. The run log shows what each provider returned, the credits used, and the properties written. See Run logs.
Triggers for HubSpot enrichment
The CRM triggers become available once HubSpot is connected. See
HubSpot and Triggers.
Enrichment starts before the form is submitted
On a form the Pixel tracks, Default starts enriching as soon as the visitor types an email address and leaves the email field, before they submit:- What runs. Default runs your workspace’s Primary Waterfall for the email, and for the company domain when the email is a work address. It also runs the waterfall’s email and IP validation checks when they are on.
- What the workflow gets. When the form’s workflow reaches an Enrich Data node that uses the same waterfall, the node reads the person and company results that are already waiting instead of calling those providers again, and those lookups are not charged a second time. The waterfall’s email and IP validation checks run again in the node and are charged again.
- What it costs. The early lookup uses credits like any other lookup, including for visitors who leave without submitting.
- When it does not run. Without a primary waterfall, Default skips the early lookup, and the Enrich Data node calls the providers when the workflow reaches it.
Write enriched fields back to HubSpot
Default writes to HubSpot with CRM nodes from the Records section of Add Node:
For each HubSpot property, open the data picker and choose a value under the Enrich Data node’s
Person or Company result, for example Title, Seniority, Industry, or
Employee Count. Which fields come back depends on what the providers return for that lead.
How Default handles the values:
- Empty results do not clear properties. When the enrichment returned nothing for a field, Default skips that mapped property, so a miss never blanks out a HubSpot value. Choose Set field to null in the value picker only when you intend to clear a property.
- Existing values are overwritten. Update Record replaces the property’s current value with the enriched one. If reps also edit a property by hand, write enriched values to separate properties, or leave existing contacts unchanged as in the form example below.
- HubSpot’s Create Record has no Update on conflict. Check for an existing contact with Match Record first. If HubSpot rejects a create because a unique property already has that value, the node creates nothing, continues with the existing record when HubSpot reports its ID, and the run goes on. See Duplicate CRM records.
Enrich new HubSpot contacts from a form
This example enriches every demo request, creates a HubSpot contact for new leads with the enriched properties, and leaves existing contacts as they are.1
Add the trigger
In Workflows, create a workflow and add the Form Submission trigger. Set
Connected Form to your demo request form.
2
Add the Enrich Data node
Select Add Node, then choose Enrich Data in the Enrichment section. Set
Enrichment target to Both and Enrichment source to your primary waterfall. Leave
Email / Domain (optional) empty so Default uses the submitted email and its domain.
3
Check for an existing contact
Add Match Record from the Records section. Set CRM to HubSpot and Record to
Contact, and under Match Details match the contact’s email to the submitted email.
4
Create the contact on the No Match branch
On the No Match branch, add Create Record. Set Platform to HubSpot and
Record Type to Contact. Under Mapped Fields, map the email and name from the form, then
map enriched values into properties such as
Job Title and Phone Number.5
Leave the Match branch unchanged
Leave the Match branch without an Update Record node, so an existing contact keeps the
values your team already has. Add an Update Record node there only for properties that Default
owns.
6
Test, then publish
Select Test, choose the Form Submission trigger, enter a test email, and select
Run Test. Check the new contact in HubSpot and the Enrich Data step in the run log. Then
select Publish and turn on the deployment switch so the
status reads Live.
Enrich contacts created in HubSpot
This example enriches every contact that appears in HubSpot, whatever created it.1
Add the trigger
Add the CRM Record Created trigger. Set CRM to HubSpot and Record to Contact.
Optionally, add a Condition, for example on the contact’s lifecycle stage.
2
Add the Enrich Data node
Add Enrich Data. Set Enrichment target to Person or Both, and
Enrichment source to your waterfall. Set Email / Domain (optional) to the contact’s email
from the trigger.
3
Write the fields back
Add Update Record. Set Platform to HubSpot, Record Type to Contact, and
Record to update to the contact’s record ID from the trigger. Under Fields, map each
HubSpot property to an enriched value.
4
Test, then publish
Test with a sample contact, confirm the properties in HubSpot, then select Publish and turn on
the deployment switch so the status reads Live.
The write-back is a change to the record. If another workflow uses CRM Record Updated on the same
HubSpot object, the write can start it. Give that workflow a Condition that uses
Fields Updated and watches only properties this enrichment workflow does not write.
What HubSpot enrichment costs
HubSpot enrichment uses the same enrichment credits as any other lookup in Default:- Each provider in the waterfall that returns data is charged. A miss is free, except for Clearbit and the email and IP validation checks.
- Both runs a person lookup and a company lookup, and each is charged.
- Writing to HubSpot uses no credits.
Troubleshoot HubSpot enrichment
Related: Lead enrichment software from Default