HubSpot and Clay

Read a filtered slice, fill the gaps, write it back, on a schedule. From Clay Growth up.

What you have to buy first

Clay Growth or above, where CRM integrations start. Nothing extra on HubSpot.

What moves

Contacts, Companies, Deals, Lists, two-way sync.

Price the Clay plan before anything else, because CRM integrations start on Growth and the HubSpot integration documentation never mentions it. Past that, this is a loop rather than a sync and the framing matters: Lookup actions read without changing anything, while Create and Update write a result every user in the portal sees immediately. The discipline that keeps it safe is the same three rules every time: import a filtered set rather than the portal, keep blank values ignored, and exclude the properties your reps own.

What actually syncs

Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.

WhatDirectionWhat that means in practice
HubSpot to Clay One way, in Lookup actions pull contacts, companies, deals or a list into a table. Read-only, so nothing in HubSpot changes.
Enrichment in between Event only Any provider, including any HTTP API, becomes a column. This is how a tool with no HubSpot app gets one.
Clay to HubSpot One way, out Create and Update push real changes. Test on a handful of rows first, because there is no preview of a write at volume.
Refresh Both ways Auto-update re-runs the table on a schedule, which is what turns a one-time backfill into a maintained field.

One of those four rows moves in both directions. The two that do not are HubSpot to Clay and Clay to HubSpot, and those are the rows that decide how you design around this rather than the ones in the brochure.

Which field lands where

Clay does not map fields to HubSpot so much as read and write them one action at a time. Every action starts with an object type pulled from your own portal, and the properties underneath change with the type you pick, so the dropdown is your schema rather than a fixed list.

In HubSpotIn ClayWhat to know about the match
Contacts Look up, Create, Update object Reading needs crm.objects.contacts.read, which is mandatory. Writing needs the contacts write scope, which is optional and on by default, so a connection made with it unticked reads perfectly and silently cannot write.
Companies The same three, plus a domain switch Keep subdomains in Company domain is off by default on Create and Update, so shop.example.com is reduced to example.com before it is written. Look up has the matching switch for its Domain filter and the two are set separately.
Deals Look up, Create, Update object The deal read and write scopes are optional and enabled by default. Choosing Deal as the object type exposes your own pipelines and their stages as mappable fields.
Leads Create object, with Association Fields Lead is the one type whose Create action associates as it creates, taking an association object type of Company or Contact, an association type, and the target object ID.
Owners Find owner By owner ID or by email, and supplying both validates the email against the owner found by ID. Clay says the ID is the more reliable input, because an email coming out of an enrichment often belongs to nobody in the portal.
Associations Create association, Get associated objects Get associated objects defaults to 20 and 20 is also the maximum, so a company with fifty contacts cannot be read in one call.
Static lists Add record to list Only lists whose membership you can edit are offered. HubSpot recalculates an active list from its own filters, so those never appear in the dropdown and the list has to be created as static first.
Custom objects Every object action, Enterprise only They appear in the object type dropdown after the standard four. The three scopes behind them are the ones HubSpot will not grant below Enterprise.

What each Clay write looks like from inside HubSpot

Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.

The actionHow it reads on the record
Update objectA property change on the existing record, visible to every user at once, with no staging copy and no preview
Create objectA new record, and a duplicate of one that already existed under a key you did not match on
Create associationA link between two records, of the association type the pair of object types offered
Add record to listMembership of a static list, or nothing at all with Added to list returned as false
An enrichment you did not mapNothing. A column that stays in the table is invisible to the portal, and it still cost an action

What does not cross

Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.

  • Activity. The action list covers objects, associations, owners and lists, and carries nothing that writes to a timeline, so an email Clay found is a property value rather than a line on the record.
  • Any marker saying a table did it. A Clay write is a property change like any other and shows in HubSpot's own property history as one. Writing to prefixed properties is how teams tell their enrichment from their reps.
  • Active list membership, which is HubSpot's to compute from the list's filters rather than anybody's to write.

Every row above travels as a file: eight field mappings, five action rows and three documented exclusions, each one's note, and the four vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.

Field map

What the table describes is a loop rather than a sync: nothing is mapped, so nothing drifts out of agreement, and equally nothing stays in step without a schedule behind it. That is the trade this route makes against the HubSpot and Zapier route, which maps once and fires on an event.

