Clay CRM: is Clay a CRM, and how does it sync with yours?

Is Clay a CRM?

Clay is not a CRM. A customer relationship management (CRM) system is where a company records who its customers and prospects are, which deals are open, who owns each account and what has been said to them. Clay does a different job upstream of that: it finds companies and people, enriches them from many data providers, researches them with AI and then writes the result into the CRM you already use.

The practical test is what happens after a prospect replies. In a CRM the reply is logged against a contact and a deal, a rep is assigned and a forecast moves. In Clay there is no pipeline, no deal stage and no rep inbox. Clay's own integration pages describe the work as importing, looking up, creating and updating records in other systems, which only makes sense if another system holds the records that matter.

Think of Clay as the workbench and the CRM as the filing cabinet. Our guide to what Clay is covers the workbench in full, and the Clay integrations guide shows where the CRM sits among the other layers of a GTM engineering stack.

What do people mean when they search for Clay CRM?

The phrase "Clay CRM" covers three different intents, and it helps to separate them before choosing a tool.

• A search for the sales tool: people who have seen Clay used for outbound want to know whether it can replace HubSpot or Salesforce. It cannot, as above.
• A search for the connection: people who already run a CRM want to know how Clay talks to it, which is the Clay HubSpot, Salesforce and Attio integrations covered below.
• A search for a different product: a personal relationship app launched in 2021 was also called Clay, which is why TechCrunch's May 2023 piece calls it a personal CRM. Automattic bought it in June 2025 and renamed it Mesh (me.sh) in March 2026. It is a contacts and reminders tool for individuals, not the enrichment platform this guide describes.

If you landed here from the second group, skip to the CRM sections. If you are choosing a CRM, the pages for HubSpot, Salesforce and Attio compare pricing and fit.

Does Clay replace a CRM?

No, and trying to make it do so creates the problems it is good at solving elsewhere. Clay tables hold rows for enrichment runs, not a durable history of every touchpoint. The table below shows which system should own each job, and our waterfall enrichment guide explains the contact lookup row in detail.

A team that adopts Clay still needs a CRM, and one that cannot yet afford a CRM should start with a free tier of HubSpot or Attio rather than treating a Clay table as a database. Both vendors list free plans: Attio's Free plan allows three seats and 50,000 records as of October 2026.

Get your CRM ready for Clay data

Does Clay Audiences turn Clay into a CRM?

Not quite, although it moves Clay closer. Clay launched Audiences on 23 June 2026 and calls it its GTM data layer: one persistent profile per person and per company, built from your CRM, your data warehouse and Clay's own enrichment, which you filter into segments and act on. Clay's documentation lists it on all paid plans at no extra charge, with usage billed in the normal Actions and Data Credits.

Audiences still has no deal pipeline, no activity timeline and no rep ownership, and Clay's launch post describes it as a layer that syncs back to your CRM and warehouse, not a replacement for them. What it changes is scale and freshness: it removes the 50,000-row ceiling of a Clay table and re-imports CRM records on a schedule.

Write-back is uneven. Clay's Audiences docs list Salesforce Accounts and Contacts as the only direct write-back destination, with field-level controls for write if empty, always write and never write. HubSpot is import-only in Audiences and Attio is not listed as a source, so for both you route records through a Clay table and use that CRM's own write actions, covered below.

How does the Clay HubSpot integration work?

The Clay HubSpot integration is a Clay-built integration marked Included in Growth+, with every action needing your own HubSpot account. Clay's documentation lists these actions: Import objects, Lookup object, Create object, Update object, Create association, Retrieve associated objects, Find owner, Add record to list and a pair of sequence actions that check or set enrolment.

Four details decide whether the sync is safe. First, import is a source, so you can pull an entire object or a static list into a table. Second, Lookup object filters on fields you choose, with HubSpot Object ID the most precise option, and it matches on the root domain by default unless you switch on subdomain matching. Third, Clay's docs do not describe any duplicate check on Create object. HubSpot itself treats email as unique for contacts but will accept a second company with the same domain, so look up first. Fourth, Update object needs the HubSpot Object ID of the record, so a lookup step must supply it.

The overwrite setting matters most. Clay's docs say Update object has an Ignore blank values option that defaults to on, so blank Clay cells do not overwrite HubSpot. Turning it off "sends blank values through and overwrites existing HubSpot values with them." Leave it on unless you deliberately want Clay to clear fields.

During connection, Clay requests read access for contacts, companies, leads, owners and lists, and offers write scopes that are on by default. Custom object scopes are only available on HubSpot Enterprise portals, according to Clay's troubleshooting note. Sequence scopes are off by default.

How does the Clay Salesforce integration work?

Clay's Salesforce integration is also marked Included in Growth+, with each action needing your own Salesforce account. As of October 2026 Clay lists nine actions. Reads: Lookup Record, Lookup Record via SOQL, Count Records in a List View, Salesforce Records and Salesforce Reports, which imports report data on a rolling basis. Writes: Create Record, Update Record, Upsert Object and Convert Lead.

SOQL lookups are the strongest feature for hygiene work, because they let you check for an account by domain, a contact by email or an open opportunity before anything is written. Upsert Object inserts or updates depending on whether the record exists, which is the dedupe-friendly option, but a Salesforce upsert matches on an external ID field. If your org has no field marked as both Unique and External ID on the object, there is nothing for the upsert to key on, so an admin has to create one first.

Be careful with Convert Lead. It turns a lead into an account, contact and opportunity inside Salesforce, which is a business event with routing and reporting consequences, so run it from a reviewed list rather than a live signal. Test every write action on a handful of rows in a sandbox first, because a bad bulk write is slow to unpick.

