Clay + HubSpot Integration Guide: Full Setup (2026)
A working Clay and HubSpot integration is what turns a clever spreadsheet into a CRM that actually drives outbound. Clay enriches the records. HubSpot stores the relationships. The trick is connecting them so the data flows in cleanly without creating duplicates, broken activity, or fields nobody trusts. This guide is the version we use when we set up the integration for clients.
We orchestrate outbound for B2B teams running on Clay and HubSpot. The setup steps below are pulled from production engagements in 2025-2026. Pricing and feature details verified as of mid-2026.
Why Connect Clay and HubSpot
Clay and HubSpot solve different problems. Clay is a data orchestration platform. It pulls from many sources, runs enrichment workflows, and outputs personalized records. HubSpot is a CRM. It stores contacts, companies, deals, and activities, and gives reps and marketers a single source of truth.
Connected, the two cover the full outbound motion. Clay finds and enriches the right contacts. HubSpot stores them, tracks activity, and reports on pipeline. The integration is the part where the data crosses from one to the other cleanly.
The risk is that without good integration logic, you end up with duplicate contacts, overwritten fields, broken associations, and a CRM that nobody trusts. We have seen teams burn quarters cleaning up Clay-HubSpot data because the initial integration was rushed.
Prerequisites
Before you connect Clay to HubSpot, do three things.
First, make sure your HubSpot setup is clean. Field consistency, naming conventions, dedup rules, and any custom properties you use for outbound should all be documented. If your HubSpot is messy now, Clay will make it messier.
Second, define what fields Clay will write. Most teams write to: Email, First Name, Last Name, Job Title, Company Name, Company Domain, LinkedIn URL, and one or two custom fields for the Clay-derived signal (like "Latest Funding Round" or "Tech Stack Signal").
Third, define dedup logic. Will Clay match contacts on email? Email plus company domain? LinkedIn URL? The match logic determines whether you get clean updates or duplicate records. We recommend matching on email primarily, with LinkedIn URL as the secondary key.
Step 1: Connect HubSpot to Clay
In Clay, go to Integrations and search for HubSpot. Click Connect. Authenticate via OAuth using a HubSpot user with admin permissions.
Once connected, Clay can read from and write to HubSpot. The connection is at the workspace level, so any table in your Clay workspace can use HubSpot data.
Step 2: Pull Data From HubSpot Into Clay
Most workflows start by pulling a list from HubSpot. Common starting points:
- Contacts in a specific list (e.g., "Q2 outbound target accounts") - Companies with a specific lifecycle stage (e.g., "Lead" but not "Customer") - Contacts created in the last 30 days - Companies in a specific industry or size range
Use the "HubSpot: Find Contacts" or "HubSpot: Find Companies" action in Clay. Filter to the records you want. Pull them into a Clay table.
This is your input. The Clay workflow runs on top of these records.
Step 3: Build the Enrichment Workflow
A standard SaaS or B2B enrichment workflow in Clay typically includes:
1. Find decision maker (Apollo + LinkedIn Sales Navigator waterfall) 2. Enrich company data (Clearbit + ZoomInfo waterfall) 3. Pull tech stack signal (BuiltWith) 4. Pull funding signal (Crunchbase) 5. Run Claygent for the most relevant signal in the last 30 days 6. Generate personalized opener 7. Verify email and quality-check
Each step is a column in Clay. The output is a row that contains the original HubSpot record plus the Clay-derived enrichment.
For more on workflow patterns, see our Clay for SaaS guide.
Step 4: Push Data Back to HubSpot
Once the Clay enrichment is complete, write the new fields back to HubSpot. Use the "HubSpot: Update Contact" or "HubSpot: Update Company" action.
Three rules for clean writes:
The first rule is to match by HubSpot Object ID, not by email. The Object ID is the canonical identifier in HubSpot. Matching by email creates false matches when the same person changes companies.
The second rule is to write only the fields Clay owns. If a field is updated by reps in HubSpot, do not let Clay overwrite it. Set Clay to write to its own dedicated custom fields, not to fields shared with rep workflows.
The third rule is to log the write timestamp. Add a custom field like "Clay Last Enriched" so you can see when each record was last updated. This makes debugging much easier.
Step 5: Avoid the Duplicate Trap
The single biggest source of mess we clean up for clients is duplicate contacts created by Clay-to-HubSpot pushes.
Three things prevent this.
First, always match before write. The "HubSpot: Find Contact" action with email match should run before any "HubSpot: Create Contact" action. If a match exists, update. If not, create.
Second, set up HubSpot's built-in dedup rules. Under Settings > Objects > Contacts, configure Match Properties to include email and any other fields you trust. HubSpot will prevent creation of obvious duplicates.
Third, audit weekly. Run a HubSpot report on contacts with the same email or the same LinkedIn URL. Merge duplicates as they appear. The first month of a Clay integration almost always produces some duplicates that need cleanup.
Step 6: Trigger Outbound From HubSpot
Once Clay-enriched records are in HubSpot, trigger your outbound from HubSpot.
The cleanest setup uses HubSpot lists or workflows to push records into your sending platform (Smartlead, Instantly, Apollo). The trigger is a list membership rule or a workflow action. Reps and managers see the campaign status in HubSpot, and replies sync back via the sending platform's HubSpot integration.
This keeps HubSpot as the source of truth for activity and pipeline. Clay is the enrichment layer. The sending platform is the execution layer. Each tool has its job.
Sample Workflow: Funding-Triggered Outbound
Here is a complete workflow we set up for a SaaS client in 2026.
1. HubSpot Source: Companies in the "Series A-C SaaS" list, lifecycle = Lead, last activity > 90 days ago 2. Clay enrichment: Pull funding events in the last 30 days, find decision maker, generate opener referencing the round and the most likely use of funds 3. Write back to HubSpot: Update the company record with "Clay Latest Signal" field and the contact record with "Clay Personalized Opener" field 4. HubSpot list trigger: When "Clay Personalized Opener" is set, add to "Clay Outbound Q2" list 5. Smartlead trigger: HubSpot list membership pushes contact to Smartlead campaign 6. Reply sync: Replies in Smartlead sync to HubSpot as activities
The result is a closed loop. HubSpot starts the cycle, Clay enriches, the sending platform executes, replies come back to HubSpot. Reps see everything in one place.
Cost Considerations
Clay credits add up fast on multi-step workflows. A funding-trigger workflow that runs across 1,000 accounts can consume 3,000-5,000 Clay credits. At Explorer-tier pricing (about $349 per month for 50,000 credits), that is roughly $20-$35 per 1,000 enriched accounts.
HubSpot integration is free on Clay's side. HubSpot itself charges for Marketing Hub and Sales Hub seats, which most teams already have.
For more on Clay pricing and ROI math, see our Apollo vs Clay comparison.
Where LeadHaste Fits
We orchestrate the Clay-HubSpot integration for clients who want the output without managing the workflows themselves. The integration is one layer of a system that includes data sources, Clay workflows, HubSpot configuration, sending infrastructure, and reply handling.
The client owns everything we build. The HubSpot setup, the Clay workflows, the sending domains, all of it. We run the system. If we ever part ways, the client takes the entire orchestration with them.
For more on our approach, see our services and case studies.
Ready to Run Clay and HubSpot as One System?
We build clean Clay-HubSpot integrations for B2B teams that want enriched outbound without breaking their CRM. You own everything. We run it.
Frequently Asked Questions
A modern outbound stack includes: data enrichment (Apollo, Clay, ZoomInfo), email infrastructure (Google Workspace, custom domains), sending tools (Smartlead, Instantly), warm-up services (Warmbox), LinkedIn automation (Expandi, Dripify), CRM integration (HubSpot, Salesforce), and analytics platforms. Most agencies use 15–30 tools orchestrated together.
Building your own stack costs $3K–5K/month in software alone, plus a dedicated person to manage it. With a managed service, you get all the tooling plus the expertise to orchestrate it — often at lower total cost. The key question: can you afford to spend 6–8 weeks setting up instead of generating pipeline?
There's no single 'best' tool — it depends on your volume, budget, and integration needs. Smartlead and Instantly are popular for high-volume sending. Apollo doubles as a data and sequencing platform. The real advantage comes from how tools are orchestrated together, not from any single tool choice.
Look for three things: (1) Do you own the infrastructure they build? (2) Do they guarantee results or just charge a retainer? (3) Can you see transparent metrics and real case studies with specific numbers? Avoid long contracts, vague reporting, and agencies that own your domains.
Data enrichment is the process of taking basic company or contact data and adding layers of detail — job titles, direct emails, phone numbers, technographics, intent signals, company size, funding stage, and more. Enrichment tools like Apollo, Clay, and ZoomInfo pull from multiple data sources to build a complete prospect profile before outreach begins.
Dimitar Petkov
Co-Founder of LeadHaste. Builds outbound systems that compound. 4x founder, Smartlead Certified Partner, Clay Solutions Partner.