The Clay plans that actually carry this

HubSpot gates almost nothing here. Clay gates most of it, and its own HubSpot documentation does not mention a plan, so this grid is read off the pricing page instead. Pick one on each side and the grid marks the answer.

Pick one on each side.

Clay planScheduled runsCRM integrationsHTTP API and webhooksSync faster than daily
Free No access No access No access No access
Launch Full access No access No access No access
Growth Full access Full access Full access No access
Enterprise Full access Full access Full access Full access
No access
The row on Clay's plan comparison reads "Not included". For CRM integrations that means the HubSpot source and the object actions are not available to you at all, whatever HubSpot edition you are on.
Full access
The row reads "Included". Source sync frequency is the one that is not binary: it is one day on Free, Launch and Growth, and 15 minutes on Enterprise.

Counted off that grid, of sixteen pairings: eight give you no access, eight give you full access. The staircase is the useful shape here, and it runs the opposite way to most pairs in this directory: a HubSpot upgrade buys Clay almost nothing, and the plan that decides whether this pair exists at all is Clay's. If the bill is the problem, the lever is the filter on the import step rather than a tier on either side.

How to connect HubSpot to Clay

Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.

Who has to do it
Somebody who can authorise an app on the HubSpot portal, and whoever owns the Clay workbook. One person is often both.
How long it takes
Ten minutes to connect. The hour goes on deciding what to import and what to let it write.
Setup checklist 0 of 8 done

Clay: pricing

The plan comparison marks CRM integrations as a Growth feature, not on Free or Launch, and Growth is $446 a month on the page header. Nothing in the HubSpot integration documentation says so, so this is the step that gets skipped and the one that ends the project.

HubSpot: Lists

Clay's import takes an optional list, and the documented behaviour without one is that every object is pulled. A static list of the records missing the field you care about is the difference between four hundred rows and the whole portal, and it sets what the run costs.

Clay: workbook, + Add

Click + Add at the bottom of a workbook, search HubSpot, then pick the account or run + Add account. Seven read scopes are mandatory and cannot be refused: contacts, companies, leads, owners and lists, plus the contact and company property schemas.

Clay: the consent screen

crm.schemas.custom.read, crm.objects.custom.read and crm.objects.custom.write arrive switched off, and Clay documents why: HubSpot grants them on Enterprise portals only, and authorisation stops rather than continuing without them. Switch them on below Enterprise and the connection fails outright.

Clay: Import objects from HubSpot

The object type list is read from your own portal, so your custom objects sit beside the standard ones. Point it at the list, leave Include Read Only Properties off so you get editable properties rather than every calculated field, and turn Exclude empty properties on if blanks are noise.

Clay: Add enrichment

Look up object, Get associated objects and Find owner all read and change nothing in HubSpot. Run the table to the end of those columns and check the values while a mistake is still free, because the next step is not reversible.

Clay: Update object

Update requires the HubSpot Object ID, and that requirement is what makes the write land on the existing record instead of spawning a copy. Ignore blank values is on by default and should stay on. Create belongs to records that are genuinely new.

Clay: run settings

Auto-update re-runs the table and Only run if holds a column back until its condition is met. That pair is what turns a backfill into a maintained property, and what stops every provider re-running against rows that already resolved. Source sync is daily on every plan below Enterprise, where it is 15 minutes.

Six of those eight steps are reversible and two are not. The plan check comes before the build rather than after it, and the filter comes before the import rather than after a bill. The write step is the one worth rehearsing on ten rows, which is the discipline this part of the orchestration layer rewards more than any other.

Hand it to an agent instead

The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.

curl -o .claude/skills/hubspot-clay/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-clay.md

What breaks, and what nobody tells you

Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.

Actions are billed on the attempt
Clay bills per action rather than per result, so a provider that finds nothing still costs you. On a hard segment the effective cost per filled field is the action rate divided by your match rate, and that multiplier is the whole economics of this route.
A write is immediately live
Update actions change the record every user in the portal sees. There is no staging environment. The standard protection is a small test set, "ignore blank values" left on, and an explicit exclusion list for properties reps maintain.
Importing the whole portal is the classic mistake
Pull a filtered slice: contacts missing a title, companies with no employee count, deals in an open stage. Importing everything costs actions on rows that did not need anything and makes the write step far riskier than it needs to be.

Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.