How does the Clay Attio integration work?

The Clay Attio integration is the most clearly documented of the three. It is marked Included in Growth+ and needs your own Attio account, connected through OAuth by a workspace admin. Clay can import records from an Attio object or list, with a cap of 50,000 records per import.

The actions are Create record, Lookup records, Update record and Upsert record, plus matching actions for list entries. Lookup returns up to 10 matches and is free, Create, Update and Upsert cost 1 credit per run, and Update works by record ID with no create fallback. Upsert matches on a unique, writable attribute such as email or domain, updates on a match and creates otherwise. Clay's docs advise checking with Lookup before creating, and using Upsert "when uncertain" to avoid duplicates.

Multiselect fields have their own switch: Update record can append to or overwrite existing multiselect values, and overwriting replaces what is there. Choose append for tags that several teams maintain. For Attio's own data model and pricing, see the Attio tool page.

What does a Clay CRM sync cost in credits?

Clay meters work in Actions and data in Data Credits. Clay's Actions and Data Credits doc says importing data from a CRM costs no Actions, formulas and filters cost none, and sourcing accounts or contacts is free of Actions too. CRM exports and syncs do cost Actions, and each enrichment costs one Action even when you bring your own provider key.

On the Attio page, Clay states 1 credit per Create, Update or Upsert run and free lookups. The HubSpot and Salesforce integration pages on clay.com do not state a per-action cost, so treat one Action per write as the working assumption from the Actions doc and confirm in a test table.

A worked example shows why this matters. Suppose you refresh 10,000 company records and write each one back. At one Action per write that is 10,000 Actions for the run. Clay's pricing page lists 15,000 Actions a month on Launch and 40,000 on Growth as of October 2026, but CRM auto-sync sits on Growth, so the refresh would use a quarter of the monthly allowance before any enrichment. Skipping rows that have not changed, with an Only run if condition, is the cheapest saving. Our Clay pricing guide covers plan limits in more detail.

Which CRM enrichment and hygiene workflows suit Clay?

Four workflows account for most Clay and CRM work. Each follows the same shape: import from the CRM for free, enrich in the table, then write back only the fields that changed.

1. Fill missing firmographics. Import companies with a domain but no industry, headcount or location, enrich them, and update only those empty fields.
2. Find missing contacts. Import accounts with no contacts at your target titles, run a waterfall to find and verify people, then create them in the CRM after a duplicate lookup.
3. Detect stale records. Re-check job titles and employers for contacts you plan to email, and flag changes in a review field instead of overwriting the original.
4. Route new inbound leads. Send form submissions to a Clay webhook, enrich and score them, then write the score and owner back so routing rules can act. Webhooks are a Growth feature, so check the plan.

The common design rule is to write to dedicated fields where you can, such as "Clay industry" and "Clay last enriched", and let a human or workflow promote the value into the main field. Salesforce's own copy field enrichment in Data 360 follows the same pattern: its Trailhead module creates new custom fields on the Account object first and maps the enriched values into those. A reviewable audit trail is easier to defend than a silent overwrite.

What mistakes cause overwrites and duplicates?

Most Clay CRM incidents come from five avoidable choices, and all of them show up on the first large run.

• Creating without looking up. Unless the CRM enforces a unique field, such as email on HubSpot contacts, a Create action can add a new record every time it runs. Put a lookup first, or use Upsert on a unique key, and make the Create step conditional on the lookup returning nothing.
• Matching on a weak key. Company names and subdomains produce near-duplicates. Match on the root domain, a CRM record ID or a verified email, and normalise domains in the table first.
• Letting blanks erase data. In HubSpot, keep Ignore blank values on. In Attio, choose append rather than overwrite for multiselect fields.
• Overwriting human-entered data. Enrichment is often wrong for small or new companies. Only write to a field when it is empty, or use a separate Clay field.
• Running on auto-update unattended. Auto-update writes new rows as they arrive. Test on five to ten rows, check the result in the CRM, then widen the run.

Another risk is permissions. Write scopes are broad, so connect with a dedicated integration user where your CRM allows it, so that Clay's changes are traceable in the audit log. A CRM set up with a clean data model makes every one of these problems easier to prevent, because unique keys, required fields and owner rules already exist.

When should you use the CRM's own enrichment instead?

Use the CRM's native enrichment when your gaps are basic and your volume is modest, because it removes a tool, a sync and a credit meter. HubSpot's knowledge base says data enrichment is available on Starter, Professional and Enterprise subscriptions and does not consume HubSpot Credits, although smart properties do, and that existing values are kept unless you run a manual enrichment or enable the setting to overwrite incorrect enrichment values. Automatic enrichment is off by default and needs a Super Admin to switch it on.

Attio enriches company and person records from the domain or email you give it. As of October 2026 its Free plan fills names, descriptions, logos, categories, social links and locations, Plus adds employee count and ARR, and Pro adds funding raised. Salesforce's native enrichment is thinner for prospecting data: its copy field enrichments live in Data 360 (formerly Data Cloud), which runs on its own consumption-based credits, so Salesforce teams more often reach for a third party such as Clay.

Move to Clay when you need things a CRM feed does not give you: several providers in a waterfall for emails and phones, enrichment from signals such as hiring or funding, AI research of a website, or scoring from your own rules. Many teams run both, using the native feed for logos and descriptions and Clay for contact data. If you want the Clay layer designed and connected for you, see our Clay agency service.