The 8 failures people actually hit

Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.

01

The HubSpot source and the object actions are not there

WhyThe workspace is on Free or Launch. Clay's plan comparison marks CRM integrations as included from Growth, and nothing in the HubSpot integration documentation repeats it.

Check the plan before debugging the connection. There is no partial version of this on a lower tier, so the decision is a purchase rather than a setting.

02

Connecting fails with an unexpected error during the app authorization process

WhyOne of the three custom object scopes was switched on against a portal below Enterprise. HubSpot cannot grant them there, and the authorisation stops rather than proceeding without them.

Reconnect with all three off, which is how they arrive. Reconnecting keeps whatever was enabled last time, so an Enterprise portal that already has them on holds onto them.

03

The List dropdown shows an error asking you to reconnect

WhyThe connection does not carry the create and edit lists permission. HubSpot asks for it by default, so this is a connection somebody made with it unticked.

Reconnect the account and select that scope. It is the same flow and the rest of the permissions are unaffected.

04

A row ran, HubSpot accepted it, and the record is not in the list

WhyAdded to list came back false. Clay documents that as HubSpot taking the request and declining the record, because it is already a member or is not eligible for that list.

Read the output rather than the row status. A record ID that does not exist in the portal fails the row instead, which is a different signal and a different fix.

05

The write created a second copy of a record that already existed

WhyCreate was used where Update was meant. Create has no record ID input and no matching step, so it writes a new object every time it runs.

Use Update keyed on the HubSpot Object ID for anything that came out of an import. Clay puts that ID at the top of the Look up filter list for the same reason: it is the only precise match on offer.

06

A populated HubSpot property came back blank after a run

WhyIgnore blank values was turned off on the Update action. With it off, a blank Clay cell is sent through and overwrites what HubSpot had.

Turn it back on, and keep the properties your reps maintain out of the write entirely. It is on by default, so this is a setting somebody changed on purpose.

07

A company domain lost its subdomain on the way in

WhyKeep subdomains in Company domain is off by default, so shop.example.com is reduced to example.com before the write lands.

Switch it on in the Create or Update action, and separately in Look up if you are filtering on a subdomain. The two switches do not follow each other.

08

Credits went roughly twice as far as the row count suggested

WhyDuplicate records in HubSpot arrived as separate rows and every provider ran against both. Actions bill on the attempt, so a duplicate costs exactly what a match costs.

Measure the portal's duplicate rate before the first run and filter the import to the records you mean to pay for. This is the most expensive failure on this pair and all of it happens outside Clay.

If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.

When this is the right integration

Set it up when

  • Backfilling a property across thousands of existing records
  • Connecting a data source that has no HubSpot marketplace app
  • Logic that a RevOps lead needs to change without filing a ticket

Do not bother when

  • The enrichment is one field from one provider and never changes
  • You need the result inside HubSpot within seconds of a form submission
  • Nobody on the team is going to own the table

The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.

What practitioners say about it

Searched for this pair by name, in the words a person would use. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.

A duplicate rate in the CRM is a Clay bill, not a data problem

23% duplicate rate in contacts. Clay was enriching both copies, burning credits twice on the same person.

r/CRM·April 2026·1 points

Written up as a post-mortem across three mid-size SaaS teams on HubSpot Professional. The same post reports the lookup success rate going from about 58% to about 91% after the cleanup, on the same settings and the same waterfall, which is the clearest statement of the attempt-billing limit above that anybody has put in public.

Clay writes records, it does not log activity

Clay will not actually log activities to HubSpot, or at least this is probably not the cleanest set up.

r/revops·December 2025·4 points

It matches the action list exactly: objects, associations, owners and lists, and nothing that writes to a timeline. The rest of that comment sends the activity half to a sequencer with its own HubSpot app, which is a division of labour rather than a workaround.

The people who like it limit what it is allowed to overwrite

Clay - for enrichment and intent data, it's great but I've had to limit the triggers so it doesn't overwrite too much.

r/MarketingAutomation·November 2025·3 points

Two documented switches do exactly that, and both are in the setup list above: Ignore blank values, which is on by default, and Only run if, which holds a column back until its condition is met. Neither is visible from the table view, and both are cheaper than the cleanup afterwards.

The pattern people land on is one table that writes, not many

Send all individual table leads data (accounts + sub scores that you're generating) to one master table from those tables. And ensure auto dedupe based on domain is on.

r/gtmengineering·December 2025·3 points

The question was how to build one intent score in HubSpot out of signals living in four separate Clay tables. The answer is a fan-in: every table writes to one, the dedupe happens there, and only that table holds the HubSpot write. It keeps the number of things that can touch the portal at one.

The HubSpot-native alternative needs a hub most teams never bought

If you have Ops Hub Pro you could probably trigger a webhook in a tool like N8N and use an AI agent there.

r/hubspot·March 2025·3 points

Ops Hub is what HubSpot now sells as Data Hub, and the webhook action in a workflow needs its Professional tier or above. That gate is the reason enrichment logic leaves HubSpot for Clay or n8n in the first place, and the conditional at the front of that sentence is carrying all the weight.

What the threads add up to

Nobody in these threads argues about whether the connection works. What they argue about is what should be allowed through it, and every complaint lands in one of three places: writes that were too broad, rows that should never have been imported, and activity somebody expected on a timeline and got as a property. The teams reporting it going well describe the same habits, and each of those habits is a switch Clay already ships.

None of those five is a measurement, and the cost figures in the first are one team's own rather than a benchmark. They are worth reading because four of them describe behaviour Clay documents outright, which is the same reason every other Clay pair is worth checking against the docs the same way.

The longer answer

The reason Clay belongs in an integration directory at all is that it is a general-purpose connector wearing a spreadsheet. Any API becomes a column. That means a provider with no marketplace listing, Reverse Contact among them, is roughly as easy to wire into HubSpot as one with a certified app, and considerably easier to change afterwards.

What you are paying for is the change part. If your enrichment is one provider filling one field and that will be true next year, a workflow webhook does the same job with no third meter. If the logic is "try this, then that, and if the company is European do the other thing", and it changes every month because somebody keeps learning something, then the table is not overhead, it is the product.

The write step is where teams get hurt, and the fix is procedural rather than technical.

  • Run the table read-only until the columns look right.
  • Write to a handful of rows and open them in HubSpot.
  • Only then schedule it.

Every unpleasant Clay-to-CRM story starts with someone skipping the middle step.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-10-11
Sources
4 vendor documents
Paid placement
None

The integration moves the record. Something has to fill it.

Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under HubSpot, Clay and everything else in this directory, and it returns null with a confidence score rather than a guess.

Free trial, no card required, and 500 credits to start.

HubSpot and Clay, asked and answered

How does Clay connect to HubSpot?

Through native actions in both directions. Lookup actions read contacts, companies, deals or a list into a table without changing anything in HubSpot. Create and Update actions write back, and those writes are immediately visible to every user in the portal. Nothing extra is needed on the HubSpot side, including Data Hub, but Clay's own pricing page marks "CRM integrations" as a Growth feature, so the gate is on Clay rather than on HubSpot.

Which Clay plan do I need for the HubSpot integration?

Growth or Enterprise. Clay's plan comparison lists "CRM integrations", "HTTP API integrations" and "Automate any signal via webhooks" as included from Growth and not on Free or Launch, and Growth is listed at $446 a month on the page header. "Schedule recurring enrichment runs" arrives one tier earlier, on Launch. The Clay HubSpot documentation names no plan at all, which is why teams find this out after building the table.

Will Clay overwrite my HubSpot data?

Only what you point it at. Three rules keep it safe: write to prefixed properties that no human types into, leave "ignore blank values" on so an empty response never blanks a populated field, and exclude the properties your reps maintain. Then test on ten rows and open them in HubSpot before scheduling anything.

Why is my Clay bill higher than expected?

Because actions are consumed by the attempt rather than the result. If half your rows resolve, your real cost per filled field is twice the action rate. The lever is the filter on the import step: pull only the records missing the field you care about, never the whole portal.

Should I use Clay or a HubSpot workflow?

A workflow if the enrichment is one provider filling one field and that will still be true next year, assuming you own Data Hub Professional. Clay when the logic is conditional, changes monthly, and is owned by somebody who does not write code. Paying for a table nobody has opened in six months is the failure mode worth checking for.

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant